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
We have got lot of internal feature requests where a team wants to enable new analyzer package on their repo, and wants to generate a baseline of all the existing analyzer violations using a custom command line tool. The current baselining support in Visual Studio only works on individual projects/solutions and also needs the build administrator to open each solution in Visual Studio and manually perform a baseline operation. This is not feasible for big repos, especially as they keep adding new analyzer packages and/or move to new version of analyzer packages and want to repeat the baseline operation. Hence, the request is to provide richer symbolic information for diagnostics in SARIF errorlog output of the compiler, so that they can author a custom command line tool that operates directly off this error log output to generate global SuppressMessage attributes in a suppressions file which can suppress each of the reported diagnostics.
Compiler Feature Request
Enhance the /errorlog command line switch (or provide a new command line switch) so that the SARIF output contains the following additional information for each reported diagnostic:
Symbol kind of the containing symbol of the diagnostic location
Above information can be easily mapped to the target string and scope for suppress message attributes that can suppress corresponding diagnostic instance.
The text was updated successfully, but these errors were encountered:
Extracted out from #32102
Context
We have got lot of internal feature requests where a team wants to enable new analyzer package on their repo, and wants to generate a baseline of all the existing analyzer violations using a custom command line tool. The current baselining support in Visual Studio only works on individual projects/solutions and also needs the build administrator to open each solution in Visual Studio and manually perform a baseline operation. This is not feasible for big repos, especially as they keep adding new analyzer packages and/or move to new version of analyzer packages and want to repeat the baseline operation. Hence, the request is to provide richer symbolic information for diagnostics in SARIF errorlog output of the compiler, so that they can author a custom command line tool that operates directly off this error log output to generate global SuppressMessage attributes in a suppressions file which can suppress each of the reported diagnostics.
Compiler Feature Request
Enhance the
/errorlog
command line switch (or provide a new command line switch) so that the SARIF output contains the following additional information for each reported diagnostic:Above information can be easily mapped to the target string and scope for suppress message attributes that can suppress corresponding diagnostic instance.
The text was updated successfully, but these errors were encountered: