Perhaps most importantly, my wallchart highlights the key changes between WinForm and WPF, Visual Studio 20. The MSDN web page is missing a few components from the Visual Studio toolboxes I have included all toolbox controls in the wallchart.My wallchart groups controls into categories, particularly useful because a pair of equivalent WinForm / WPF controls might not both start with the same letter.I provide for almost every such instance suggestions or alternatives for the WinForm control. When there is no WPF equivalent, the MSDN page halts right there.Notice for example, that it shows there is no equivalent for the DataGridView when, in fact, there is: the newly incorporated WPF DataGrid control. NET 4.0 version, some entries are not up-to-date. Though this web page purports to be the.Some of the table remarks are too terse for WPF novices I provide explanations in this article. Most of the controls and most of the footnotes from my wallchart come directly from this table. it is entitled simply, Windows Forms Controls and Equivalent WPF Controls – see Figure 2. It a single web page containing Microsoft’s rendering of the differences between WinForm and WPF libraries. One of the key resources I found to aid my understanding, and to jumpstart the research for this article, comes from MSDN. NET framework rather, it focuses on the components commonly used in the toolbox of Visual Studio’s visual designer.įigure 1: Thumbnail of the WinForm / WPF Cross-Reference Wallchart Start at the Beginning That is, it is not a comprehensive comparison for all classes in the. NET 3.5 to 4.0 for the toolbox-centric components. On a single sheet of paper it lets you compare, at a glance, WinForm to WPF, Visual Studio 2008 to 2010, and. Not to give away the ending, but you will want to refer to the accompanying cross-reference chart as you read this article-Figure 1 shows a thumbnail. (Part of my motivation is self-interest: it also gives me a reference to come back to!) Then I could say that I’d reached my first goal of “getting my feet wet”: still a long way to go! Next I organized the material and put it down on paper as a reference, something that I could then share with the developer community through a vehicle such as this article. I then went back through them again as a second pass with the goal of identifying patterns and compartmentalizing. How did I get started with WPF? I began by reading the blogs, the reference material, the tutorials, etc. You may find inaccuracies, though, due either to my nascent WPF knowledge or simply to the passage of time as technologies change. Note: My wallchart, and the discussion of it here, are as accurate as I could make them at the time of writing in March 2010, when Visual Studio 2010 is at “release candidate” stage. Rather, this article provides explanatory notes to my quick reference chart that could be quite a timesaver as you migrate from Visual Studio 2008 to 2010 and from WinForm to WPF. If that describes you, you will find this useful only in conjunction with other introductory WPF material. This article is not a starting point for the complete WPF neophyte. WPF is huge, so getting a clear understanding of either of these moves would be daunting doing both together might seem well nigh overwhelming! At the same time I decided to take the leap from WinForm to Windows Presentation Foundation (WPF) to take advantage of the expressiveness of the technology, and the richness of XAML. NET developer / designer for some time, and have been eagerly awaiting both the new design tools of Visual Studio 2010 and the new capabilities of the. He also describes the current weaknesses in WPF, and the most obvious differences between the two. NET 3.5 / 4.0. This can be downloaded for free from the bottom of the article. Michael Sorens provides a handy wallchart to help migration between WinForm / WPF, VS 2008 / 2010, and.
0 Comments
Leave a Reply. |