When I add a Crystal control to my project VS creates a reference to the CrystalDecisions.Crystalreports.Engine.dll version 10.2.3600.

 

MSDN and the Crystal Reports "walk through" docs clearly say that if you are using the VS generated msi installer you DO NOT need to include merge modules, but...

 

1) Any time I output an msi without the merge modules NO Crystal .dll's are installed.

 

2) If I include the CrystalReports10_Net_EmbeddedReporting.msm then the *actual* crystal engine included, and eventually installed on the client machine, is version 10.0.9500.

 

In either case I get the error you would expect: "Could not load file or assembly 'CrystalDescisions.Crystaleports.Engine, version 10.2.3600"

 

If I add that particular .dll manually as a reference then the application gets a bit further before it tells me it can't find/parse/whatever yet another .dll. It seems I could be manually adding .dll's forever. So...

 

1) WHY would VS2005 add a reference to a specific .dll that it does not then include in the msi project?

 

2) WHY does the merge module for .Net/CR10 you get from Crystal Reports have .dlls versions that are out of date?

 

3) WHY do both MSDN and Crystal Reports say that you do not need to add merge modules when using an msi project, yet VS2005 loads NO CR dll's without the merge modules?

 

Has anyone else encountered this? How the heck can I work past this?

 

Thanks.

 

Kurt