Re: WPF v Windows Forms



On Feb 25, 11:55 am, vulcanite <vulcan...@xxxxxxxxxxxxxxxxx> wrote:
Hello all,

I am just trying to get up to speed with WPF (and .Net 3.0 in general), and
trying to decide whether it is worth using WPF for a new business application
(job tracking) which will be used by small businesses on windows Pcs
(XP/Vista). Hope to have it
ready by late 2007.

The only reasons I can see to use WPF instead of WinForms are:

Built on direct X and not win32 subsystem for graphics rendering (but what
precisely is the benefit of that for a business app?)

XAML may be easier for designers (non coders);

Possibly can acheive a new look which Winforms cannot (but not sure what
that is - any examples?)

What other specific reasons should be taken into account?

Caveat: I have not started using WPF yet. The following is just from
what I've read....

PROS
Easier skinning (should you want to do that): easier for branding,
changing look of entire application for special needs. (Say, large
company wants application branded with their logo, colours, etc.)
Vector-based graphics make continuous scaling possible, may be better
for people with vision problems, etc.
Ability to cleanly separate UI functionality (code) from UI look
(design). Artsy-type designer people can work on look and feel
independent of programmers. (But if you're writing it all yourself,
that probably doesn't matter.) No, they probably won't learn XAML, but
then that's what design tools are for....
Any future UI enhancements will probably be exclusively for WPF and
not back-ported to WinForms.

CONS
Brand new. Version 1.0 of anything, by any company, is always scary.
That goes double for a complete rewrite of an operating system's UI.
Mind you, it probably won't take long to work the bugs out, but bugs
there will be....

.



Relevant Pages

  • Re: WPF vs WinForms
    ... Right now I think that is where the strengths are in WPF. ... button group where each tab is a radiobutton because a tab control ... Give us a Menu that you don't have to edit in Xaml. ... but I thought the design was very well done. ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: WPF vs WinForms
    ... Data binding isn't what it is in WinForms, and there's nothing equal to the DataGridView, which while it can be a pain in the a**, is very flexible. ... Right now I think that is where the strengths are in WPF. ... Give us a Menu that you don't have to edit in Xaml. ... but I thought the design was very well done. ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: New to WFP
    ... I purchased Visual Studio 2008 and several books thar seemed to deal with C# and WPF. ... You need to go get some books on the basics first and work your way up the spectum, which is not hard to do. ... is a programming paradigm that uses "objects" and their interactions to design applications and computer programs. ... Patterns are about design and interaction of objects, as well as providing a communication platform concerning elegant, reusable solutions to commonly encountered programming challenges. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Winforms oder WPF - Erfahrungen?
    ... Zeit für das Projekt veranschlagen, als Du das bei erfahrenen Entwicklern ... neuen Dinge, die WPF bieten kann, auch verwenden will. ... Code, unter WPF nun wieder in externen XAML-Dateien. ... Design viel deutlihcer gezogen wird. ...
    (microsoft.public.de.german.entwickler.dotnet.csharp)
  • Re: Message Routing in Winform-Applikationen
    ... Bei der IMessage-Schnittstelle funktioniert das! ... Controls selber, aber eben auch bei den anderen, "offensichtlichen" ...
    (microsoft.public.de.german.entwickler.dotnet.csharp)