Partilhar via

Manual: Publishing an Initial Version of an Application

  • Artigo
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.

This topic describes how to publish an initial version of a ConfigurationModularity QuickStart application using the .NET Framework 3.5 SDK Manifest Generating and Editing tool (Mage).

Prerequisites

This topic requires the following:

  • Composite Application Guidance must be downloaded and unpacked to a folder.
  • Internet Information Services (IIS) must be installed.
  • The ConfigurationModularity QuickStart application solution must be built.

Note

If you are using Internet Information Services 7.0 (IIS7), the IIS 6 Metabase and IIS 6 Configuration Compatibility component is also required. To deploy the application from IIS7, you will need to change the Application Pool basic setting for the virtual directory to the Classic .NET AppPool instead of the Default .NET AppPool.

Steps

You will publish the ConfigurationModularity QuickStart application with the following steps:

  1. In Visual Studio, set the project publish settings and publish the ConfigurationModularity QuickStart application.
  2. Copy the additional module files to the publish application files directory.
  3. Update the application manifest using Mage.
  4. Update the deployment manifest using Mage.

You first need to publish the ConfigurationModularity QuickStart application from Visual Studio to generate the manifests and to publish the application outputs as application files.

To publish the ConfigurationModularity QuickStart application from Visual Studio

  1. In Visual Studio, open the ConfigurationModularity QuickStart solution.
  2. Right-click ConfigurationModularity, and then click Properties.
  3. Click the Publish tab.
  4. Change the** **Publishing Location folder to https://localhost/ConfigurationModularity/.
  5. Click Updates.
  6. Select the The application should check for updates check box if it is not already selected.
  7. Select the Before the application starts option if it is not already selected.
  8. Click Publish Now.

The project will be built and published to the location specified.

To copy the additional module files to the publish folder

  • Copy the following files from the build output folder's Modules subfolder (for example, C:\CompositeWPF\QuickStarts\Modularity\ConfigurationModularity\ConfigurationModularity\bin\Debug\Modules) to the publish folder's application files folder (C:\inetpub\wwwroot\ConfigurationModularity\Application Files\ConfigurationModularity_1_0_0_0\Modules):
    • ModuleA.dll
    • ModuleB.dll
    • ModuleC.dll
    • ModuleD.dll

To update the application manifest using Mage

  1. Open a Visual Studio 2008 command prompt, type mage, and then press ENTER.

  2. On the Mage toolbar, click Open a manifest file.

  3. In the published application files folder (C:\inetpub\wwwroot\ConfigurationModularity\Application Files\ConfigurationModularity_1_0_0_0), click the application manifest (ConfigurationModularity.exe.manifest), and then click Open.

  4. In the left pane, click Files.

  5. Click the Populate button (see Figure 1).

    Ff921094.e958823d-36a7-469c-97f7-d8bfdb7eb996(en-us,PandP.10).png

    Figure 1
    Mage application manifest files

  6. In the** This will permanently rename files** dialog box, click OK.

  7. Find the ConfigurationModularity.application.deploy file in the list of files, select the row, and then press the DELETE key to remove the item from the list of application files.

    Note

    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.

  8. On the File menu, click Save.

  9. In the Signing Options dialog box, click the ellipsis button (...), navigate to the publisher certificate that was generated by Visual Studio when you first published from there (for example, C:\temp\QuickStarts\Modularity\ConfigurationModularity\ConfigurationModularity\ConfigurationModularity_TemporaryKey.pfx), and then click it.

  10. Click OK to save and sign the manifest.

To update the deployment manifest using Mage

  1. On the Mage toolbar, click Open a manifest file.

  2. Navigate to the root publish folder (C:\inetpub\wwwroot\ConfigurationModularity\ConfigurationModularity.application), and then click ConfigurationModularity.application.

  3. In the left pane, click Application Reference (see Figure 2).

    Ff921094.e89ec2e8-5adc-4065-b5b7-6eae0bfb4057(en-us,PandP.10).png

    Figure 2
    Mage deployment manifest application reference

  4. In the right pane, click Select Manifest, navigate to the Application Files\ConfigurationModularity_1_0_0_0 subfolder of the publish folder, and then click ConfigurationModularity.exe.manifest.

  5. In the main Mage window, click Save.

  6. Click the ellipsis button (...), and then select the same publisher certificate (.pfx file) as you did in the previous procedure.

  7. In the Signing Options dialog box, click OK.

  8. Close Mage.

Outcome

The ConfigurationModularity QuickStart application will be ready to deploy through ClickOnce. You will be able to provide a link to the deployment manifest to your users and they will be able to click the link to download and launch the application on their computers.

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.