Log verbosity

[rr-wfm]

Log verbosity

[molszews]

Seems like sqlproj way of building is automagically inserting GOs between files?

[jmezach]

@molszews That's interesting. You don't get this error when building the .dacpac using .sqlproj?

As for some log verbosity, have a look at the output from the Build. It should show you the files being added to the model and will probably give a clue about which file is causing this error.

[molszews]

I think this is related to PostDeployment scripts, I have many sql files that are not table models but migrations scripts, there is one marked as entry file in sqlproj:
<PostDeploy Include="PostDeployment\runMigrations.sql" />
which then uses sqlcmd syntax to include other files :r .\disableTriggers.sql btw. these are set in sqlproj as <None Include="PostDeployment\disableTriggers.sql" />

when I remove PostDeployment dir with all migration scripts then dacpac builds just fine

[jmezach]

Yes, by default we include all .sql files into the compilation, except for those in the folders Post-Deployment and Pre-Deployment (see the ItemGroup here). I believe those are the names of folders that you get when you create a new .sqlproj project.

You could try to rename the PostDeployment folder to Post-Deployment, or you can edit the .csproj and add this to it:

<ItemGroup>
  <Content Exclude="PostDeployment\**\*.sql" />
</ItemGroup>

That will probably fix building the .dacpac, but will probably not include the post deployment scripts you currently have. For that to work we'll probably need to add support for the PostDeploy and PreDeploy build actions somehow.

[ErikEJ]

I dont think those folders are created by default - just the Postdeploy/Predeploy Build action on the related scripts (and they can also refer to some scripts with build action None)

This file contains SQL statements that will be appended to the build script.		
 Use SQLCMD syntax to include a file in the post-deployment script.			
 Example:      :r .\myfile.sql								

[jmezach]

;) Maybe that's just how we've setup our projects. Perhaps we shouldn't exclude those by default anymore, although that would be a breaking change. Either way we'll probably want to add support for post deployment scripts. I'm just not sure how those can be added to the model and if they resolve those references by default or that we need to add some logic to make that happen. That does sound like a different feature than what is being requested here though, so maybe we should open a separate issue.

[ErikEJ]

Agree, proper support for pre and post is a separate issue.

[molszews]

ok, seems to me this issue can be closed now

[molszews]

btw @jmezach any hints re local setup to play with MSBuild.Sdk.Sqlproj locally? I mean, other way than publishing nuget package

[jmezach]

Have a look at the test projects. They mostly just include the Sdk.props and Sdk.targets files directly which should work if you want to try out changes locally.