XBAP was really the initial intent of Silverlight back in the early years in terms of concept.
It rarely got touched the moment Silverlight was named so with that your not likely to see much in the way of support or fixes for issues given it was essentially parked to the side of the Microsoft production queues. Silverlight gets installed into the browser under its own activex permissions etc where as xbap has to from memory hook itself in via secured sites or something assbackwards as that .. Been a very long while since I last touched it. Xbap is just wpf with stuff locked down. Sent from my iPhone On 12/02/2012, at 6:29 AM, "Greg Keogh" <g...@mira.net> wrote: > Folks, what are the pros and cons of writing a Silverlight app versus a WPF > app running inside the browser (XBAP)? > > A bit of reading indicates that you get richer UI effects with XBAP and more > controls to play with. I see they all run in a security sandbox by default, > but you can run XBAP in full trust if you want. However, there must be some > other considerations that are not so obvious? ... dependencies on other > software, cross-browser support, download size, etc. > > I found this interesting comment: > > XBAPs are a powerful technology based on .NET Framework technologies, but > they are not commonly used on the Internet. Our crawls of the top 100,000 > websites found no uses of the technology. We know that many customers use > XBAPs on internal sites and, as such, these applications remain enabled in > the Local Intranet, Trusted, and Local Machine zones. > > I also tried to view an XBAP demo and IE9 blocked me, and I’m still looking > for which option will unblock the security. This leads me to think that XBAP > is more practical trouble than Silverlight. > > Cheers, > Greg
