You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Change directory to samples\DeploymentExtensionsFailsSqlBuild\SampleDatabase
Build the project via dotnet build
The build produces
seeding.data.sql(4,1,4,1): Build error SQL70001: This statement is not recognized in this context.
This is a regression compared to .NET Framework solution, it successfully accepted the file as the extension for a contributor.
I'm expecting the build would pass the item to contributors.
I'm expecting the build would still validate SQL syntax if the extension is .sql and references to SQL objects, although this feature was not part of previous .NET Framework based implementation.
Did this occur in prior versions? If not - which version(s) did it work in? It worked in .NET Framework based project without SDK-like project.
Proposal:
I'm suggesting to fix this in SDK.targets similarly as PostDeploy and PreDeploy. Similarly, I believe, the same applies to BuildExtensionConfiguration.
<ItemGroup>
<!-- Remove files specified as PreDeploy, PostDeploy, and None scripts from build -->
<Build Remove="@(PreDeploy)" />
<Build Remove="@(PostDeploy)" />
<Build Remove="@(None)" />
<Build Remove="@(DeploymentExtensionConfiguration)" />
<Build Remove="@(BuildExtensionConfiguration)" />
</ItemGroup>
The text was updated successfully, but these errors were encountered:
Steps to Reproduce:
dotnet build
Did this occur in prior versions? If not - which version(s) did it work in? It worked in .NET Framework based project without SDK-like project.
MSBuild 17.7.1+971bf70db
microsoft.build.sql\0.1.12-preview
Proposal:
I'm suggesting to fix this in SDK.targets similarly as PostDeploy and PreDeploy. Similarly, I believe, the same applies to BuildExtensionConfiguration.
The text was updated successfully, but these errors were encountered: