Microsoft http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.png http://channel9.msdn.com/Tags/vance+morrison Channel 9 keeps you up to date with the latest news and behind the scenes info from Microsoft that developers love to keep up with. From LINQ to SilverLight – Watch videos and hear about all the cool technologies coming and the people behind them. http://channel9.msdn.com/Tags/vance+morrison en Sun, 26 May 2013 06:28:31 GMT Sun, 26 May 2013 06:28:31 GMT Rev9 2 1 25 conversation right here on C9 with Raja Krishnaswamy and Jesse Kaplan. The idea of type equivalence and its potential usefulness beyond simplifying and de-bloating COM interop that employs Interop Assemblies (CLR 4's No-PIA feature) led to the need to sit down with Raja and Vance Morrison to really dig into the thinking behind the technology. How does type equivalence actually work? What are the semantics and why? In the VS 2010 timeframe, what should developers expect to be able to do with this new programming abstraction? What types make sense to mark as equivalent? Why? Where does Type Embedding fit into this picture and what role does the compiler play in the No-PIA dance? What impact may this have on the future of managed-to-managed type "interop"? What's the story here? What's next?

This is a great conversation with the primary minds behind type equivalence support in CLR 4. Enjoy. ]]> http://channel9.msdn.com/Shows/Going+Deep/Raja-Krishnaswamy-and-Vance-Morrison-CLR-4-Inside-Type-Equivalence You recently learned about CLR 4's support for type equivalence in a conversation right here on C9 with Raja Krishnaswamy and Jesse Kaplan. The idea of type equivalence and its potential usefulness beyond simplifying and de-bloating COM interop that employs Interop Assemblies (CLR 4's No-PIA feature) led to the need to sit down with Raja and Vance Morrison to really dig into the thinking behind the technology. How does type equivalence actually work? What are the semantics and why? In the VS 2010 timeframe, what should developers expect to be able to do with this new programming abstraction? What types make sense to mark as equivalent? Why? Where does Type Embedding fit into this picture and what role does the compiler play in the No-PIA dance? What impact may this have on the future of managed-to-managed type "interop"? What's the story here? What's next?This is a great conversation with the primary minds behind type equivalence support in CLR 4. Enjoy. 3517 http://channel9.msdn.com/Shows/Going+Deep/Raja-Krishnaswamy-and-Vance-Morrison-CLR-4-Inside-Type-Equivalence Fri, 05 Jun 2009 17:12:00 GMT http://channel9.msdn.com/Shows/Going+Deep/Raja-Krishnaswamy-and-Vance-Morrison-CLR-4-Inside-Type-Equivalence Charles Charles 4 http://channel9.msdn.com/Shows/Going+Deep/Raja-Krishnaswamy-and-Vance-Morrison-CLR-4-Inside-Type-Equivalence/RSS .NET .NET Framework CLR 4 COM COM Interop No-PIA Programming Raja Krishnaswamy Type Equivalence Vance Morrison
Here, Vance guides us through some of the history of the CLR, a look inside the upcoming version and some insights into the future. One of the things that Vance is thinking about with respect to type inheritance is what he calls default interfaces: they are contractual, but with default implementation characteristics, as opposed to purely abstract as interfaces are today. So, a default(implementation) interface is capabe of changing without breaking the systems that implement it. Wait a minute, that' goes against the basic rules of interfaces in the OO world. Vance explains. Relax.

Meet Vance, the face of MSIL. There's much of his thinking and code inside the CLR. Learn about some this here. Tune in.

Enjoy. ]]> http://channel9.msdn.com/Shows/Going+Deep/Vance-Morrison-CLR-Through-the-Years CLR Architect Vance Morrison has been very busy working on the future of the CLR, especially as it relates to execution performance and the type system. Some of his latest work is present in the upcoming 4th version of the virtual machine that powers all things .NET, CLR 4, which ships with Visual Studio 2010. Vance has been on the CLR team since its inception. MSIL, the intermediate language produced by the compilers of all .NET languages, is primarily Vance's doing. Here, Vance guides us through some of the history of the CLR, a look inside the upcoming version and some insights into the future. One of the things that Vance is thinking about with respect to type inheritance is what he calls default interfaces: they are contractual, but with default implementation characteristics, as opposed to purely abstract as interfaces are today. So, a default(implementation) interface is capabe of changing without breaking the systems that implement it. Wait a minute, that' goes against the basic rules of interfaces in the OO world. Vance explains. Relax. Meet Vance, the face of MSIL. There's much of his thinking and code inside the CLR. Learn about some this here. Tune in.Enjoy. 2668 http://channel9.msdn.com/Shows/Going+Deep/Vance-Morrison-CLR-Through-the-Years Tue, 19 May 2009 15:48:00 GMT http://channel9.msdn.com/Shows/Going+Deep/Vance-Morrison-CLR-Through-the-Years Charles Charles 23 http://channel9.msdn.com/Shows/Going+Deep/Vance-Morrison-CLR-Through-the-Years/RSS .NET .NET Framework Architecture CLR CLR 4 MSIL Programming Vance Morrison Virtual Machines