Being pragmatic by leveraging existing code in Metro style apps (Channel 9)

Being pragmatic by leveraging existing code in Metro style apps

Date: September 16, 2011 from 9:00AM to 10:00AM

Day 4

PLAT-877T

Speakers: Jason Olson

(1)

8,964 Views

6 Comments

Video format

Auto

Use our suggested format for this video.

Smooth Streaming

Adaptive bitrate streaming - little buffering but lower video quality at times of low bandwidth.

Progressive

Traditional buffered video format.

HTML5

For browsers that support h264 MP4 or WebM video playback such as:
IE9+, Chrome 5+, or Safari 4+.

Note: These selections will fall back to the next best format depending upon browser capability.

Does building a new Metro style app for Windows 8 mean you have to start from scratch? Absolutely not! Come learn how you can leverage existing code when developing Metro style apps for Windows 8. In this session, you will get an opportunity to learn directly from developers who have already benefitted from their existing code.

Follow the Discussion

Subscribe to these comments

Ian2 In geeks we trust ...

Sep 17, 2011 at 1:19 AM quote reply

Cool, am planning on bringing across some of my phone sequencing software* - will check out your sample!
Excellent presentation Dude!
PietAmersfoort

Sep 20, 2011 at 7:35 AM quote reply

Just watched your talk at Build.
Are there any online resources available on referencing legacy dotNET dlls in a Metro style app?
scarless

Sep 20, 2011 at 11:12 AM quote reply

Jason, please explain how it is useful to be able to wrap legacy code if you have to port it to WinRT anyway to list your app in the App Store? Since the App Store is the SINGLE point of distrbution why did you even give this talk?
JasonOlson

Sep 20, 2011 at 4:25 PM quote reply

Thanks Ian . It was great to come out and share what we've been working on .
JasonOlson

Sep 20, 2011 at 4:30 PM quote reply

Piet, IIRC, referencing legacy dotNET dlls is not currently supported in Metro style apps. You can find more information in Krzysztof's talk: http://channel9.msdn.com/Events/BUILD/BUILD2011/TOOL-930C

Scarless. The amount of porting required will depend heavily on the codebase you are discussing. Some code will just come forward with little to no changes (like JavaScript). I'm assuming you are specifically talking about .NET code though. Even with porting, it's still a lot of code you can leverage in your app rather than starting from scratch. For instance, just making the .NET code into a Metro style library rather than a full-blown class library. This is a similar situation that happens today with Silverlight and the profile of the .NET Framework you have to adhere to when developing Silverlight applications.
dentaku

Oct 06, 2011 at 2:10 PM quote reply

Interesting looking drum machine.
I hope there's a way of sending MIDI data from a Metro app. It would be nice to make something that's like Usine Pro but that doesn't actually create any audio.
I'm just thinking about the interface building part so you can create your own MIDI/OSC controller interfaces and send that data over virtual midi cables like Midi-Yoke.