The custom tool 'CrystalDecisions.VSDesigner.CodeGen.ReportCodeGenerator' failed. The located assembly's manifest definition with name 'Microsoft.VisualStudio.Designer.Interfaces' does not match the assembly reference.

This error occurs when attempting to add a Crystal 9.2 report to a project. In this case, changing VSDesigner to VSShell as described in other forums does not work if you are using the 9.2 DLLs as your designer tools libraries.

It would help if I knew where to find an assembly's manifest definition. This also occurs when attempting to add a report to a webservice project. Which in turn causes all the generated code for the webservice to fail.

Interestingly enough this started happening after I resolved the issue of changing to the 9.2 web report viewer. Now .NET is confused about the reportcode generator. Also, not surprizingly, there are 3 different entries in the registry that are supposed to define what code generator .NET is supposed to use for a .rpt file.

'CrystalDecisions.VSDesigner.CodeGen.ReportCodeGenerator' is supposed to be the correct tool yet the error is saying the assembly manifest definition does not match. How can that happen???