|Dotfuscator > Configuring Dotfuscator via the GUI > The Standalone GUI > Working with Inputs > Windows Store Inputs|
Dotfuscator provides the ability to specify a Windows Store deployment file, .APPX, as an input. A Windows Store Package consists of a single APPX file which will be parsed and presented in the user interface as a Windows Store Package. All managed assemblies that are contained in the APPX will be used as inputs to Dotfuscator. Any other files contained in the APPX will be listed as Package Artifacts and will be included in the output APPX in the output directory. Dotfuscator will output a single APPX that contains obfuscated and/or instrumented assemblies, an updated manifest and any other non-assembly files from the input APPX.
To add a Windows Store 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 APPX 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 Windows Store 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.
All Windows Store packages are signed and must 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 APPX certificate options set the certificate file container and optional certificate password and timestamp server that are used to sign the output APPX file.