Come learn about the common XAML UI framework for Windows and Windows Phone. This session will cover the common XAML APIs across Windows and Windows Phone, techniques and limitations when using common XAML to build experiences both Windows and Windows Phone as well as cover device-specific XAML APIs that enable device specific experiences.

For more information, check out these courses on Microsoft Virtual Academy:

WPF being phased out - isn't that the route they're going, if you read the signs of the time? I just went through the session list of this Build, and there's not a single one about WPF development except for a panel discussion (see here). WPF is like dead in the water for at least two years. No words on its future, improvements, if they plan to let it take advantage of the native XAML stack etc. I hope there'll be some folks asking the right questions...

aaronholmes - You mean like we heard about it when Metro was announced and all they were talking about was C++ and HTML/JS? How they kept saying "Wait until September" and we realised that they had actually not considered .Net at all until the last minute and left us with not only yet another architecture - but one where there are more facilities for JavaScript than C#? (Like the entire messy ink canvas objects...)

WPF being phased out - isn't that the route they're going, ... No words on its future, improvements, if they plan to let it take advantage of the native XAML stack etc. I hope there'll be some folks asking the right questions...

Desktop apps are still desktop apps, and so are Windows Store apps. Both apps are very different in nature in the sense that they must exist and coexist in a Windows platform.

That way, I'd rather have WPF rewritten and integrated into WinRT in the future.

No WPF Sessions yet again.Call it build and they will come , LOLWindows phone == fail < 4% market share !Metro/Modern/Store == epic fail, tick tack toe?, tip calculator,etcRT = lolWPF making gains despite sabotage by Microsoft!search for WPF on MSDN and you see all post stop in OCT 2010,I have yet to hear a single reason why.without .Net/WPF/Silverlight MS has nothing of value to us.look like it may be time to start looking for alternatives!

Can MS now take the Universal platform to the next level and develop emulators for the competative platforms, based on the same dev. experience now introduced. Could this be a closer co-operation to a platform like Xamiran ?

Sure it's nice to have this common XAML framework now for mobile, but I'm still not convinced that "apps" will be the answer to all scenarios in the future. Maybe for consumers, but I don't see them fit for professional use cases and tools that require a deeper level of system access or extensibility. Sandboxing just ain't suitable for that. As of today, the platform actively prevents third-parties from building competitive browsers because they cannot benefit from JIT-compiled JavaScript, and an application like Visual Studio wouldn't be possible without removing one of its key strength that allows for third-party extensions.

I really hope when they are finished with the mobile obsession and made that platform solid, they'll find some time to spend on the desktop side of things again.

You should know that with this update, there is some steps made that makes XAML apps much much more powerful for Desktop/Business Scenarios. First is that they can run windowed/or snapped like before. Second, sideloaded apps get full access to desktop apis using some kind of brokered process, but still pretty seamless for developers. Third is the sideloading deployment is now much easier.

so i personally don't really see the need for WPF anymore(which is still supported and works pretty well), because there is now FULL desktop support actually. You just have to gather your informations. See: http://channel9.msdn.com/Events/Build/2014/2-515

dx12/wpf questions ... airgap , shell integration and real api exposure , flip3d , chrome , multiscreen and desktopsI understand it was important for microsoft to go on a diet for mobile , but you see how much of a thud that made on the desktop . nobody wants to spend thousands on 295s and titan z's to look at a 4k screen of color clashing tiles

As a long serving WPF developer, I can say that Windows RT is often completely inappropriate for full desktop development. The low information density and touch-first user interface components make it a complete non-starter. I've work with traders that use 6 monitors at once, all filled to the max with tightly packed data and charts. Metro applications will NEVER come to this environment. So banks are currently and actively looking at the alternatives. Banks always look 5 years ahead as they have to start now for anything happening in 5 years time. There's a big question mark over WPF (and Microsoft client technologies in general). So if they decide to move elsewhere in 5 years they are making that decision now. It doesn't take much to return desktop development to the first-class status it deserves, so Microsoft should do this as a matter of urgency, or become an also-ran in client software and hope azure pays all the bills.

@Dean Chalk: I don't think that is true, Microsoft really wants their New win RT to be the best, they are investing a lot to it, for example Microsoft was suppose to make windows better by making it similar to the easier and better Silverlight but they made Windows Phone coding experience worse by making it similar to the Windows Runtime. Its kind of weird because now most of the things are much more harder, This shows that Microsoft is not going to ditch Win RT

Remove this comment

Remove this thread

Comments Closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums, or
Contact Us and let us know.