Crystal Reports not working with Visual Studio 2015

[former_member1086932]

Hello, all,

I have a following issue:

When I try to preview a crystal report in my application I get this error:

Could not load file or assembly 'file:///C:\Program Files\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\dotnet1\crdb_adoplus.dll' or one of its dependencies. The system cannot find the file specified.

I have seen people talking about this error, but, already in my application I have the advised solution for this problem applied-> In my App.config I have

<startupuseLegacyV2RuntimeActivationPolicy="true">
<supportedRuntimeversion="v4.0"sku=".NETFramework,Version=v4.6"/>
</startup>

I am working in a team with few developers, and just 2 of us, including me, have this issue.

We have all installed same CR version, and I do not see any specifics regarding my infrastructure.

My current configuration is this:

Windows 10 Pro 64-bit is OS.

Configuration:

CPU: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz 3.60GHz.

RAM: 12.0GB

I have both Visual Studio 2015 Enterprise and Visual Studio 2017 Enterprise installed, and were targeting to do reports development in 2015 version.

Crystal reports for Visual Studio version 13.0.17.2096.

I have even tried creating this dotnet1 folder, as it doesn't get created on installation ( nor it gets created on colleagues' workstation that don't get this issue)

and copying wanted files in there, but then I get other error:

Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information.

Please help. Highly appreciate any idea!

[former_member11696 · Accepted solution]

Hi Jelena,

That error is completely due to the legacy mode in the app.config file.

Use ProcessMonitor and make sure it is loading the right app.config file. There may be more than one in your project.

See if adding "Crystal reports for .NET" assembly to your project fixes this issue, if it's not there already.

Any warnings like Interopt type...?

Don