This question is locked. New answers and comments are not allowed.
I am using JustCode and DataAccess. I'm wondering if there is a way to turn off JustCode analysis for the DataAccess generated classes, as the naming conventions used by DataAccess are giving me warnings because the names are cased wrong or are using the _ within method names.
Can I selectively disable the JustCode analysis on a give class? That would be nice because it would work with other ORM and other code-generated classes that cannot easily follow naming conventions and that should not be modified to correct the warnings, as it would cause problem the next time the code is regenerated.
Also, many of the SQL naming conventions do not match C# and .Net naming conventions. So when DataAccess uses the SQL table, sprocs, and parameter names as method names in the .Net classes, all of these will throw warnings. I have about 200 warnings like this, which effectively hides any valid warnings that I need to see. So at this point, the JustCode warnings become useless because I cannot pick through the 200 DataAccess generated warnings to find the couple that are valid.
How can I better manage this? I'd like to work through the warnings, but I need to turn them off on all of the DataAccess generated classes to do so.
Can I selectively disable the JustCode analysis on a give class? That would be nice because it would work with other ORM and other code-generated classes that cannot easily follow naming conventions and that should not be modified to correct the warnings, as it would cause problem the next time the code is regenerated.
Also, many of the SQL naming conventions do not match C# and .Net naming conventions. So when DataAccess uses the SQL table, sprocs, and parameter names as method names in the .Net classes, all of these will throw warnings. I have about 200 warnings like this, which effectively hides any valid warnings that I need to see. So at this point, the JustCode warnings become useless because I cannot pick through the 200 DataAccess generated warnings to find the couple that are valid.
How can I better manage this? I'd like to work through the warnings, but I need to turn them off on all of the DataAccess generated classes to do so.