Re: WPF/E Feasibility Summary

Take it from me...its not at all suitable.  WPF/E is about reach, not
richness of API and therefore for an intranet app it is not rich enough to
do what most people want.  I think you are more interested in XBAP and WPF
than WPF/E.  WPF/E's small download size is interesting because of its use
on Internet applications, not Intranet.  It is missing key components that
most enterprise developers need like text processing, printing, controls,
etc.  I have a number of WPF/E posts on my blog if that would help
understand the issues.  You might also look at Mike Harsh's blog
(http://blogs.msdn.com/mharsh).

Thanks,
 
Shawn Wildermuth
Wildermuth Consulting Services, LLC
http://wildermuthconsulting.com
http://adoguy.com
Microsoft MVP (C#), MCSD.NET, Author and Speaker


-----Original Message-----
From: Discussion of building .NET applications targeted for the Web
[mailto:[email protected]] On Behalf Of Brady Kelly
Sent: Wednesday, January 31, 2007 3:54 AM
To: [email protected]
Subject: [DOTNET-WEB] WPF/E Feasibility Summary

I need to compile a quick evaluation of WPF/E as a suitable platform for an
intranet business application. I was to fully evaluate it as an alternative
to our current ASP.NET application, but was later told to not devote too
much effort as the ASP.NET app is progressing better than expected.



I would appreciate some input from people who have played with or used,
WPF/E, or know more than me at least, to help in just drafting a short
report (1 -2 pages) on this platform. I have some of the usual info from
MSDN etc., but some experiential data, if available, would be a real bonus.


===================================
This list is hosted by DevelopMentor.  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com