Is Windows Forms dead with the advent of Silverlight/WPF and VS2010? - NOT A PROGRAMMING QUESTION BUT A RELIGIOUS ONE
-
What's your take? And are there still uses for Windows Forms-based rich client applications?
Sincerely Yours, Brian Hart
-
What's your take? And are there still uses for Windows Forms-based rich client applications?
Sincerely Yours, Brian Hart
-
What's your take? And are there still uses for Windows Forms-based rich client applications?
Sincerely Yours, Brian Hart
The only reason I'd see to use Windows Forms would be backward compatibility. Compatibility with developers that are already familiar with Windows Forms. Compatibility with systems that can't install .Net 3.0 but can install .Net 2.0. Compatibility with other programs expecting to interoperate with Windows Forms applications (e.g., remote desktop works faster with Windows Forms apps, and some libraries expect Windows Forms objects). Though, there is still some use for Windows Forms. For example, there is no FolderBrowserDialog in WPF, so one must reference a Windows Forms DLL to get access to that dialog. Also, the WPF tree view can't nest as many levels deep as the Windows Forms tree view (I'm pretty sure Mole uses a Windows Forms tree view for this very reason). Aside from technicalities like that (which could be fixed or worked around), I'd say there is every reason to completely move away from Windows Forms.
-
What's your take? And are there still uses for Windows Forms-based rich client applications?
Sincerely Yours, Brian Hart
I still use it for knock off internal apps. Nothing client facing.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
What's your take? And are there still uses for Windows Forms-based rich client applications?
Sincerely Yours, Brian Hart
Hell no. WPF is all nice... if you have a really bad ass computer. Also, in its 3.5 version, it's buggy and has terrible IDE support. I tried using WPF for a couple of projects, but I ended up having to fight bugs in the IDE and the framework instead. Maybe .NET 4.0 has brought some goodies to the table, but I'm not holding my breath for VS 2010. 2010 is unbelievably slow! (Talking about the RC, not the Beta!)
-- Kein Mitleid Für Die Mehrheit
-
What's your take? And are there still uses for Windows Forms-based rich client applications?
Sincerely Yours, Brian Hart
Brian C. Hart, Ph.D. wrote:
are there still uses for Windows Forms-based rich client applications
Sure - in the same way that Win Forms didn't replace the need for developing MFC based apps.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
Hell no. WPF is all nice... if you have a really bad ass computer. Also, in its 3.5 version, it's buggy and has terrible IDE support. I tried using WPF for a couple of projects, but I ended up having to fight bugs in the IDE and the framework instead. Maybe .NET 4.0 has brought some goodies to the table, but I'm not holding my breath for VS 2010. 2010 is unbelievably slow! (Talking about the RC, not the Beta!)
-- Kein Mitleid Für Die Mehrheit
The IDE 'support' is a horrible joke, and the idea is to sell you Blend for that part. It's ridiculous. But, nothing beats a WPF UI, I am afraid.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
What's your take? And are there still uses for Windows Forms-based rich client applications?
Sincerely Yours, Brian Hart
No, it's not dead. Unless a CodeProject article is specifically about WPF or Silverlight, WinForms is still the fastest way to get a GUI on a sample application.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
What's your take? And are there still uses for Windows Forms-based rich client applications?
Sincerely Yours, Brian Hart
Font rendering is putrid on this machine, designer is lag-tastic and buggy, and overall a poor choice. Windows Forms crushes WPF for sure.
People think it must be fun to be a super genius, but they don't realize how hard it is to put up with all the idiots in the world. - Calvin (from Calvin and Hobbes)(The Indispensable Calvin and Hobbes, p105-3)
