.net - When creating a new GUI, is WPF the preferred choice over Windows Forms? -
most restrictions , tricks windows forms common programmers. since .net 3.0 there wpf available, windows presentation foundation. said can make "sexy applications" more easy , .net 3.5 sp1 got speed boost on execution.
but on other side lot of things working different wpf. not more difficult have learn "everything" scratch.
my question: worth spend time when have create new gui , there no time pressure project?
wpf enables amazing things, , love it... feel obligated qualify recommendations, whenever developers ask me whether think should moving new technology.
are developers willing (preferrably, eager) spend time takes learn use wpf effectively? never have thought mfc, or windows forms, or unmanaged directx, not want team trying "pick up" wpf on course of normal dev. cycle shipping product!
do @ least 1 or 2 of developers have design sensibilities, , individuals final design authority have decent understanding of development issues, can leverage wpf capabilities create better, instead of more "colorful", featuring gratuitous animation?
does percentage of target customer base run on integrated graphics chip sets might not support features planning -- or still running windows 2000, eliminate them customers altogether? people ask whether customers care enhanced visuals but, having lived through internal company "our business customers don't care colors , pictures" debates in '90s, know well-designed solutions competitors make them care, , real question whether conditions right, enable offer make them care now.
does project involve grounds-up development, @ least presentation layer, avoid additional complexity of trying hook incompatible legacy scaffolding (interop win forms not seamless)?
can manager accept (or distracted noticing) significant drop in developer productivity 4 6 months?
this last issue due think of "fizzbin" nature of wpf, ten different ways implement task, , no apparent reason prefer 1 approach another, , little guidance available make choice. not shortcomings of whatever choice make become clear later in project, virtually guaranteed have every developer on project adopting different approach, resulting in major maintenance headache. frustrating of inconsistencies trip up, try learn framework.
you can find more in-depth wpf-related information in entry on blog:
Comments
Post a Comment