Manual: 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 manually publish a new version of an application on the deployment server, you will perform the following steps:

1. Create a copy of the previous version's Application Files folder.
2. Copy the updated module into the new folder.
3. Update the version and application files list in the application manifest using the Visual Studio 2008 SDK tool named Manifest Generating and Editing tool (Mage).
4. Update the version and application reference in the deployment manifest using Mage.

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 copy the ModuleA.dll file into the new folder

1. Copy the ModuleA.dll file from the ConfigurationModularity build output folder's Modules subfolder (for example, C:\CompositeWPF\QuickStarts\Modularity\ConfigurationModularity\ConfigurationModularity\bin\Debug\Modules).
2. Paste the file into the new version's application files directory (C:\inetpub\wwwroot\ConfigurationModularity\Application Files\ ConfigurationModularity_1_1_0_0), overwriting the existing file.

To update the application manifest

1. Run the Mage tool (in a Visual Studio 2008 command prompt window, type mage).

2. On the File menu, click Open.

3. Navigate to the new version's subfolder under the publish folder (C:\inetpub\wwwroot\ConfigurationModularity\Application Files\ ConfigurationModularity_1_1_0_0), and then click the new version's application manifest (ConfigurationModularity.exe.manifest).

4. In the Version box, type 1.1.0.0.

5. In the left pane, click Files.

6. In the right pane, click Populate.

7. When prompted about renaming files, click OK.

8. If prompted about renaming files to overwrite the ConfigurationModularity.application.deploy file, click No to not overwrite.

   Note

   Error: Note format was corrupted. Title should be bold.You may want to open the folder and remove the file name extension .deploy from the .application file because it is not intended for deployment.

9. Select the first row in the grid (ConfigurationModularity.application.deploy), and then press the DELETE key.

10. On the File menu, click Save.

11. Click the ellipsis button (...) next to the File box for selecting a publisher certificate file.

12. Navigate to the publisher certificate that was generated by Visual Studio when you first published from there (for example, C:\CompositeWPF\QuickStarts\Modularity\ConfigurationModularity\ConfigurationModularity\ConfigurationModularity_TemporaryKey.pfx), and then click it.

13. Click OK.

To update the deployment manifest

1. On the Mage toolbar, click Open.
2. Navigate to the publish folder (C:\Inetpub\wwwroot\ConfigurationModularity), click the default deployment manifest (ConfigurationModularity.application), and then click Open.
3. In the Version box, type 1.1.0.0.
4. In the left pane, click Application Reference.
5. Click the Select Manifest button.
6. Navigate to the new version's application manifest (C:\inetpub\wwwroot\ConfigurationModularity\Application Files\ConfigurationModularity_1_1_0_0\ConfigurationModularity.exe.manifest), click it, and then click Open.
7. On the File menu, click Save.
8. Click the ellipsis button (...) next to the File box for selecting a publisher certificate file.
9. Navigate to the publisher certificate that was generated by Visual Studio when you first published from there (for example, C:\CompositeWPF\QuickStarts\Modularity\ConfigurationModularity\ConfigurationModularity\ConfigurationModularity_TemporaryKey.pfx), click it, and then click OK.
10. Close Mage.

Outcome

You will have a new version of the application published on the deployment server. The default deployment manifest (ConfigurationModularity.application) will be updated to point to that version and the new files will 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.