|Dotfuscator > Configuring Dotfuscator via the GUI > The Standalone GUI > Working with Inputs > Silverlight Inputs|
Dotfuscator provides the ability to specify a Silverlight deployment file, .XAP, as an input. A Silverlight Package consists of a single XAP file which will be parsed and presented in the user interface as a Silverlight Package. All managed assemblies that are contained in the XAP will be used as inputs to Dotfuscator. Any other files contained in the XAP will be listed as Package Artifacts and, while not processed by Dotfuscator, will be included in the output XAP in the output directory. Dotfuscator will output a single XAP that contains obfuscated and/or instrumented assemblies, an updated manifest and any other non-assembly files from the input XAP.
To add a Silverlight Package select Add Input and type the path and a file name in the Add Input dialog box. You can also browse to the specific XAP file by selecting the Browse button and navigating to it. You can specify an explicit path or use a Project Property to specify a substitution property for all or part of the path.
All project settings will be applied to all Silverlight Package assembly inputs and exclusion rules can be created and saved in the Dotfuscator project for any assemblies contained in the list of package assemblies.
A Silverlight 4 package that is signed can be re-signed by Dotfuscator. The signing options are accessed via the Package Properties button or context menu entry and consists of the Certificate File, Certificate Password, and Timestamp Server URL settings. The Silverlight certificate options set the certificate file container and optional certificate password and timestamp server that are used to sign the output XAP file.