.net - Which version of Crystal Reports do I reference (32-bit or 64-bit) when developing? -

I am currently using VS 2012 on 64-bit PC using Crystal Reports for VS 2012. After installing crystal reports for VS 2012, I saw that there are 2 main folders:

• General \ SAP BusinessObjects Enterprise XI 4.0 \ win64_x64 Li> General \ SAP BusinessObjects Enterprise XI 4.0 \ win32_x86

  The app I am deploying can be installed on 32-bit and 64-bit PCs, from which crystal reports Should DLL reference me? X86 or x64?

  Am I referred to two different solutions, an x86 DLL, and the other with x64?

  Update:

  What I did was to reference x86 DLS at the time of development, and to install X86 redirectional version of crystal reports on all of our deployment machines, Regardless of its architecture, there is hope that some of you exit from there

  I know It is not technically the answer to your question, but since it still remains unresponsive Is, nonetheless I thought I could give it to you anyway ...

  You can revisit that really requires a 64-bit version of your application or not. The most line-of-business applications (which I can assume is what you are making, because you are generating it from the report) actually does not benefit from 64-bit.

  You can create and distribute only 32-bit versions (x86) and even if it still runs on all machines, whether they are 32-bit or 64 -Bit versions run Windows or not because all 64-bit versions of Windows have a special subsystem that runs 32-bit code. It is completely seamless, and there is almost no compatibility problem to talk about.

  Many apps have been deployed in this way. Visual Studio itself is an excellent example: it is still 32-bit code, but it runs fine on 64-bit versions of Windows, thanks to WOW64

  To do this, you can target your project only, specifically referring to X86 platforms, and 32-bit DLLs. Since you are only constructing a binary, it will be easy to simplify the development and distribution efforts, not only in terms of knowing which DLL is to refer, but also to check the number of codes Is required and the distribution process is the same.

  If you write good code after standard idioms and recommended practices, then add 64-bit support later (if it has never been proven to be of some benefit to your case) a fairly trivial Operation will happen. The .NET Framework abstract platform-specific difference very well; In this way how they can offer "any CPU" targeting option. Also, if I am allowed to keep speculation (because I do not have any special experience with Crystal Reports), I imagine the public interface is both 32-bit and 64-bit DLL Is similar to.

  In that case, you can also refer to the 32-bit edition for your development work, and then configure your build script to make the right you want 32-bit or 64 Depending on the version of the DLL, you are building -bit binary.

  Naturally, the installer will need to make that choice, either during installation (if you are using a unified installer) or when you create the installer yourself (if you have 32-bit And 64-bit installer).