Greetings, Apologies for the cross-post, but I figured both lists may be interested...
Just upgraded our CruiseControl.NET 1.4 server with FxCop 1.36 after uninstalling FxCop 1.35. We use the FxCop task in the MSBuild.Community project, and unfortunately this task no longer works. A peek at the source in FxCop.cs task suggests the registry key has (probably) been changed between 1.35 and 1.36. Quick and dirty fix is to manually create a registry key: HKEY_CLASSES_ROOT\FxCopProject\shell\open\command With default value of: "c:\Program Files\Microsoft FxCop 1.36\FxCop.exe" "%1" As to a more permanent fix, once approach might be to check if key FxCop.Project.9.0 exists, and if it does, use that before falling back to FxCopProject. -- It's a wild world that we live in, you step to the vibe like a new found religion, take your position, compile your vision, futurism, algorithm has risen up! pfm - the western
