Skip to Content
avatar image
Former Member

.Net Framework 4.0 and Crystal Reports 2013 on Windows 64-bit OS

Hi,

At present, we are using .Net framework version 3.5 with the Crystal Reports XI R2 version which is already deprecated version. 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. The Windows application that generates the reports various reports has reference to DLL's CrystalReports.Engine and CrystalDecisions.Shared.

We are planning to upgrade the Crystal reports to CR 2013 and .Net Framework to 4.0 targeting to Windows 64-bit operating system (Windows Server 2008 R2). I got an email from SAP representative with a link to full developer version and runtime version of the Crystal reports - CRforVS_redist_install_32bit_13_0_12.zip and CRforVS_redist_install_64bit_13_0_12.zip. I have installed both the versions of this on Windows 7 64-bit

operating system and could not locate the DLL's CrystalReports.Engine and CrystalDecisions.SharedDLL's CrystalReports.Engine and CrystalDecisions.Shared.

Please help me with the correct run time version of the reports that will have the refence to the above said DLL's.

Thank you!!

-Sivaram

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Jan 12, 2015 at 10:07 PM

    Hello,

    DO NOT install just the runtime for CR for VS on your DEV PC. The first link is to integrate into VS, all other are for redist only.

    SAP Crystal Reports, developer version for Microsoft Visual Studio: Updates & Runtime Downloads

    Set your Project for X64, do not use AnyCPU, or if you do be aware of the BootStrapper methods, Search for more info on this.

    SAP Rep should know better or does understand how this version works.

    Don

    Add comment
    10|10000 characters needed characters exceeded

    • A lot of things have changed since XI R2.  To integrate into Visual Studio, you MUST install the "Install Executable" from the link that Don gave you.  All of the other links on the row are for various forms of runtime installs that you can use, depending on what type of installation you've configured.

      So, yes, you need to uninstall the runtime and install the "Install Executable" on the development machine.

      -Dell

  • Jan 12, 2015 at 10:11 PM

    Another thing you need to be aware of, when you move to .NET 4.x, there is a new property for the CrystalDecisions references called "Embed Interop Types".  It needs to be set to "False".  Sometimes this automatically gets set correctly and sometimes it doesn't, so you need to check it.

    Also, you MUST use the full version of the .NET 4.x framework - Crystal will NOT work with the "Client" version of the framework.

    -Dell

    Add comment
    10|10000 characters needed characters exceeded