We've found many posts/blogs/etc. about deploying the Crystal Runtime components For instance: http://wiki.sdn.sap.com/wiki/display/BOBJ/Deploying+Crystal+Reports+for+Visual+Studio+2010+Runtime and
http://scn.sap.com/thread/3366125
But, we want to make sure we understand the correct runtimes (meaning 32-bit or 64-bit) to install on a client, with a corresponding CRforVS project, based on the following:
A CRforVS project created in VS2010 (VB.NET) uses the latest components (SP6) to display (print/preview/export) a Crystal Report created in the Crystal Report designer.
The CRforVS project is compiled with a Target CPU of x86 (this is how SAP/BO had advised past versions of CRforVS to be compiled as Crystal did not support 64-bit.), and Target framework of .NET Framework 4.
Now that Crystal does support 64-bit, in order to support executing this particular CRforVS project from both 32-bit and 64-bit client machines, our questions are:
- Does the CRforVS project still need to be compiled with a Target CPU of x86?
- If so:
- Do we only need to include the 32-bit runtime components for all types of client machines (32-bit and 64-bit) since the Target CPU is x86? or
- Do we need to distinguish (at time of install) that if the client machine is 32-bit, install the 32-bit runtime and if 64-bit, install the 64-bit runtime regardless of the CRforVS project's Target CPU setting?
- If so: