Installer deployment

This article is for IT Admins who want to configure Firefox on their organization's computers. We recommend keeping automatic updates enabled for Search Support Search. ORCA 4.

Use the Select your preferred language drop-down to install a Firefox MSI installer in your preferred language.

Logging can be configured on the MSI to help troubleshoot installation issues. Note that this will invalidate the MSI file's signature; if you need the file to be signed, you'll have to sign it again using your organization's certificate. In particular, using XCopy often incurs the overhead for creating, executing, and maintaining scripts for managing deployment in a robust way.

Furthermore, XCopy does not support versioning, uninstallation, or rollback. Windows Installer allows applications to be packaged as self-contained executables that can be easily distributed to clients and run.

Furthermore, Windows Installer is installed with Windows and enables integration with the desktop, the Start menu, and the Programs control panel. Windows Installer simplifies the installation and uninstallation of applications, but it does not provide facilities for ensuring that installed applications are kept up-to-date from a versioning standpoint.

ClickOnce enables Web-style application deployment for non-Web applications. Applications are published to and deployed from Web or file servers. Although ClickOnce does not support the full range of client features that Windows Installer-installed applications do, it does support a subset that includes the following:.

The deployment options for a WPF application depend on the type of application. From a deployment perspective, WPF has three significant application types:.

Standalone applications are deployed using either ClickOnce or Windows Installer. Either way, standalone applications require full trust to run. Full trust is automatically granted to standalone applications that are deployed using Windows Installer. Standalone applications that are deployed using ClickOnce are not automatically granted full trust. Instead, ClickOnce displays a security warning dialog that users must accept before a standalone application is installed.

If accepted, the standalone application is installed and granted full trust. If not, the standalone application is not installed. Markup-only XAML pages run within a partial-trust security sandbox with restrictions that are defined by the Internet zone permission set. For more information about security for WPF applications, see Security. These pages can be viewed using Internet Explorer or Windows Explorer.

For more information about registry entries, see Registry entries for Outlook form regions. Document-level solutions don't require any registry entries. Instead, properties inside the document are used to locate the customization. For more information about these properties, see Custom Document Properties Overview. In order for a customization to run, a solution must be trusted by the machine.

The Add-in can be trusted by signing the manifest with a certificate, creating a trust-relationship with an inclusion list, or by installing it to a trusted location on the machine. For more information about how to obtain a certificate for signing, see ClickOnce Deployment and Authenticode.

You can add an inclusion list entry with a custom action in your Windows Installer file. For more information about enabling the inclusion list, see How to: Configure Inclusion List Security.

If neither option is used, a trust prompt is displayed to the user to let them decide whether to trust the solution. For more information about security related to document-level solutions, see Granting Trust to Documents. The Setup and Deployment project templates are included with the Microsoft Visual Studio Installer Projects extension that is available for download. Visual Studio opens the File System Explorer for the new setup project. The File System Explorer allows you to add files to the setup project.

The setup project needs to deploy the ExcelAddIn. You can configure the setup project for this task by adding the ExcelAddIn project output to the setup project. The setup project needs to deploy the deployment manifest and application manifest. Add these two files to the setup project as stand-alone files from the output folder of the ExcelAddIn project. Select the ExcelAddIn. Figure 3: Application and deployment manifests for the Add-in in Solution Explorer. These components must be excluded and deployed using prerequisite packages to allow them to be registered correctly.

Also, the Software License Terms must be displayed and accepted before the installation begins. The Utilities assemblies are meant to be deployed along with your application. In the Properties window, change the Exclude property to True to exclude the dependent assemblies from the setup project. Make sure to not exclude any Utilities assemblies. You can configure your Windows Installer package to install prerequisite components by adding a Setup program, also known as a bootstrapper.

This setup program can install the prerequisite components, a process called bootstrapping. For the ExcelAddIn , these prerequisites must be installed before the Add-in can run correctly:. In the Prerequisites dialog box, select the correct version of the. Some of the configured prerequisite packages in your Visual Studio Setup Project are dependent on the selected build configuration.

You must select the right prerequisite components for each build configuration that you use. Microsoft Office locates Add-ins by using registry keys. Delete the [Manufacturer]? Use the text Software for the name of the new key. Right-click on the newly created Software key and create a new key with the text Microsoft.

Right-click the SampleCompany. ExcelAddIn key, select New , and click String value. Use the text Description for the Name.