This post originated from an RSS feed registered with .NET Buzz by Sam Gentile. Original Post: Microsoft Roadmap for Windows Forms and Avalon Feed Title: Sam Gentile's Blog Feed URL: http://samgentile.com/blog/Rss.aspx Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More! Latest .NET Buzz Posts Latest .NET Buzz Posts by Sam Gentile Latest Posts From Sam Gentile's Blog

Via Chris Sells, I found out about “John Montgomery, Microsoft Marketing Maven in charge of .NET and WinFX messaging, has posted the road map agreed on by the Windows Forms and Avalon teams about which UI stack to use and when.”  Chris also posts the relevant excerpt:

"Microsoft's roadmap for client UI development has three main phases:

1. "Today, use Windows Forms v1.1 and observe the Microsoft Patterns and Practices guidance for maintaining clean separation between UI and other application logic.
2. "When Avalon v1.0 releases (scheduled for mid-2006), we recommend that applications looking to differentiate their user interface such as Web sites and graphically intensive applications such as complex data visualization look closely at Avalon. Other applications should continue using Windows Forms.
3. "Following the release of Avalon 1.0, the next version of Visual Studio following Visual Studio 2005 will contain tools and designers to support Avalon. At this point, customers should start to move their new development efforts to Avalon and use the Windows Forms/Avalon interoperability features."