If you come across publishing a SQL databse from a Visual Studio Database Project that the “the script file could not be found”, after a lot of digging around I found that all you need to do is delete the .dbmdl file, and it will publish again.
In VS 2012 I receive the following error message (one for each table) when trying to build a database project.
SQL71566: Microsoft.Data.Tools.Schema.Sql.SchemaModel.SqlFilegroup cannot not be set on both the Microsoft.Data.Tools.Schema.Sql.SchemaModel.SqlTable and the clustered Microsoft.Data.Tools.Schema.Sql.SchemaModel.SqlPrimaryKeyConstraint.
For reference here is script associated with this error.
CREATE TABLE [dbo].[OperationsMaster](
[OperationID] [numeric](18, 0) NOT NULL,
[OperationName] [nvarchar](150) NOT NULL,
[OperationTypeID] [numeric](18, 0) NOT NULL,
CONSTRAINT [PK_OperationsMaster] PRIMARY KEY CLUSTERED
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
In above script in last line on word [PRIMARY] red line appears. When I run the same script in SSMS it executed successfully.
You can get your project to build by enabling the project setting “Enable extended Transact-SQL verification for common objects.”.