Automated: Publish an Updated Version of an Application

Retired Content
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Prerequisites

This topic requires the following:

• Either the automated or manual procedures in How to: Publish an Initial Version of an Application must be completed.
• The procedures in How to: Deploy an Initial Version of an Application must be completed.

Steps

To modify a module before publishing the update

1. In Visual Studio, open the ConfigurationModularity QuickStart solution.

2. In the editor, open the DefaultViewA.xaml file from the ModuleA project.

3. Change the label text from "Module A Loaded" to "Module A Modified," as shown here.

   <Label VerticalAlignment="Center" HorizontalAlignment="Center">Module A Modified</Label>
   

4. Build the solution.

To create a copy of the previous application files folder on the deployment server

1. In Windows Explorer, open the publish folder's Application Files folder for the application (C:\inetpub\wwwroot\ConfigurationModularity\Application Files).
2. Right-click the folder that contains the previous version (ConfigurationModularity_1_0_0_0), and then click Copy.
3. Right-click in the right pane, and then click Paste.
4. Rename the new folder ConfigurationModularity_1_1_0_0.

To use the Manifest Manager Utility to update the manifests

1. Run the Manifest Manager Utility application.

2. On the File menu, click Open.

3. In the File Open dialog, navigate to the publish folder (C:\inetpub\wwwroot\ConfigurationModularity), select the **ConfigurationModularity.application **file, and then click Open.

4. In the Version box, type 1.1.0.0.

5. Next to the Application Manifest box, click Select.

6. Navigate to the ConfigurationModularity_1_1_0_0 folder, click ConfigurationModularity.exe.manifest, and then click Open.

7. In the list of files, select the row for ModuleA, and then click Delete Selected File on the Edit menu.

8. On the Edit menu, click Add Files.

9. In the Add Application Files dialog box, navigate, if necessary, to the build output folder's Modules subfolder for the ConfigurationModularity QuickStart solution (for example, C:\CompositeWPF\QuickStarts\Modularity\ConfigurationModularity\ConfigurationModularity\bin\Debug\Modules).

10. Select the ModuleA.dll file, and then click Open.

    In the Browse For Folder dialog box, expand the publish folder, expand the Application Files folder, expand the ConfigurationModularity_1_1_0_0 folder, select the Modules folder (see Figure 1), and then click OK.

    

    Figure 1
    Selecting the Destination Path for ModuleA.dll

11. On the File menu, click Save.

12. If the Path box does not already contain the correct certificate file path, click Browse, and then click the certificate file created by Visual Studio when you first published (for example, C:\CompositeWPF\QuickStarts\Modularity\ConfigurationModularity\ConfigurationModularity\ConfigurationModularity_TemporaryKey.pfx).

13. Click Sign and Save.

Outcome

You have a new version of the application published on the deployment server. The default deployment manifest (ConfigurationModularity.application) has been updated to point to that version, and the new files have been added to that version's application manifest. The new version is ready to be deployed and will be automatically detected by the client application the next time it is launched by the user.

Retired Content
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.