Hi, Anand > I don't have this problem. For me, FxCop 1.36 is working.
Is your build script using the FxCop task from MSBuild.Community.Tasks? Did you uninstall FxCop 1.35? (they install into different directories) Line 332 of FxCop.cs in MSBuild.Community.Tasks.csproj (r345): using (RegistryKey buildKey = Registry.ClassesRoot.OpenSubKey(@"FxCopProject\shell\Open\command")) When I look in the Registry after uninstalling FxCop 1.35 and installing 1.36 I only see key FxCop.Project.9.0, so how could this work? FWIW, I also get the missing images, but that's probably an css issue and nothing to do with FxCop task in MSBuild.Community. -- 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
