Compiler Error Message: CS0433

[Former Member]

Compiler Error Message: CS0433: The type 'CrystalDecisions.Web.CrystalReportPartsViewer' exists in both 'c:\WINDOWS\assembly\GAC_MSIL\CrystalDecisions.Web\11.5.3700.0__692fbea5521e1304\CrystalDecisions.Web.dll' and 'c:\WINDOWS\assembly\GAC_MSIL\CrystalDecisions.Web\10.2.3600.0__692fbea5521e1304\CrystalDecisions.Web.dll'

Support Information:

Windows Server 2003

Crystal 9,10 and 11 support required based on reports and web configuration.

This error relates to the following configuration:

Visual Studio 2005

Crystal .Net that comes with VS2005 SP2 (10.2.3600.0)

Web application deployment.

I am told that some Web.Config settings would fix this, but no one has been to specific.

Thanks

-Jonathan

[former_member184995 · Accepted solution]

Check your application and apps web.config for any references to the 11 version of the web.dll.

You need to check the references, the html pages that have viewers on them, the web.config, etc.

Jason

[Former Member · Accepted solution]

Been over those files many times today actually. Thanks for the suggestion though. Apparently this type of issue is a known issue when you have multiple DLL's in the assembly cache with regards to how Crystal is laid out.

My Web.Config has no refference to either assembly, the project reference only refferences 10.2.3600.0 DLL's, Specific Version is set to true on all of them. The only way around this problem from what I have read is to use some sort of Web.Config adjustment, and the only article that even slightly goes into this is:

http://blogs.gotdotnet.com/richarde/archive/2005/09/02/468187.aspx

As you can see by that article, Microsoft is not only aware of this problem, but have had to do work arounds in the Web.Config themself to get around it. The problem is, I do not know the xmlns to use for Crystal, the depenentAssembly information, or even the assemblyIdentity to use in this case.

What I need is the <runtime> variables for atleast version 10.2.3600.0 and 11.5.3700.0 along with 11.5.3300.0, some of my reports are directly created inside of VS 2005 C# .Net and need to be displayed in a web project, others are created in VS 2003 and used in an application layer and those are fine, but finally, I have Crystal XI R2 reports (several people creating these) which are displayed on a web page via <assemblies> tags within those sub project websites.

The sticker at the moment is the VS2005 C# projects. I would LOVE to just shove a package at VS 2005 to force it to upgrade from 10.2.3600.0 to 11.5.3700.0, then it wouldn't matter as much, but Microsoft won't support me, they consider this a Business Objects issue. What I am looking for is the Web.Config <runtime> setttings.

<runtime>

<assemblyBinding xmlns="????">

<dependentAssembly>

<assemblyIdentity name="???" publicKeyToken="???" />

<bindingRedirect oldVersion="??" newVersion="??" />

</dependentAssembly>

</assemblyBinding>

</runtime>

One for me to get past this issue.. Or some sort of upgrade to VS 2005 to bring it up to Crystal XI R2 package level, or some direction there of.

[Former Member · Accepted solution]

Any more suggestions on this or should I open a ticket with support? I really need to get this solved and I have to do it through Business Objects support, just would rather it be on the forums so others can also benefit from a solution. If the PublicKeyToken was different from version to version, this would be a non-issue, but they are not.

I have tried to use the Visual Studio Integration Manager, but it is telling me that CR 11.5 is not installed for VS 2005, which can't be true since I have Crystal Reports Developer XI R2 installed and it shows up as one of the options for VS 2003, but 10.2 is the only option for VS 2005. Is there a registery entry I need to update to fix this somewhere?

Edited by: Jonathan Wood on Oct 17, 2008 5:54 PM

[Former Member · Accepted solution]

Ok, I left messages for support, and emailed support and never got a call back, so I spent the weekend doing tests to try to solve this problem since support probably had no answer for me. Here is what I discovered. Crystal, when installed, only attaches itself to one version of Visual Studio that is installed, it has no clue how to itterate through multiple version. Say you have VS 2003, 2005 and 2008 installed. IF crystal finds 2003 first, it will hook into 2003 and the management tool will allow you to change versions of crystal only for 2003. This is true for any of those versions above. Which ever crystal installation finds first will be the only version that it hooks into and allows you to switch between.

Un-installing all versions except for the one that I wanted XI R2 to work with (in this case 2005), then re-installing crystal XI R2 allowed the management tool to see that XI R2 was installed for 2005 and allowed me to switch out the tools. This is very unfortunate that the install is not intelligent enough to just throw the files and update the registery for all possible versions of Visual Studio.

I tested this on 3 machines over the weekend, installed 2008 first, then 2005, then 2003, then Crystal, it only found the first instance of VS installed (2008), then I removed everything and started again, with 2005 first etc, and only 2005 was updated with Crystal XI R2, finally removed everything again and installed 2003 first and the rest then crystal, crystal install only found 2003. It only reacts to the first installation of visual studio it finds. This is undocumented and is a bug for the install. MANY developers have multiple version of VS installed and require the ability to switch which version of crystal they are using in which version of VS.

I had hoped in 72 hours that support would have called me back on this, but at this point I have solved this problem myself since I only require it on 2005 at the moment and if I need it on the other versions, I have laptops which I will load up with 2003 or 2008 and crystal to use the management switching tool made by business objects.

Second issue now posted in the threads with regards to crystal reports and a published website asking for login information on a schema. (which obviously you have no database login information for a schema .xsd file)

[Former Member]

No support on this, the only answer was the same as others who had this same problem which was not helpful and obvious. Final answer was found by me, the person who asked the question and I had sent in emails to support asking for a call-back and had no support response. Ultimately the answer was a work around to a bug for the Crystal XI R2 install which only supports 1 version of Visual Studio installed at a time.