Could not load file or assembly crdb_adoplus.dll

问题:

For the following error:

Could not load file or assembly ‘file:///C:\Program Files\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\dotnet1\crdb_adoplus.dll’ or one of its dependencies.

Is there any way to resolve this error other than through the solution:

<startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0"/>
</startup>

That solution not work in my application

回答1:

Please use this code. It may be helpful for you.

<startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
</startup>

This is slightly different than you. For more details visit this link Crystal Report Viewer

回答2:

Change the first line to work successfully

After you open a file "App.config" from Solution Explorer

Previous:

<startup> 

<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/></startup>

Current:

<startup useLegacyV2RuntimeActivationPolicy="true">

<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/></startup>

回答3:

This stuff basically happens, if you have correct setup of SBO (I wish you so:)), that between different components of your SBO SDK there are assemblies with different .NET version. Check if you have some old version of SAP BO SDK installed on your machine too. Hope this helps.

回答4:

Use only

<startup useLegacyV2RuntimeActivationPolicy="true">
</startup>

It works for all frameworks!

回答5:

Try inserting the code below at your app.config or web.config file:

<startup useLegacyV2RuntimeActivationPolicy="true">
        <supportedRuntime version="v4.0"/>
</startup>

回答6:

Follow steps: Right click on project then click properties ->compile ->Advance Compile Option -> click Target framework and select .Net Framework 3.5 -> Now Click OK

Thats the simple solution.

回答7:

When facing this issue in ASP.Net application, check the application pool of the application in IIS. Change the Application pool to .Net 4.0 from .Net 2.0.

It will fix the issue.

回答8:

worked fine for me for all configs:MSIL, x64 and x86 bit even works just fine.