Silverlight manifest file

The xap file is a compressed file — a zip file, if you will — that contains everything needed to deploy the Silverlight content to the client. One of the benefits of using this compressed file approach is that the smaller file requires less download time and improves the user experience.

And of course having only one file to deploy makes the deployment process very easy indeed. The other content that the xap file will contain is at least one dll file. In this case there is only the one — the library created in Visual Studio to hold all the classes, functions, variables, controls, resources, etc. Of course if the application is more complex and needs access to more than one dll then that will also be listed here in the xap file.

Net technologies do use, albeit with other names and different content. It contains the details of files and references needed by the deployed application — i. This is a slightly simplified description because the AppManifest does contain more information than just a list of files:. Setting up the development environment for a Smooth Streaming client requires attention to the domain requirements of Silverlight applications. NET development server without cross-domain configuration. The example in the current topic does not require cross-domain configuration unless you have to run the sample with the ASP.

NET development server. Clear the check box that indicates the option to host the Silverlight application in a new Web site. Instead, let the build process generate a test page. This page will be named TestPage. When the template completes and the project opens, you should see a display that looks like the following MainPage. Silverlight supports both the System. To use Smooth Streaming, add a reference to the Microsoft.

All other libraries needed for this application are supplied by the Visual Studio Silverlight template. Add the following line to MainPage. The tested web page is specified in the browser settings and is opened automatically when the browser launches.

Launch the browser using the Run Browser keyword test operation or the Browsers. Change the launching settings so that the browser first opens the about:blank page and then navigates to the desired web page from the test. Your test can look something like the pseudo-code below Prepare your Silverlight application for testing using the tcAgPatcher utility as it is described above. In order for TestComplete to be able to access the internal objects, methods and properties of this Silverlight application, prepare the application for testing with the tcAgPatcher utility.

See above for complete information. If you want to test a Silverlight application that uses cross-domain communication, you need to perform the following steps to make the application testable with TestComplete:. Create a crossdomain.

In the application manifest file AppManifest. By default, the application manifest file is generated when you are building your Silverlight project. For this purpose:. In the Project Properties window, switch to the Silverlight tabbed page.

Select the Generate Silverlight manifest file check box and specify a manifest file template by default, it is AppManifest. The way Silverlight application developers can change the enableHtmlAccess parameter depends on the way the application is embedded into the wrapper web page. Locate the Silverlight. The Deployment. Parts defines the Assembly Parts that are referenced in the project and present in the.

It also defines the main output DLL as the Assembly part. As shown in the above figure, we have only one assembly in our XAP the main project output and hence only one entry in the AppManifest. Let's add some more external dependencies to our project. Build it and open the XAP once again. Now you will see that in our latest xap, we have the external assemblies too as highlighted below :. If you open the AppManifest.

Parts section.