Comments

Like Such a great resource, thanks C9!

2 days ago, Dan wrote

My personal thoughts are that for indie developers, we provide a totally free way to watch *every* session online in < 24 hours. That's unheard of in our industry. The total cost is $0.

If you are an indie developer, then I totally understand the importance of reducing costs. Traveling and airfare to an event can even cost as much as a pass to a conference like Build ($250/night for hotel, $400-1,200 on airfare depending on domestic vs international, food, etc).

If I was an indie developer, I would:

• Watch the live streams and ask questions during live Q&A
• Watch all the sessions that are relevant to me
• Attend FREE Microsoft training like our 1-2 day dev camps on Windows, Phone, Azure, Web - http://www.devcamps.ms/. The best thing about these camps is that they are so many that you may not have to incur any travel costs to attend.

 

 

Cool. 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?

3 days ago, schroedl wrote

"For better or for worse, desktop apps are desktop apps." -- this quote makes me sad.

I 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).

Great tutorial, thanks!

A 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

@bdesmet: Thanks very much for the reply and helpful suggestions! Will definitely keep an eye out for any official guidance, too. 

Thanks 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

Thanks!! How about this one? http://channel9.msdn.com/Events/TechEd/Europe/2012/DEV301

You guys are nuts. Love it. -David