Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Build 2013 Registration is now open!
Apr 04, 2013 at 10:21 PMLike
Such a great resource, thanks C9!
Windows 8 App for Channel 9 now available
Apr 03, 2013 at 3:09 PMWindows 8 App for Channel 9 now available
Apr 03, 2013 at 2:06 PMCool. But, I don't understand what's up with the layout:
http://i.imgur.com/4elNV6e.jpg?1
Looks like I'm missing most of the functionality described. Also - does the app truly not support the search charm, or is that just my version too?
Inside Windows 8: Martyn Lovell and Elliot H Omiya - The Windows Runtime
Nov 17, 2012 at 5:00 PMI feel similarly. We have legacy dependencies which won't pass the restricted WinRT API. Here's hoping that we'll get language projections and native XAML for desktop use (or side-loaded enterprise apps which can be compiled with fewer restrictions).
C# Part 1: Create a Hello world app
Oct 26, 2012 at 1:42 PMGreat tutorial, thanks!
Bart De Smet: Rx 2.0 RTM and RTW
Aug 28, 2012 at 4:08 PMA relevant post by Daniel Plaisted:
http://blogs.msdn.com/b/dsplaisted/archive/2012/08/27/how-to-make-portable-class-libraries-work-for-you.aspx
Bart De Smet: Rx 2.0 RTM and RTW
Aug 20, 2012 at 12:24 PM@bdesmet: Thanks very much for the reply and helpful suggestions! Will definitely keep an eye out for any official guidance, too.
Bart De Smet: Rx 2.0 RTM and RTW
Aug 18, 2012 at 5:01 PMThanks to Bart and Charles for yet another excellent Rx video. Here's a thought and question for you guys:
I could be reading this wrong, but it seems to me that if the Rx team has a hard time creating portable libraries (e.g. last-minute change in binary deployment/partitioning strategy between RC and RTM), the rest of us are probably going to do it wrong every time. I lead a small OSS .NET library project, and it's pretty intimidating to come up with a plan for deploying device-specialized libraries that themselves depend on platform-specific BCL classes, not to mention the collisions Bart mentions between portable and non-portable binaries.
This "platform enlightenment" and versioning stuff seems to be emerging as a pattern in itself - a virtual requirement of the new level of platform fragmentation in .NET. What's the hope that we can get tooling, or at least guidance, to help other library devs out there on this topic? I presume the platform specialization and discovery process would be implemented with something like MEF. Can you share the bootstrapper process for this? Can we expect IJW-like behavior in a future major .NET version?
Thanks in advance for any help or guidance.
David
TechEd Europe 2012: Now available on-demand on Channel 9
Jul 03, 2012 at 2:57 PMThanks!! How about this one? http://channel9.msdn.com/Events/TechEd/Europe/2012/DEV301
The BoxingBots Infomercial
Jun 29, 2012 at 3:08 PMYou guys are nuts. Love it. -David
See more comments…