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
Is your feature request related to a problem? Please describe.
I'm very happy to have a new parameter for SqlCodeAnalysis task, where we can specify a custom path to locate our custom rules DLLs, SqlCodeAnalysisAssemblyPaths and I think it's amazing how it works.
But all the errors now are not being thrown as build errors in my case, but as IntelliSense errors, during VS build/rebuild command (devenv.exe /build)
This is a problem, because with previous versions of Microsoft.Data.Tools.MSBuild I could install the custom rules DDLs inside VS SQLDB DAC folder and it would throw code analysis errors as build errors, using MSBuild command line. Now, with the errors being thrown as IntelliSense errors, I cannot use msbuild command line anymore to validate my solution.
Describe the solution you'd like
Code Analysis rules errors to be thrown as build errors, not IntelliSense errors.
Describe alternatives you've considered
Using older versions of DataTools + DacFx does the trick, but I'd like to use the more recent versions of DacFx and have the SqlCodeAnalysisAssemblyPaths parameter as an option for MSBuild.
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm very happy to have a new parameter for SqlCodeAnalysis task, where we can specify a custom path to locate our custom rules DLLs,
SqlCodeAnalysisAssemblyPaths
and I think it's amazing how it works.But all the errors now are not being thrown as build errors in my case, but as IntelliSense errors, during VS build/rebuild command (
devenv.exe /build
)This is a problem, because with previous versions of
Microsoft.Data.Tools.MSBuild
I could install the custom rules DDLs inside VS SQLDB DAC folder and it would throw code analysis errors as build errors, usingMSBuild
command line. Now, with the errors being thrown as IntelliSense errors, I cannot usemsbuild
command line anymore to validate my solution.Describe the solution you'd like
Code Analysis rules errors to be thrown as build errors, not IntelliSense errors.
Describe alternatives you've considered
Using older versions of DataTools + DacFx does the trick, but I'd like to use the more recent versions of DacFx and have the
SqlCodeAnalysisAssemblyPaths
parameter as an option for MSBuild.Additional context
The text was updated successfully, but these errors were encountered: