I reviewed several of our VB.NET libraries using FxCop, and all errors relate to setting up the DLL (i.e. strong names, culture information) and the case of Variables methods.
After looking at a few examples of checking FxCop in C # Dll, it seems to offer much more potential errors.
Does this mean that FxCop is more valuable in C # developments that VB.NET or I just chose the bad examples.
I thought it was so that FxCop was working on IL and not specific languages, so am I just skipping rule files for VB.NET or is there more available for C # there?
source
share