Multiple .NET framework in one solution

Question

1.00/5 (3 votes)

See more:

.NET4.5

Hi, I got one project in a solution in which I need to use .NET 4.5.1 or above for the function to be working(asynchronous programming to be exact). But in the one solution, I have multiple projects.

For example, Project A need .NET 4.5.1 while Project B need .NET 4(I know I can alter their .NET version but I want to keep it as it be to minimize the impact or possible error in the future). But when i try to run the solution, it returns me some error message(e.g. are you missing some assembly...)

Any help would be appreciated. Thank you.

What I have tried:

1. Altering .NET 4.5.1 back into .NET 4 but it did not support asynchronous programming.

Posted 17-Apr-16 21:00pm

Jamie888

Updated 17-Apr-16 21:05pm

Add a Solution

Comments

Sergey Alexandrovich Kryukov 18-Apr-16 3:04am

Formally speaking, it's possible just because projects in a solution can be unrelated. You should ask about the use of different versions in the same process (but why?)
If some project needs 4.0, it can be compiled to the 4.5.1 target, which is fine because you use it anyway. Use different targets, but why? Error message? Fix the bug. We have no information to help you.
—SA

1 solution

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)

Garth J Lancaster · Answer 1 · 2016-04-17T21:05:00

Solution 1

why dont you standardise on .NET 4.5.1 then - ie, project B -> .Net 4.5.1, not Project A 'downgrade' - Im pretty sure this wont have any nasty effects for project B, and that means you're on the same versions

or have I missed something ?

Posted 17-Apr-16 21:05pm

Garth J Lancaster

Updated 17-Apr-16 21:06pm