Deployment Issues - .NET 2005 and Crystal Reports 11 compatability with Crystal_Managed2003.msm

I have an application control that I just upgraded to .NET 2005 (from 2003).  The application uses the Crystal Report Viewer control and references the following dlls...:

 * crystaldecisions.crystalreports.engine.dll (version 10.2.3600.0)
 * (version 10.2.3600.0) access reports created in Crystal Reports 11.  

I am using InstallShield 11.5 for distribution (but I've also tried with the msi deployment project tool provided with VS.NET).  To make sure all the referenced dlls get loaded properly, I'm installing with the Crystal_Managed2003.msm merge module.  However, I noticed that the merge module uses versions 9.1.9800.0  for both the aforementioned dlls - a lower version that what .NET 2005 uses.  

When building my install, InstallShield warns me that it cannot find the above dlls for my application.  And sure enough, after running the install on my test machine, I get an exception concerning one of the dlls when I run my application:
System.IO.FileNotFoundException: Could not load file or assembly 'CrystalDecisions.Windows.Forms, Version=10.2.3600.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.
(note the version it is looking for)

Everything works fine on my development machine (of course).

Is there another merge module or something else out there that I can use so that the correct version of the dlls (and their dependencies) are successfully installed on the target machine?

This used to work when I was using .NET 2003.  I'm guessing it used to work in VS .NET 2003 because the provided dlls used version 9.1.5000.0 - which is lower than the merge module.

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.

you can try some updates on this page:

I had a similar problem when was conveting my program from VS2002 to VS2003.

good luck,

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
CincinnatusAuthor Commented:
Thanks Yurich.

That was exactly what I was looking for.  The merge module I downloaded (CrystalReportsRedist2005_x86.msm) contained the updated dlls for 2005 .NET

I still seem to be getting the same type error message, however.  But I must be doing something wrong in InstallShield.  I'll post a follow up question if I can't figure it out.

Thanks again.
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
.NET Programming

From novice to tech pro — start learning today.