Crystal Reports For .Net Framework 2.0 X64 Redistributable Package (64 Bit)
It’s an affordable SaaS solution that will be duly appreciated by people working with a large number of documents in various formats on a regular basis: from secretaries and students to IT specialists and content managers. Aplikasi pdf ke word. You no longer need to purchase expensive professional PDF editing tools to make a few occasional edits in your documents. Docs.Zone is an online service that can be accessed from any device connected to the Internet and supporting file downloads.
Problem Installing Crystal Reports Redistributable 64 bit version Posted by Sergey Barskiy on 21 October 2013, 11:52 am I was trying to install Redistributable package for one of the software systems I am working on on my Windows 8 64 bit machine. The Microsoft.NET Framework version 2 (x64) redistributable package installs the.NET Framework runtime and associated files required to run 64-bit applications developed to target the.NET. The crystal reports were created using the developer version CR XI R2 and these reports will get generated for different parameters in using windows application in.Net Framework 3.5. Common Crystal Reports For.net Framework 2.0 X64 Redistributable Package (64 Bit): What Are These And the way to Fix It.
| Similar help and support threads | ||||
| Thread | Forum | |||
| .NET Framework Installation Error Hi all, I just formatted my machine with Windows 7 64-bit then I got an error window while installing the latest .NET Framework 4.6.2 and I can successfully install 4.6.1 without problem. Please advise the workaround. Thanks! | Software | |||
| .NET Framework 4.5 'Fatal Error During Installation' While trying to install Windows .NET Framework 4.5 from the standalone installer onto my laptop, I get the error message 'Fatal Error During Installation'. When installing with windows update, I get the error code (0x80070643). NB: The CBS.zip file was 38MB, far bigger than the maximum 8. As.. | Windows Updates & Activation | |||
| .NET Framework Installation Error I royally screwed up. I tried to fix the CLR error 80004005 by uninstalling all .NET Framework versions my computer. After that, I restarted and tried to install the .NET Framework 4 on my computer. It downloaded the files, installed for maybe 1 minute and then says 'Installation failed' without.. | Installation & Setup | |||
| .NET Framework 3.0 Installation error? http://i33.tinypic.com/15rgz5y.jpg Hmm, anyone know what it means by 'Windows features' ? | General Discussion | |||
| Manual Installation of Framework 4.0 can not run Hello all, I have windows 7 64 bits and I have a problem with Framework 4.0. Windows suggested me with the updates it has downloaded correctly, but the installation crash. So I did a manual installation using this file 'dotNetFx40_Full_setup.exe' then he starts it decompresses a file on.. | General Discussion | |||
I'm currently using VS 2012 on a 64-bit PC, using Crystal Reports for VS 2012.
After installing Crystal Reports for VS 2012, I noticed there are 2 main folders:
Crystal Reports For .net Framework 2.0 X64 Redistributable Package (64 Bit)
- CommonSAP BusinessObjects Enterprise XI 4.0win64_x64
- CommonSAP BusinessObjects Enterprise XI 4.0win32_x86
The app that I'm going to deploy can be deployed on both 32-bit and 64-bit PCs, so which Crystal Reports DLLs should I reference? x86 or x64?
Or do I need to have 2 separate solutions, one with the x86 dlls referenced, and the other with x64?
Update:
What I did was to reference the x86 dlls when developing, and install the x86 redistributable version of crystal reports on all my deployment machines, regardless of its architecture. Hope that helps some of you guys out there
1 Answer
I know this isn't technically an answer to your question, but since it still remains unanswered even after having set a bounty, I thought I might suggest it anyway…
You might re-consider whether you really need a 64-bit version of your application. Most line-of-business applications (which I can assume is what you're building, since you're generating reports from it) do not really benefit from being 64-bit.
You can build and distribute only a 32-bit version (x86) and it will still run on all machines, regardless of whether they are running a 32-bit or 64-bit version of Windows. This is because all 64-bit versions of Windows include a special subsystem (Windows-on-Windows, or WOW64) that runs 32-bit code. It's entirely seamless, and there are virtually no compatibility problems to speak of.
Lots of applications are deployed this way. Visual Studio itself is an excellent example: it's still 32-bit code, but runs fine even on 64-bit versions of Windows, thanks to WOW64.
So to do this, you just set your project to target x86 platforms, and reference 32-bit DLLs exclusively. Since you'll only be building a single binary, this would greatly simplify development and distribution efforts, not only in terms of figuring out which DLLs to reference, but also the amount of code you need to test and the distribution process itself.
If you write good code that follows standard idioms and recommended practices, adding 64-bit support later (if it ever does prove to be of some benefit for your case) would be a fairly trivial operation. Download driver bolt aquila max bl1. The .NET Framework abstracts away platform-specific differences extremely well; that's how they can offer an 'Any CPU' targeting option.
Aside from that, if I am allowed to speculate (because I have no particular experience with Crystal Reports), I imagine that the public interface is identical for both the 32-bit and 64-bit DLLs.
In that case, you can just reference the 32-bit version for your development work, and then configure your build script to pick the correct version of the DLL depending on whether you're building a 32-bit or 64-bit binary.
Naturally, the installer would need to make the same choice, either during the install (if you're using a unified installer) or when you build the installer itself (if you have separate 32-bit and 64-bit installers).