Reputation: 12530
What happens in a .Net 4 app when referencing .net 2 assemblies?
I have an application I want to upgrade to .NET 4, but I have a couple 3rd party assemblies that reference the .NET 2 BCL.
I seem to remember reading something that says they should play nice, but I can't find any documentation on the subject. ( I think my question posed to Google is just too broad, with not enough .Net 4 material out there yet )
Can anyone help me find documentation on what will happen in this case?
Upvotes: 4
Views: 413
Answers (3)
Reputation: 5333
I wanted to reference StructureMap in one of my class libraries. Orginally it was created by VS2010 to use the .NET 4 client profile. Turns out, I had to changed this to the full .NET 4 framework, otherwise structuremap would not be recognized.
Upvotes: 0
Reputation: 300579
If I'm reading Scott Guthrie's post, Multi-Targeting Support (VS 2010 and .NET 4 Series), correctly then that will work fine.
Of Interest?: .NET 4.0 project reference 2.0 assembly
Upvotes: 1
Reputation:
The .NET Framework 4 works side by side with older Framework versions. Applications that are based on earlier versions of the Framework will continue to run on the version targeted by default.
Upvotes: 0
Related Questions
- When linking a .NET 2.0 Managed Assembly from a .NET 4.0 Application, which framework is used?
- .net 4 Application running a .net 2.0 assembly
- Can .NET 2.0 assemblies run under .NET 4.0?
- How can the very same assembly behave differently when used by an 4.5 or 4.6 app?
- Is there any difference between .NET 2 and .NET 4 assemblies running under .NET 4
- Referencing .net 2.0 assemblies in .net 4.0 application
- Referencing a .NET 2 assembly in a project targeting .NET 4
- How to link a .NET 2.0 assembly in a .NET 4.0 solution
- Will it be any performance issues when referencing 2.0/3.5 assemblies from .net 4.0 project?
- What happens when .NET 4.0 references a .NET 2.0 assembly?