Moving from Crystal Reports 9.1 to Crystal Reports 10.0

Experts i have an application which was developed in ASP.NET using Crystal 9.1 version.
Now the staging environment has 10.0 version and my crystal reports are falling apart when i move from testing to staging.
Is there any work around??
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

parveenmehtaAuthor Commented:
This is the error i get when i change the version in web.config and add references to 10.0 version

Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: The base class includes the field 'crvViewer', but its type (CrystalDecisions.Web.CrystalReportViewer) is not compatible with the type of control (CrystalDecisions.Web.CrystalReportViewer).

Source Error:

Line 20:                         </tr>
Line 21:                         <tr>
Line 22:                               <td colspan="2"><CR:CrystalReportViewer id="crvViewer" style="Z-INDEX: 101; LEFT: 8px; POSITION: absolute; TOP: 8px" runat="server"
Line 23:                                           Width="350px" Height="50px" DisplayGroupTree="False"></CR:CrystalReportViewer>
Line 24:                               </td>

Source File: C:\ACM_PRCS\ACM_PRCSWeb\reports\AddEmpDetailsViewer.aspx    Line: 22

Did you change to use the CR10 dlls or web parts?

Why is Crystal 10 installed in your staging environment?  Does production have the same?  You may be running into a contention with the Crystal dlls installed versus those that you are deploying (older).  If Crystal 10 is a requirement, then you should upgrade the development environment and package the app with those references and merge modules.

Staging should mirror prod.  If Crystal 10 is not really needed in Staging or Prod, then I would try un-installing all Crystal references and then deploy your app with the appropriate merge modules for Crystal 9.  Please see the following documentation:

Crystal 9

Crystal 10

Click on the Deployment Document links in both.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
parveenmehtaAuthor Commented:
Thank very much for your response and here is the good news.
I actually was looking for a redistributable that installs CR 9 dlls in windows assembly and fortunately i found it hidden deep down inside one of our company's shared drives.I ran the set up and man i tell you it started working as if it were never bad.
So got this issue resolved.
Thank you very much once again for your help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Crystal Reports

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.