This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. < But it's not!

Question

0.00/5 (No votes)

See more:

Hi,

I've upgraded a class library project in my solution to .NET Framework 4.0. But after the upgrade I figured out the server i'm using doesn't support .NET Framework 4.0.

So I had to downgrade again to v3.5. But after doing this, I cannot run my application anymore. When I run it, it compiles correctly, starts up the browser and then I get this error:

Could not load file or assembly 'Xxxxx_DLL' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. 
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.BadImageFormatException: Could not load file or assembly 'Xxxxx_DLL' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.

The webapplication using the assambly is set to .NET Framework 3.5 and the assambly itself is also set to .NET Framework 3.5. So this error should not be possible.

Do you guys have any suggestions?

Posted 15-Feb-13 0:41am

willempipi

Updated 8-Dec-22 23:58pm

v2

Add a Solution

3 solutions

Solution 1

The problem is likely to be in one or more of the assemblies you are referencing as part of your application.

Go into your project in VS, open up the "References" branch, and make a note of all the references you are using. You can then highlight each one in turn and look at the "Runtime Version" property in the Properties pane. At least one will be greater than the 3.5 your app is expecting.

Posted 15-Feb-13 0:59am

OriginalGriff

Solution 4

I faced the same issue after upgrading my code base from .Net 3.5 to 4.7.
The mistake I was doing was not upgrading the IIS Application Pool to 4.0 integrated to match the upgraded code.

So few things:-
1. Ensure your DLLs and Project are pointing to the same target runtime
2. Clean/Rebuild solution
3. Ensure APP Pool is according to the Project framework

Posted 8-Dec-22 23:58pm

Member 15859455

Updated 9-Dec-22 0:02am

v2

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

willempipi · Accepted Answer · 2013-02-15T01:54:00

Solution 2

Turns out the updated DLL (v4) was still in the Bin directory under a different name. Forgot I renamed the projectname.

Posted 15-Feb-13 1:54am

willempipi