CLR hosting has always been a hot topic. Consider the case of Windows Shell Extensions and the inability to load more than one CLR version per process being the dagger in the heart of the very idea of scalable managed shell extentions. With CLR 4, consuming
applications will be able to host both a CLR 2 and CLR 4 in the same process. Again, gone are the days of single instance CLR per process. The implications here are profound. On the one hand, this means that applications can run code targetting an older CLR
version and code targetting CLR 4 in the same process. How does this work, exactly? What are some of the key supported scenarios for mulitple CLRs per process? What does CLR In-Proc Side-by-Side mean for the future of CLR hosting, generally?
Meet two of the CLR SxS In-Proc developers, Simon Hall and Rick Byers. They explain exactly what went into the SxS In-Proc design, the challenges and opportunities. Tune in to get insight into the thinking behind the thinking in CLR 4's side by side in process