{"id":2223,"date":"2010-04-06T06:00:00","date_gmt":"2010-04-06T06:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudio\/2010\/04\/06\/wpf-in-visual-studio-2010-part-7-wrap-up\/"},"modified":"2022-10-14T12:50:00","modified_gmt":"2022-10-14T19:50:00","slug":"wpf-in-visual-studio-2010-part-7-wrap-up","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/wpf-in-visual-studio-2010-part-7-wrap-up\/","title":{"rendered":"WPF in Visual Studio 2010 \u2013 Part 7 : Wrap up"},"content":{"rendered":"

This is the final part in the WPF in Visual Studio 2010<\/a> series.<\/p>\n

Reflections on the Series<\/h3>\n

One of the aims of this series was to give a deeper look into collaboration the Visual Studio and WPF teams undertook during this release, specifically focusing on the \u201cLessons learned.\u201d As such, I tended to focus on the issues we encountered and the solutions we came up with, rather than listing all the things that \u201cjust worked\u201d. That may have left a negative impression with some readers, but the reality is that we were able to do things with WPF that would have been impractical with GDI and Win32. By impractical, I mean that it would have been possible, but would have taken so much time that we wouldn\u2019t have been able to finish.<\/p>\n

The move to WPF also gave us an opportunity to examine the architecture of Visual Studio and make changes that enforce a healthy separation between data and presentation. This is invisible to an end-user but, by reducing maintenance costs and improving \u2018testability\u2019 of components, it is immensely valuable to the development team and that investment will pay off in future versions too.<\/p>\n

Visual Studio 2010\u2019s use of WPF has enabled a number of interesting extensions<\/a>, some of which have been<\/a> mentioned<\/a> on this blog and I\u2019m sure there will be more to come.<\/p>\n

In the end, I hope that this series was helpful and educational and helps ease any concerns about migrating to WPF.\u00a0 As always, please feel free to use the comment stream to post questions, comments or suggestions.<\/p>\n

Links<\/h3>\n

I\u2019ll take a break from writing my own prose and let others do the talking. There are many, many online resources for WPF and I\u2019m sure some of you have your own favorites. Here are mine.<\/p>\n

If you\u2019re looking for new features in version 4.0 here are a few nice summary articles:<\/p>\n

Scott Guthrie\u2019s blog : http:\/\/weblogs.asp.net\/scottgu\/archive\/2009\/10\/26\/wpf-4-vs-2010-and-net-4-0-series.aspx<\/a><\/p>\n

Lester Lobo\u2019s blog : https:\/\/learn.microsoft.com\/en-us\/archive\/blogs\/llobo\/<\/a><\/p>\n

You can also see video walkthroughs here<\/a> and shorter ones here<\/a>.<\/p>\n

For general WPF training, there are some bite-sized, single-topic screencasts up on windowsclient.net<\/a>, the official Microsoft site for WPF.<\/p>\n

For more in-depth discussions and interviews with team members and enthusiasts, check out Channel 9\u2019s WPF<\/a> video library.<\/p>\n

If you want to get started writing your own WPF extensions to Visual Studio 2010, check out these MSDN videos<\/a>, samples<\/a> and the Visual Studio Etensibility learning center<\/a>. The Visual Studio 2010 SDK<\/a> contains project templates for creating WPF Tool Windows and extending the new Editor in WPF.<\/p>\n

Thanks<\/h3>\n

I\u2019d like to thank everyone who took the time to comment on earlier posts. Those comments helped shape this series and have inspired additional topics for inclusion in future Visual Studio articles.<\/p>\n

Finally, let me thank those on the Visual Studio and WPF teams who helped put together this series, especially Matt Johnson<\/a> and Phil Price<\/a> for their excellent articles.<\/p>\n

Previous posts in the series:<\/p>\n