cancel
Showing results for 
Search instead for 
Did you mean: 

Different Assembly Versions in Development and Production Environments

Former Member
0 Kudos

I have just taken over an ASP.NET project utilizing Crystal. I have acquired Crystal XI from BusinessObjects.com and installed it in my development environment but the assembly versions are slightly different. The version on the development server is:

<add assembly="CrystalDecisions.ReportSource, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

<add assembly="CrystalDecisions.Shared, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

<add assembly="CrystalDecisions.Web, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

<add assembly="CrystalDecisions.ReportAppServer.ClientDoc, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

<add assembly="CrystalDecisions.Enterprise.Framework, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

<add assembly="CrystalDecisions.Enterprise.InfoStore, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

The version that embeds after I add the comprable references on my development environment is:

<add assembly="CrystalDecisions.ReportSource, Version=11.5.3500.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

<add assembly="CrystalDecisions.Shared, Version=11.5.3500.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

<add assembly="CrystalDecisions.Web, Version=11.5.3500.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

<add assembly="CrystalDecisions.ReportAppServer.ClientDoc, Version=11.5.3500.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

<add assembly="CrystalDecisions.Enterprise.Framework, Version=11.5.3500.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

<add assembly="CrystalDecisions.Enterprise.InfoStore, Version=11.5.3500.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

Plus, numerous pages import the assembly directly so it can create custom tags like so:

<%@ Register Assembly="CrystalDecisions.Web, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"

Namespace="CrystalDecisions.Web" TagPrefix="CR" %>

I can control the web.config version with build constants but those don't usually work at the page level. Is there any recommedation for how I can develop on my machine which has the 11.5.3500.0 and deploy seamlessly to the production environment?

Thank you,

Jonathan Karlen

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi, Jonathan;

Are you sure the version was listed as 11.5.3500.0? It could have been 11.5.3700.0. This version would be for the .NET 2.0 framework, whereas the 11.5.3300.0 version is for the .NET 1.1 framework.

Your best bet is to always ensure you are deploying the correct runtime from our msi or merge modules.

Regards,

Jonathan

Former Member
0 Kudos

Yes, I did mean .37 but the production environment is running .NET 2 yet it's configuration files call for .33. I've double checked and the production server's IIS is configured to run .NET 2 and the code uses partial classes which would seem to clinch that it's .NET 2 code.

Former Member
0 Kudos

I hate to be a pest but if anyone here can help I'd be really appreciative. I have verified that I'm using the Framework 2.* in both my production environment and development environment. The production environment, which has been in operation for 18 months, references assembly version .3300 but that bombs on my newly setup development machine on which I've installed XI. Should I upgrade the references in production to .3700?

Former Member
0 Kudos

Were you able to get a resolution to this issue?

I've written an application in VS 2005 that export a report to PDF and works fine on the development machine. Once i install it on the production machine i have the same problem as you refered to. The assembly file information is different on my development vs the production machine.

thanks,

Ramon

Answers (1)

Answers (1)

0 Kudos

Please re-post if this is still an issue to the .NET Development - Crystal Reports Forum or purchase a case and have a dedicated support engineer work with you directly