Wednesday, December 13, 2006 5:49 PM
I was recently trying to evaluate why there is seemingly two ways to write web-based applications with WPF. Am I way off?
Can anyone explain to me when I would use an XBap over a straight up WPF/E application?
Wednesday, December 13, 2006 6:07 PMAt the moment, yes you are way off.
Alan Z wrote: I was recently trying to evaluate why there is seemingly two ways to write web-based applications with WPF. Am I way off?
WPF/E wil work on the Mac and under Mozilla, however.
Monday, January 01, 2007 11:17 AM
The big answer is portability IMHO. WPF/E is meant to be for portable pieces of *WEB* content. It does not support the full WPF stack. On the otherhand, WPF/E is 1/50th the size (the x86 size of the .NET 3.0 Runtime is 50 Megs, 90 Megs for x64). And if you need Apple compatibility, WPF/E is the obvious choice.
XBap is a compelling answer closer to click-once deployment. I have a list of common confusions about WPF vs. WPF/E on my website if that helps too:
Monday, January 08, 2007 7:49 PM
Shan McArthur wrote: As it stands, neither XBAP or WPF/E are suitable for integrated web development.
Indeed. It really seems as if Microsoft has gone out of its way to make sure they don't have a competitive rich-client development environment.
XBap's hijack your whole browser and can't even read your session cookies. Meanwhile, WPF/E is just an anemic version of Flash with no Flex components. WPF/E's ability to communicate with browser objects is nice -- but since WPF/E has no functionality, what good is it?
Microsoft seems to be going backwards in the rich client domain. Even a plain old NET 1.1 object embedded in a web page using an <OBJECT> tag could be rendered as part of a larger HTML page.
WPF/E seems like it won't ever expose a significant portion of the CLR. I think the best hope is that the XBap team realizes they need to expose the browser's Document Object Model to running XBap's. Until then, XBap's will have to be built entirely in XAML.
Monday, January 08, 2007 8:49 PM
I agree with you on WPF/E but I think they are working to improve it in that regards.
I don't mind XPab not being able to access the browsers cookies or object model. That is what I'm hoping we would get away from with XBap.
Tuesday, January 09, 2007 3:03 PM
I dont believe you researched XBAP very much. XBAP are a method of deploying .net 3 applications in the browser sandbox.
XBAP enables nearly full .net 3.0 functionaly for writing fat or thin clients applications
While wpfe is a slim down portable (mac, mobile etc...) subset of WPF to enable cross platform media and rich data visualisation with XAML.
XBAP can read seesion cookies but you must enable it in your back end. See blog and example on
The XBAP / browser communication is weak i agree, but not impossible agian see example http://www.galasoft-lb.ch/mydotnet/WpfTests.TestOpenWindow/index.html
Friday, January 12, 2007 12:00 AM
XBAP cannot read or use the session cookies of the browser window that launched the XBAP application. The article demonstrates that it can hold onto the browser cookies of any child web services of the XBAP application, but this does not work for the parent window cookies. Consider a web application that uses forms authentication, then attempts to launch a secure XBAP application. The XBAP application cannot get the forms authentication cookies, and therefore cannot integrate with the web application using the same user credentials (without asking the user to re-authenicate).
I too wish that the XBAP team would reconsider their design requirements and allow XBAP to integrate with the container IE window/frame, share the cookies, access the DOM from within the XBAP, and open windows. All of these capabilities are possible with EVERY other web development platform, and missing these features is a significant impediment on WPF.
Friday, January 19, 2007 2:03 PM
Saturday, January 20, 2007 10:40 AM
hi andrew you said in your statement that combining c# and wpf/e is a piece of cake can you please guide me along as to how we can combine wpf/e based application with c# file.
Monday, January 22, 2007 9:56 PMNo, not from a WPF ("Avalon") application.
This post is provided "as-is"