FxCop 1.35 Beta 1 Analyzes .NET 1.x and 2.0, But Not Together

I switched to version 1.35 of FxCop the other day and aside from it forcing me to install into C:\Program Files, I noticed that this version will analyze both 1.x and 2.0 .NET assemblies, which I believe is a change from the previous 1.32 Whidbey build (it only analyzed 2.0 assemblies). But be aware that the current build of 1.35 won't analyze 1.1 and 2.0 assemblies if they are part of the same FxCop project. You'll have to create separate projects if you need to do that. Hopefully the next beta release, or at least the final build, will allow you to have 1.1 and 2.0 assemblies in the same FxCop project. That would be tight.

Print | posted on Sunday, April 02, 2006 8:05 AM

Feedback

# re: FxCop 1.35 Beta 1 Analyzes .NET 1.x and 2.0, But Not Together

left by David M. Kean at 4/11/2006 10:59 PM
Dave,

FxCop 1.32 did/does analyze both .NET 1.1 and .NET 2.0 (I believe we did have a bug that prevented analyzing .NET 1.0 - but that's fixed now).

The missing installation folder page has also been fixed in the latest RC. However, you won't see the ability to analyze assemblies from different Framework versions any time soon. Due to the cross-assembly analysis, to do this would be quite complex for not much benefit.

Regards

David
Comments have been closed on this topic.