J
John
Hi
If I have a choice of WPF or Windows Form versions of a control which one
should I purchase?
Thanks
Regards
If I have a choice of WPF or Windows Form versions of a control which one
should I purchase?
Thanks
Regards
John said:If I have a choice of WPF or Windows Form versions of a control which one
should I purchase?
John said:Thanks. I use vs 2008 and all clients have win 2000 but mostly winxp.
Does wpf reduce application execution speed noticeably compared to windows
form?
Jon said:I believe that WPF is much more efficient overall - but tends to be
used to do snazzier things, which obviously have their own costs.
Steve Gerrard said:Jon, do you see future support as an issue at all? Or do you expect both to be
equally well supported long term?
Jon Skeet said:I suspect both will be supported for the foreseeable future. WPF has
been given so much emphasis that MS would lose face by dropping it now,
and there's so much code using Windows Forms that it would be madness
to stop supporting that.
Look how much code used VB6 and they dropped that. Why wouldn't they drop
Windows Froms too.
Jon Skeet said:True enough - but VB6 was sounding "old" by then. WinForms may sound
old compared with WPF, but it's still on the shiny .NET platform
they're pushing.
I don't *think* MS would drop support for it any time soon...
I agree, especially since there's so many controls not yet available in WPF,
and it's not as stable as Windows Forms. To me, it also seems like it's more
for graphics type apps than for business store-data-and-report-it kind of
apps.
Just my two cents' worth.
RobinS.- Hide quoted text -
- Show quoted text -
I have to wonder if VS2008/WPF is really ready for prime time.
Error Option Strict On disallows implicit conversions from
'System.Windows.Application' to 'WpfApplication1.Application'.
Smokey Grindel said:"WinForms" is just a wrapper for Win32 forms... to drop Win32 forms you'd
have to rewrite every windows app out there that has a UI... so don't
epect MS to drop them anytime soon...
Alex Clark said:I started to rewrite a small stats application for one of my customers a
few weeks ago. I got as far as wondering why I couldn't get root-lines to
show up on a tree-view control, and after much Googling realised that I'd
need 100+ lines of XAML template-altering non-intuitive chevron and curly
bracket laced code written by some hobbyist on the internet for something
that still wouldn't quite work the same way as the original root lines in
good old fashioned WinForms. This is how MS define WPF as being
"finished". Yeah, right...
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.