Which Library Files Necessary for VS-2010 Crystal Reports

[Former Member]

I've distributed the following Crystal DLL files in my application's folder,

just as documented in the Crystal Help File.

But I can't get reports to run unless I install the redistributable runtime CRRuntime_32bit_13_0.msi.

- CrystalDecisions.ReportSource.dll

- CrystalDecisions.Shared.dll

- CrystalDecisions.Windows.Forms.dll

- CrystalDecisions.CrystalReports.Engine.dll

Are these files necessary at all?

If I use merge modules which ones do I need?

I assume CRRuntime_13_0.msm

but what about the ...cs.msm, ...da.msm etc. they all look similar.

My application is in English and my customers are all English speaking.

Thanks

Dale

[Former Member · Accepted solution]

Hello Dale,

Crystal Reports is not fully managed by the .NET Framework. We have our own collection of runtime files that have to be installed. Using the MSI as you did is how the runtime files should be distributed.

You should not copy any of the Crystal assemblies or DLLs into your application directory. The files you listed will be distributed by the MSI. Any Crystal assemblies or files that are "copied local" won't be updated if you need to apply any updates for the Crystal runtime files down the road.

Sincerely,

Dan Kelleher

[Former Member · Accepted solution]

Hi Dan,

You answered the first part of my question and I understand that I could use the .msi to distribute the reu-time files.

However, it is extremely large and I was hoping that by using the .msm files the installation package would be smaller.

If this is a possiblity which .msm files are necessary?

Thanks for you time.

Dale

[Former Member · Accepted solution]

Hi Dale,

The size of the Crystal Reports runtime file distribution is essentially fixed. There's really no way to reduce the footprint of the MSI, and there's only a limited option for shrinking a deployment package using the Merge Modules. There is a slight bit of flexibility with the Merge Modules because you have the option of not using all the foreign language MSMs. You can also skip the "maps" MSM as well if you don't need it. This may reduce the overall size of your installer compared to the MSI, but the base MSM can't really be changed to reduce it's size.

You can visit the [Crystal Reports for Visual Studio 2010 Production Release Now Available|CystlR%2528SAPWeblogs%253ACrystal+Reports%2529] blog for a link to the Merge Module download, as well as other information specific to CR for VS2010.

Sincerely,

Dan Kelleher

[Former Member · Accepted solution]

Thanks Dan

So which one is the english language merge module?

The blog that you referenced omits that small piece of information..

I can't decipher the 2 letter code on each of the smaller merge modules.

Dale

[Former Member · Accepted solution]

Hi Dale,

The one that is English is the one that doesn't have a 2 letter designation - CRRuntime_13_0.msm. The two letter designations are the standard language designators (e.g. ES = Spanish) that are used by most software manufacturers. English would be EN, but since it's the default language in the main MSM.

You can look up the others with Google, etc. if you're interested in deciphering the rest of them.

Sincerly,

Dan Kelleher