Build an Avalon Web Browser Application

Windows Presentation Foundation (“Avalon”) applications have two modes of execution: standalone applications and in-browser applications. The former model is I think well-understood, but the browser-based capabilities of Avalon are new to some people. Simply put, Avalon web browser applications (we’re still trying to come up with a good name – any suggestions?) run within the context of a partial trust sandbox, either filling the whole browser window or an inline frame. They’re perfect for enterprise applications where you don’t want to deploy anything to the client (simply browse to http://myserver/myapp.wba) and they’ll also be great for really immersive web experiences as Avalon becomes more ubiquitous on the desktop.

Karen Corby has just written a good whitepaper on this topic; it’s currently going through the MSDN edit / production process, but in the meantime I wanted to give you all an early peek of the article. You can download it from the staging server here.

Comments (6)

  1. Tim Sneath says:

    Charlie reminds me that it’s now OK to talk about using WBAs to develop new experiences for the Windows Vista Media Center. Check out the following link:,guid,9c467946-a52d-43dd-bf2c-b57d55fc0089.aspx

  2. Anonymous says:

    So how do you communicate to the backend from the WBA, when WCF (indigo) is not included in the sandbox?

  3. Tim Sneath says:

    Yeah, it’s not a perfect story, I think we’d all agree. WCF has prioritized other areas above implementing partial trust support for their first release. In partial trust, you can instead access web services from the originating server using the traditional ASMX model, which works just fine.

  4. Anonymous says:

    i think the white paper should also mention that WWF will not work in a WBA scenario

  5. Anonymous says:

    Have you considerd calling them Applets ?