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
The Scanner for MSBuild will analyze .cs files that are included in .sqlproj files created using the SQL Server Data Tools. However, the Scanner does not currently analyze files containing SQL.
The Scanner should be updated to analyze any files that can contain SQL e.g. .sql files.
Workaround
Add the following property to the .sqlproj file:
Notes
MSBuild classifies files by the ItemGroup they belong to (shown as the Build Action for the file in the Properties window in Visual Studio), rather than by file extension. SQL files in .sqlproj files have an ItemGroup of Build.
The Scanner for MSBuild has a list of ItemGroups that it should pass to Sonar plugins for analysis. Currently that list does not include Build, so SQL files will not be passed to the SonarTSQL plugin. The workaround above just adds Build to the list of file types to analyze.
The text was updated successfully, but these errors were encountered:
The Scanner for MSBuild will analyze .cs files that are included in .sqlproj files created using the SQL Server Data Tools. However, the Scanner does not currently analyze files containing SQL.
The Scanner should be updated to analyze any files that can contain SQL e.g. .sql files.
Workaround
Add the following property to the .sqlproj file:
Notes
MSBuild classifies files by the ItemGroup they belong to (shown as the Build Action for the file in the Properties window in Visual Studio), rather than by file extension. SQL files in .sqlproj files have an ItemGroup of Build.
The Scanner for MSBuild has a list of ItemGroups that it should pass to Sonar plugins for analysis. Currently that list does not include Build, so SQL files will not be passed to the SonarTSQL plugin. The workaround above just adds Build to the list of file types to analyze.
The text was updated successfully, but these errors were encountered: