[RESOLVED] Understanding Namespaces

[jmcilhinney]

WPF is not an evolution of WinForms. It is a completely new way to create Windows applications built from the ground up to overcome some of the limitations of WinForms and to support features desirable in modern apps. Given that WPF and WinForms are just two different ways to create Windows apps, why would it be a surprise that they both provides classes to create buttons, check boxes and list boxes? These are the sorts of things many Windows applications provide so any technology that creates Windows apps would be incomplete if it didn't provide such classes.

In fact, such features are not limited to Windows apps. Web applications would be all but useless if they didn't provide such features too, which is why the System.Web.UI.Controls namespace, which is dedicated to types related to ASP.NET Web Forms application development, also contains Button, CheckBox and ListBox classes.

Probably the properties available for editing in WPF are higher for each of these controls. Right?

I have no idea what you mean by that but, whatever it is, it's wrong. You're really trying to take something simple and make it difficult. WPF and WinForms are just two technologies that can both be used to create Windows applications. That's it. There's a namespace dedicated to the types used in each. Each of those namespaces contains the controls you can use to build a UI using that technology. The control classes in each namespace have the appropriate properties to configure those controls. That's it.

[RBARATA]

Ok, now it's clear. Sorry for the confusion but I always like to know, not only the hows, but also the whys.

One more request, if possible. Can you post a code of an application using WPF and WinForms? As far as I understood, it's possible to "call" different namespaces into your original application. I just want to compare the possibilities between WPF and WinForms.

Thank you