0

I have a solution, different projects, all of them with Target .NET Framework 3.5. If update one of the projects to target .NET Framework 4 so i can use PLINQ, would it cause problems in any aspect ?

If yes, how may i avoid them please and what should i be aware of ?

Thanks in advance.

Improve this question
2
  • Is there a specific Reason why you don't want to change all Assemblys to 4.0 ? See this Post stackoverflow.com/questions/9747858/… Commented Oct 19, 2012 at 7:34
  • @KroaX i don't mind changing all to 4.0 actually as far as it won't cause issues Commented Oct 19, 2012 at 8:48

3 Answers 3

Reset to default
2

Yes you can have different configurations for different projects in the same solution

Solution just makes it easy to have all your related projects together in Visual Studio.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

1

.NET Framework 4 uses a different Runtime, so it might indeed cause problems. 3.5 uses the Runtime version 2, and to be able to use assemblies compiled for the 2.0 Runtime, you'll have to edit the app.config of your main executable (which would have to be 4.0) and add this to the configuration tag (or edit it if the element already exists): 

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

4.0 -> 2.0 references should work that way, but probably not the other way around.

The best solution IMO though would be to upgrade them all to 4.0 if possible. And of course users would need the .NET Framework 4.

Improve this answer

Comments

1

References between the projects could become a problem, I'd recommend upgrading all of them if that's possible to remain consistent. See this similar question as well.

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.