Frameworks

Time for XAML?

The language behind WPF is starting to gain momentum, thanks in large part to Silverlight.

Don't look now, but the broadly ambitious eXtensible Markup Language (XAML) vision Microsoft kicked off several years ago appears to be gaining traction. Most developers know XAML as the language behind Windows Presentation Foundation (WPF), the graphical subsystem unveiled in 2006 with .NET 3.0 and due for an extensive refresh in .NET 4. (check out last month's cover feature, ".NET 4 Revealed").

Ironically, the real driver behind XAML to date has been Silverlight, Microsoft's fast-evolving rich Internet application (RIA) platform. Even as WPF adoption languished, Web developers began working with XAML and tooling like Expression Blend for their Silverlight projects.


Silverlight has set the stage for XAML adoption, says Todd Anglin, chief evangelist with component maker Telerik.

"I think there's a bit of a halo effect on WPF from Silverlight. Silverlight was the attention-getter and people came and learned the core concepts of XAML within Silverlight," Anglin said in an interview.

That halo effect should grow stronger this summer, when Microsoft is expected to release Silverlight 3. The new version will introduce powerful new data and application capabilities that, for the first time, make Silverlight a mature target for live-fire business application development. The question is: Will desktop application developers simply develop for Silverlight rather than the more robust and extensive WPF spec?

It's an open question, and one that VSM readers will certainly have a say in answering. Meanwhile companies like Telerik are helping developers support WPF and Silverlight apps from a common code base, with components that work from a unified code set. Are you aiming to build XAML apps that run seamlessly in both Silverlight and WPF? Or do you plan to target WPF for your traditional client applications? E-mail me at mdesmond@1105media.com.


About the Author

Michael Desmond, former editor at large of Redmond magazine, is the editor in chief of Redmond Developer News magazine. He has served as senior editor of news at PC World and executive editor at Multimedia World magazine, and has written for dozens of publications and Web sites. Desmond has also written four computing books, including Microsoft Office 2003 in 10 Simple Steps or Less.

Reader Comments:

Wed, Jul 15, 2009 Mike Milwaukee, WI

In response to Marc from Oregon "The only reason to create desktop applications was that we could get richer applications at lower cost.".. how untrue. The main reason to create desktop applications is due to the security sandbox of a web application. I manage several developers and design the systems that are used by over 800 employees. One of my decisions on which route to take is if I have to access information across a domain. If it's yes, then it's most likely going to be a Windows form. Running SSIS packages from a web form.. not a good idea and requires widening security too much. I know, I did this with 4 days of Microsoft's help. My lesson learned is NOT to go this route.

Thu, Jul 2, 2009 John Kansas City

Marc, I agree with you that internet apps have their advantages, yes. However, networks fail... Desktop apps aren't going to go away and they will always be faster then a web application. Desktop have access to local resources and don't require network access necessarily. Oh wait... I forgot maybe we should do away with FireFox... It's an desktop application...

Thu, Jul 2, 2009 Marc Beaverton, OR

The only reason to create desktop applications was that we could get richer applications at lower cost. With the arrival of Silverlight this is no longer the case. And with the increase in applications we use on a daily basis the advantage of Internet applications becomes more and more clear: they don't pollute my PC and they don't ask me to install yet another update. (And when I get a new PC I can start working immediately.)

Wed, Jul 1, 2009 John Kansas City

With the profilerations of so many diverse technologies it would be great to be able to use XAML for both Silver Light and WPF applications... Wouldn't it just make sense to do it that way?

Add Your Comments Now:

Your Name:(optional)
Your Email:(optional)
Your Location:(optional)
Comment:
Please type the letters/numbers you see above