WPF or WinForms
-
I was just wondering about this: In which situations i should use WPF instead of WinForms to create a application ?
When design have more priority.
Rating is Always appreciated.
Regards,
Hiren Solanki.
Indian Forum | My Articles | My Profile
"You will always find me near 127.0.0.1"
-
I was just wondering about this: In which situations i should use WPF instead of WinForms to create a application ?
WPF is new technology and better. A new language learning curve is involved for .Net programmer. But, WPF allows for much easier data binding through its model and this can result in faster development time. Winforms is comparatively stable and has been for long time. Customer has more trust in this. RAM can go up or down depending on your implementation. WPF stores its data more efficiently so individual objects are smaller, but there tend to be more objects in WPF than in WinForms so this balances out, and either one can come out ahead. WPF is a huge win over WinForms when it comes to maintenance. Choice is Yours! If i had to choose, to develop only, i would got for WPF. But, If i am told i have to maintain it later, WPF pays bad.
-
WPF is new technology and better. A new language learning curve is involved for .Net programmer. But, WPF allows for much easier data binding through its model and this can result in faster development time. Winforms is comparatively stable and has been for long time. Customer has more trust in this. RAM can go up or down depending on your implementation. WPF stores its data more efficiently so individual objects are smaller, but there tend to be more objects in WPF than in WinForms so this balances out, and either one can come out ahead. WPF is a huge win over WinForms when it comes to maintenance. Choice is Yours! If i had to choose, to develop only, i would got for WPF. But, If i am told i have to maintain it later, WPF pays bad.
RaviSant wrote:
But, If i am told i have to maintain it later, WPF pays bad.
Says it all, really.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
-
RaviSant wrote:
But, If i am told i have to maintain it later, WPF pays bad.
Says it all, really.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
:thumbsup:
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
-
I was just wondering about this: In which situations i should use WPF instead of WinForms to create a application ?
WPF for Desktop, Niche, Bespoke App (Monitoring Apps, Chat, Diagramming Tools, Etc) Windows Forms for Database Applications (Customer Screens Etc).
-
I was just wondering about this: In which situations i should use WPF instead of WinForms to create a application ?
-
I was just wondering about this: In which situations i should use WPF instead of WinForms to create a application ?
IMO WPF every time, Apply the M-V-VM pattern and it works like a peach (and more code is testable). Winforms is old and clunky. The only problem with WPF is the learning curve, it is different to traditional Winforms development. Also get Snoop[^], it is invaluable and should have been part of the framework.
-
WPF for Desktop, Niche, Bespoke App (Monitoring Apps, Chat, Diagramming Tools, Etc) Windows Forms for Database Applications (Customer Screens Etc).
so true, my 5
M..X...E
-
I was just wondering about this: In which situations i should use WPF instead of WinForms to create a application ?
Lucian-aSterX wrote:
In which situations i should use WPF instead of WinForms to create a application ?
That depends. Do you already know WPF? If not then use WinForms. Your first job is to deliver working software. If you can meet the requirements with a technology that you already know then that's what you use. The only reasons to use WPF are 1. You've gone and learned WPF and the opportunity arises to join a WPF project. 2. You've got some requirements that you know will be too difficult to implement in WinForms, and sufficiently easy to implement in WPF that the time saved will compensate for the time lost on the learning curve. -Richard
Hit any user to continue.
-
Lucian-aSterX wrote:
In which situations i should use WPF instead of WinForms to create a application ?
That depends. Do you already know WPF? If not then use WinForms. Your first job is to deliver working software. If you can meet the requirements with a technology that you already know then that's what you use. The only reasons to use WPF are 1. You've gone and learned WPF and the opportunity arises to join a WPF project. 2. You've got some requirements that you know will be too difficult to implement in WinForms, and sufficiently easy to implement in WPF that the time saved will compensate for the time lost on the learning curve. -Richard
Hit any user to continue.
Like the sig, made me laugh :-D
Pete
-
I was just wondering about this: In which situations i should use WPF instead of WinForms to create a application ?
