on 01-14-2015 6:21 AM
I work with vs2010,but the crystal report version is cr2008 for vs2008.
I know the depolyment for that version is only msi,so how can i merge it into the installer project in vs2010
Hi Jason,
-Crystal report for VS 2008 is not compatible with VS 2010.
-Please have a look at the below KBA.
-To use the reports created with CR4VS 2008 you need to upgrade them to Crystal report for developers version of VS 2010.
-You can follow below link to download the CR for developers’version of VS 2010(embedded crystal report for vs 2010).
Download the latest service pack 12 executable fom first column
Link: http://scn.sap.com/docs/DOC-7824
-Install the new executable make sure you add all the 13.0 versions of dll’s to the application and remove 10.5 versions of dll’s (dll’s for CR4VS 2008)
-Now your application must be having 13.0 versions of dll’s.
-While deploying the application you can install the msi depends on how you have compiled your application as if 32 bit then install 32 bit msi from the respective service pack from the same link as above if 64 then install the 64 bit msi
-Check the 32 bit and 64 bit msi for service pack 12 and download the required one on you deplyment machine
NOTE:Make sure you are on same service pack with use of executable on development machine and msi on deployment machine.
Thanks,
Jayashree
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Actually, you don't have to upgrade the reports themselves - they should work with no problems. However, as Jayashree indicated, you'll have to upgrade to the latest version of the SDK, which can be downloaded from here: . Download and install the "Install Executable" for integration into Visual Studio. The other downloads are for the various types of runtime installs.
Here are a couple of things that Jayashree doesn't mention:
1. The version 13.x .dlls do NOT play well with the .dlls that come with CR 2008. So, you'll need to either uninstall the old SDK prior to installing the new one or use VS 2010 and the new SDK on a VM.
2. The Crystal SDK does not always work well when targeting your application to "Any CPU". So, you'll need to set the project properties to target either x86 or x64 and then install the correct version of the SDK runtime when you deploy it.
3. You MUST target the full version of the .NET Framework 3.5 or higher - the SDK does not work with the "Client" versions of the framework.
-Dell
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.