Synergy DBL Inegration (SDI) Should Support Rulesets as Opposed to Explicitly Setting the Warnings in the Project
For Both Traditional Synergy in Visual Studio and Synergy.NET Projects
Currently the only way to manage warnings is to explicitly set them in the project file. The correct "Microsoft" Solution is to have these be in a Code analysis rule sets file (https://docs.microsoft.com/en-us/visualstudio/code-quality/using-rule-sets-to-group-code-analysis-rules?view=vs-2017).
We desire that this is supported (at least in a basic form).
If we supported rulesets files, how would you want the interaction between the rulesets and projects to work? Would warnings and errors settings defined in the project take precedence over warnings and errors defined in the rulesets?
Thanks for the idea!
11/12/2018 8:56 PM 0
But to answer your direct question:
Anything set explicitly in the Project should take precedence. This will allow us the most flexibility to be forgiving on legacy projects.
11/12/2018 9:05 PM 0