On this page

CLR vNext with side-by-side support



The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

RSS 2.0 | Atom 1.0 | CDF

Send mail to the author(s) E-mail

Total Posts: 83
This Year: 0
This Month: 0
This Week: 0
Comments: 5

Sign In

# Saturday, October 11, 2008
CLR vNext with side-by-side support
Saturday, October 11, 2008 10:19:31 AM UTC ( Architecture )

Reading around the PDC site for some scoops into the future, I’m pleased to see one session covering how the CLR vNext will support side-by-side versioning of CLRs within the same process.

This may seem like a rather obscure requirement at first, but keep in mind we now have CLR v1.0, CLR v1.1, CLR v2.0 and the new CLR v2.0 shipped with .Net Framework 3.5 SP1. Luckily these CLRs and their libraries are largely compatible. However, over the years of .Net  the industry has written countless of components that they probably expect to be able to use for some time to come, even in-process. As our development tools and new frameworks keep pushing us up the stack to the next version of .Net, we will probably see some issues soon.

Hopefully, this feature goes beyond providing support for multiple Silverlight version within the same browser process, and enables us to use CLR 2.0 components from CLR vFuture. If this is the case, I'm looking forward to see how they will be providing interoperability, or if we’ll have to use an in-proc WCF channel for this purpose.

Maybe this may even be a hint that Microsoft is not expecting backwards compatibility between the current and future CLRs, and their libraries.