fxcop

Using FxCop when I try to analyze projects that rely on Patterns and Practices, Enterprise Library Data (among others) 2.0.0.0 - FxCop complains that it can’t: “Locate Assembly Reference” - even though the application dll being analyzed was complied against this version and its in the GAC. If I browse to the GAC try to select the same assembly (I've checked version and public key token) FxCop won't allow me "open" it. The application succeeds in running and definitely makes use of the problem dll. OS: Seen on both Vista and Windows XP. Versions: Visual Studio 2005 and 2008. FxCop 1.36

We have an ASP.NET MVC 4 solution with a couple of references that has been building without problems for about 2 years now. However, after installing KB2993928 and KB2993937 this morning, we cannot run FxCop on this solution on our Windows 7 machines anymore. I have a feeling this is because this update changed the DLL version of the System.Web.Mvc assembly in the GAC. This is because in the GAC I can currently find 3 different System.Web.Mvc DLLs, which are all updated today. The error we receive in the build is as follows: 6>MSBUILD : error : CA0001 : The following error was encountered

What is the issue? I am trying to install FxCop 10. To install that, Microsoft Windows SDK 7.1 is required. I installed the SDK. Now, to install FxCop, I have to run FxCopSetup.exe, which is supposed to be located in the folder %ProgramFiles%\Microsoft SDKs\Windows\v7.1\Bin\FxCop. But, that folder is missing. What I did to try to fix it? I searched the web to fix the issue, and I tried a couple of workarounds that were suggested in a few discussions including (1) not doing a full installation of the SDK and (2) uninstall SDK, reboot, re-install SDK and reboot. Any help is greatly appreciated.

I am trying to get latest version of FxCop. I am using Visual Studio 2010 Professional edition which does not include code analysis, so I am trying to set it up using FxCop. At http://www.microsoft.com/en-us/download/details.aspx?id=6544 there is readme file whic says to install Windows SDK which includes latest FxCop. I've installed Windows SDK from here http://www.microsoft.com/en-us/download/details.aspx?id=8442 and it does not include FxCop at all, I have checked both x86 and x64 versions. Any idea where can I find it? Is FxCop supported by Microsoft any more? EDIT: I did full installation

FxCop wants me to spell Username with a capital N (i.e. UserName), due to it being a compound word. However, due to consistency reasons we need to spell it with a lowercase n - so either username or Username. I've tried tweaking the CodeAnalysisDictionary.xml by adding the following section to the section: <DiscreteExceptions> <Term>username</Term> </DiscreteExceptions> From what I understand how custom dictionaries work, this should tell FxCop to treat username as a discrete term and prevent the CompoundWordsShouldBeCasedCorrectly (CA1702) check to fire an error. Unfortunately this doesn't

After installing the Developer Preview our Custom FxCop rules project won't build as the following Dll's can't be found: FxCopSdk.dll & Microsoft.Cci.dll It turns out that this is a red herring, looking at the project for the custom rules on other's machines, it doesn't build without re-referencing the aforementioned dll's correctly (so that's normal) the real problem is that our existing build is using the VS11 code analysis. I've now removed VS11 but it's still not working! Any ideas? Update: Since installing vs11 my build batch is defaulting to the VS11 version, this isn't happening on

FxCop 10 is complaining about the following: using XYZ.Blah; //CA1709 - "XYZ" using Xyz.Blah; //No complaint. using XylophoneSuperDuperLongFullName.Blah; //I don't want to have a long full name for my company name. The problem is... I want my company name to show up in all UPPERCASE because XYZ is an abbreviation. The long version of the name is much too long to be a useful namespace. Microsoft gets away with this kind of stuff because their acronym is only 2 letters. using MS.Something; //No Complaint. using Microsoft.SomethingElse; //No Complaint. So, I was looking at adding a