Have you had a look at http://blogs.msdn.com/fxcop/archive/2006/05/19/making-it-easier-to-move-from -fxcop-to-visual-studio-code-analysis-jeffrey-van-gogh.aspx ? __ Microsoft MVP Visual Developer - C# http://www.peterRitchie.com/
_____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Grant Holliday Sent: January 10, 2007 11:18 PM To: [email protected] Subject: [OzTFS] Moving from FXCop to Visual Studio Static Analysis Currently we have a Project.FxCop file which defines all the enabled/disabled FXCop rules to run. We'd like to migrate to VS2005 and use the built in code analysis (and run it with Team Build, obviously) Has anybody converted a FXCop profile file to the appropriate msbuild equivalent? It seems like there's nothing to do this: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1069170 <http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1069170&SiteID=1> &SiteID=1 The *.FxCop project file looks like this: <Rules> <RuleFiles> <RuleFile Name="$(FxCopDir)\Rules\DesignRules.dll" Enabled="True" AllRulesEnabled="False"> <Rule Name="AbstractTypesShouldNotHaveConstructors" Enabled="True" /> <Rule Name="AvoidEmptyInterfaces" Enabled="True" /> ... And the Project.csproj file looks like this: <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' "> <CodeAnalysisRules>+!Microsoft.Design#CA1012;+!Microsoft.Design#CA1040;-Micr osoft.Design#CA1062;etc....</CodeAnalysisRules> </PropertyGroup> I guess all I need is something that maps "AvoidEmptyInterfaces" to "Microsoft.Design#CA1040". Any ideas? OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net
