Instead, you can simply copy your
compiled application to a network share or a virtual directory.
nNote You can get a similar effect using loose XAML files. If your application consists entirely of XAML
pages with no code-behind files, you don??™t need to compile it at all. Instead, just place the appropriate .xaml
files on your web server and let users browse to them directly. Of course, loose XAML files obviously can??™t
do as much as their compiled counterparts, but they??™re suitable if you simply need to display a document,
a graphic, or an animation, or if you wire up all the functionality you need through declarative binding
expressions.
CHAPTER 9 n PAGES AND NAVIGATION 279
Unfortunately, deploying an XBAP isn??™t as simple as just copying the .xbap file. You actually
need to copy the following three files to the same folder:
??? ApplicationName.exe. This file has the compiled IL code, just as it does in any .NET
application.
??? ApplicationName.exe.manifest. This file is an XML document that indicates requirements
of your application (for example, the version of the .NET assemblies you used to
compile your code). If your application uses other DLLs, you can make these available
in the same virtual directory as your application and they??™ll be downloaded automatically.
??? ApplicationName.
Pages:
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513