Answered by:
What runtime will .NET 1.1 DLL-references use in a .NET 2.0 application?

Question
-
Hi all !
I just migrated an application from .NET 1.1 to .NET 2.0, because I've been experiencing problems with .NET 1.1 runtime on certain Windows workstations.
The migration worked out fine, but some of the references is still referring to 3rd party DLL's that has been compiled under .NET 1.1.
What runtime will be used to run these .NET 1.1 DLL's, when they are used in my .NET 2.0 application?
Regards
Stefan Hansen
Wednesday, January 14, 2009 4:39 PM
Answers
-
Runtime loads per process, so your 2.0 app will load 2.0 runtime and 1.1 assemblies will not have any problem running agianst 2.0 because 2.0 is a backward compatible release.
- Proposed as answer by technicalganesh Friday, January 16, 2009 3:55 PM
- Marked as answer by Zhi-Xin Ye Wednesday, January 21, 2009 8:23 AM
Thursday, January 15, 2009 7:38 PM
All replies
-
Only a single runtime can be loaded into a process, if your app is using the 2.0 runtime there is no way for it to load the 1.1 runtime since the 2.0 version is already loaded.Wednesday, January 14, 2009 4:59 PM
-
The .exe determines what CLR version gets loaded, possibly with help from a .config file. That would have to be .NET 2.0 if you accomplished your goal. The .NET 2.0 assembly loader has no problem with .NET 1.1 assemblies.
Hans Passant.Thursday, January 15, 2009 1:30 AM -
Thanks, that's what i figured according to all the articles I've read, but I just couldn't find anyfinal answer :)Thursday, January 15, 2009 8:22 AM
-
Runtime loads per process, so your 2.0 app will load 2.0 runtime and 1.1 assemblies will not have any problem running agianst 2.0 because 2.0 is a backward compatible release.
- Proposed as answer by technicalganesh Friday, January 16, 2009 3:55 PM
- Marked as answer by Zhi-Xin Ye Wednesday, January 21, 2009 8:23 AM
Thursday, January 15, 2009 7:38 PM -
Absolutely, .Net 2.0 run-time environment is backward compatible...
Ganesh KumarFriday, January 16, 2009 3:59 PM -
... except for a very long list of known breaking changes.
(Was that sarcasm. I wasn't sure).
It's mostly compatible. But there are breaking changes.Thursday, January 22, 2009 2:12 PM