Skip to Content

need appropriate DLLS to refer to 4.2 version

We have a dot net application that is erroring out when we refer to the new DLLs from the BO 4.2 environment:

We get 'Could not load file or assembly 'CrystalDecisions.Enterprise.Report' DLL.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jan 09 at 04:33 PM

    I've run into a couple of issues with .NET SDK and the upgrade from 4.1 to 4.2. On the laptop where I do my development, I had to uninstall the 4.1 Client Tools and .NET SDK and completely delete the SAP BusinessObjects Enterprise folder and then do a full install of the tools I needed instead of upgrading the ones that were there. This was the only way to make sure that I had all of the correct versions. Also, some of the references may have moved. So, instead of just manually updating the references in the XML of your project's properties, you'll want to delete the existing references to the SDK and re-add them. If you're targeting the .NET 4.0 framework or newer, you'll also need to set the new "Embed Interop Types" property of the assembly to False.

    Finally, if your 4.2 system is SP4 or newer, you need to be aware that there were a bunch of changes to the underlying classes:

    1. All of the security libraries the SDK uses were updated - the previous ones were from (I believe) 2003 or 2005 and were seriously out-dated.
    2. The SDK now targets .NET 3.5 instead of 2.0.
    3. The requirement for the Microsoft Visual C++ 2005 redistributable was also updated to either the 2010 or 2012 version (I don't remember which and I have the 2010, 2012, 2013 and 2017 versions installed.) So, you'll need to make sure that you have that installed.

    -Dell

    Add comment
    10|10000 characters needed characters exceeded