Home/ Questions/Q 164473
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T11:45:01+00:00

I have been looking at a few of our VB.NET dll’s using FxCop and

  • 0

I have been looking at a few of our VB.NET dll’s using FxCop and all of the errors relate to DLL setup (i.e. Strong Names, Culture Info) and the case of Variables methods.

Looking at a few examples of FxCop examining a C# Dll, it appears to offer a lot more potential errors.

Does this mean that FxCop is more valuable on C# developments that VB.NET or have I just chosen bad examples.

I thought it was the case that FxCop worked on IL rather than the specific languages, so am I just missing rules files for VB.NET or are there more available for C#?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. I would say that’s not correct. FxCop is invaluable to any .NET developer.

    You need to show an example of where you get more (or less) output from FxCop for a piece of VB.NET code, versus a piece of C# code, both of which compile to the same IL.

    • 0