WPF browser applications (XBAP) in Internet Explorer, Firefox, Chrome, Opera and Maxthon.Powered by Google App Engine

In contrast to Silverlight, XBAP (WPF browser application) needs .NET framework (3 or later) installed.

For Internet Explorer users:
Internet Explorer 6 or later. For Internet Explorer 7 or later open Tools > Internet Options > Security Settings - Internet Zone, .NET Framework section, enable XAML browser applications and Loose XAML and restart Internet Explorer.
PICTURE PICTURE
The default setting picture is from Security (WPF). If there are problems, try WPF XBAP Permission Repair Tool.

Verify your settings using this test XBAP.

One can enable XAML browser applications programmatically:

            int i = -1;
            string s1 = @"Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\3";
            try
            {
                RegistryKey key = Registry.CurrentUser.OpenSubKey(s1);
                if (key != null)
                {
                    i = (int)key.GetValue("2400");
                }
            }
            catch
            {
            }
            if (i > 0)
            {
                try
                {
                    RegistryKey key = Registry.CurrentUser.OpenSubKey(s1, true);
                    if (key != null)
                    {
                        key.SetValue("2400", 0);
                    }
                }
                catch
                {
                }
            }

For Mozilla Firefox users:
Mozilla Firefox 2 or higher,
Windows Presentation Foundation plug-in for Mozilla browsers is installed and enabled.
Check it in Tools > Add-ons. This plugin can be installed by installing (or reinstalling, which is not recommended) .NET Framework 3.5 Service Pack 1. There is an another way of enabling support for XBAP applications in Firefox by copying Netscape Plugin NPWPF.dll (approximately 69KB) from C:\WINDOWS\Microsoft.NET\Framework\v3.5\Windows Presentation Foundation\ from an XP / Vista /Server 03 machine running .NET 3.5 SP1 to Firefox plugin directory C:\Program Files\Mozilla Firefox\plugins (C:\Program Files(x86)\Mozilla Firefox\plugins for Windows 7) and restart Firefox.

Verify your settings using this test XBAP.

One can detect whether the WPF plug-in for Firefox is installed using javascript

            var wpfPlugin = navigator.plugins["Windows Presentation Foundation"];

For Google Chrome, Opera and Maxthon users:
Make sure that Mozilla Firefox WPF plug-in works. Install Path Editor. It is freeware. Run it and Add Directory C:\Program Files\Mozilla Firefox (C:\Program Files(x86)\Mozilla Firefox for Windows 7). Click Save to Registry.

PICTURE

An alternative way is through System Properties. Restart a browser. If Chrome says that WPF plugin is crashed when tries to open XBAP, press Back and Forward arrows several times. It is recommended to rename Maxthon's updater MxUp.exe from C:\Program Files\Maxthon3\Bin to avoid Maxthon's uninvited backstage activities. Opera can display xbap which cannot be scrolled off the screen and not from localhost. For Safari for Windows 5.1.7 in Windows XP SP3 this method does not work.

Verify your settings using this test XBAP or another test XBAP from Microsoft. Yet another test XBAP in iframe.

Sometimes use command line rundll32 %windir%\system32\dfshim.dll CleanOnlineAppCache to clear XBAP cache (it is valid also for 64 bit).

One can use WoVS Default Browser Switcher Visual Studio extension to change browser used by Visual Studio. Press CTRL+ALT+R in VS and visit What Browser?.

If an XBAP is the first WPF application to load, the cold start time can be 10 seconds or more.

Visit the following useful site for .NET programmers: .NET Framework Index.

back to Searchable .NET Framework inheritance hierarchy chart homepage.