xaml file to one of your pages. When you compile your application, an .xbap
file is generated. You can then request that .xbap file in Internet Explorer or Firefox, and
(provided the .NET Framework is installed) the application runs in limited trust mode
automatically. Figure 9-13 shows an XBAP in Internet Explorer.
nNote XBAP projects have a hard-coded debug path. That means if you move an XBAP project from one
folder to another, you??™ll lose the ability to debug it in Visual Studio. To fix the problem, double-click My Project
in the Solution Explorer, choose the Debug section, and update the path in the Command Line Arguments
text box.
CHAPTER 9 n PAGES AND NAVIGATION 278
Figure 9-13. An XBAP in the browser
The XBAP application runs just the same as an ordinary WPF application, provided you
don??™t attempt to perform any restricted actions (such as showing a stand-alone window).
If you??™re running your application in Internet Explorer 7 (the version that??™s included with
Windows Vista), the browser buttons take the place of the buttons on the NavigationWindow,
and they show the back and forward page lists. On previous versions of Internet Explorer and
in Firefox, you get a new set of navigation buttons at the top of your page, which isn??™t quite as
nice.
Deploying an XBAP
Although you could create a setup program for an XBAP (and you can run an XBAP from the
local hard drive), there??™s rarely a reason to take this step.
Pages:
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512