Microsoft http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.png http://channel9.msdn.com/Tags/raja+krishnaswamy 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/raja+krishnaswamy en Sat, 25 May 2013 06:35:04 GMT Sat, 25 May 2013 06:35:04 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
You will learn, in great detail, about Type Equivalence in a soon to be released conversation with Raja and Vance Morrison. For now, wrap your head around No-PIA. Raja and Jesse are great at explaining complexity in simple to understand ways. 

No-PIA in CLR 4 is the beginning of something very, very useful (consider the non-interop scenario (managed to managed) for a moment. Fascinating, Captain.)

Enjoy! ]]> http://channel9.msdn.com/Blogs/Charles/Raja-Krishnaswamy-and-Jesse-Kaplan-CLR-4-Inside-No-PIA Principal Architect Raja Krishnaswamy, Program Manager Jesse Kaplan and team have created a new way to streamline and simplfiy PIA-based COM Interop: rather than including an entire PIA (Primary Interop Assembly) in your application to utilize the functionality of a few of its member classes, with CLR 4 you are able, via type embedding and type equivalence, to include only the objects you need which has the pleasant side effect of decreasing the size of your application and making it much easier for you to update without relying on a new PIA version from some third party (like Microsoft Office, for a canonical example). How does this work, exactly? Does this mean that PIAs are no longer required? How does versioning in this scenario work, exactly? Let's learn all about the thinking behind the thinking of this new CLR enabled feature, No-PIA.You will learn, in great detail, about Type Equivalence in a soon to be released conversation with Raja and Vance Morrison. For now, wrap your head around No-PIA. Raja and Jesse are great at explaining complexity in simple to understand ways. No-PIA in CLR 4 is the beginning of something very, very useful (consider the non-interop scenario (managed to managed) for a moment. Fascinating, Captain.)Enjoy! 1670 http://channel9.msdn.com/Blogs/Charles/Raja-Krishnaswamy-and-Jesse-Kaplan-CLR-4-Inside-No-PIA Wed, 27 May 2009 15:43:00 GMT http://channel9.msdn.com/Blogs/Charles/Raja-Krishnaswamy-and-Jesse-Kaplan-CLR-4-Inside-No-PIA Charles Charles 7 http://channel9.msdn.com/Blogs/Charles/Raja-Krishnaswamy-and-Jesse-Kaplan-CLR-4-Inside-No-PIA/RSS Architecture CLR CLR 4 COM COM Interop No-PIA Raja Krishnaswamy Type Equivalence