Share via

Automated: Publishing an Initial Version of an Application

  • Article
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:

  • Composite Application Guidance must be downloaded and unpacked to a folder.
  • Internet Information Services (IIS) must be installed.
  • The ManifestManagerUtility solution must be built.
  • The Modularity\ConfigurationModularity QuickStart 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

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 add the additional modules using the Manifest Manager Utility

  1. Run the ManifestManagerUtility.exe utility.

  2. On the File menu, click Open.

  3. Browse to and select the published deployment manifest (C:\Inetpub\wwwroot\ ConfigurationModularity \ConfigurationModularity.application).

    The commonly modified values from the deployment manifest and the list of files from the referenced application manifest will be loaded into the utility (see Figure 1).

    Ff921130.434cd755-7214-4ac9-8983-5b921042797a(en-us,PandP.10).png

    Figure 1
    Manifest Manager Utility

  4. On the Edit menu, click Add Files.

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

  6. Select the following files to add them to the application manifest, and then click Open:

    • ModuleA.dll
    • ModuleB.dll
    • ModuleC.dll
    • ModuleD.dll

  7. In the Browse For Folder dialog box that allows you to select target location shown in Figure 2, navigate to the publish folder for the application, expand the tree to the version-specific Application Files folder, add a subfolder named Modules using the Make New Folder button, select the Modules folder, and then click OK.

    Ff921130.6f85fb58-523f-47c5-936d-139e05bd0292(en-us,PandP.10).png

    Figure 2
    Browse For Folder dialog box

  8. On the File menu, click Save.

  9. In the Select Publisher Certificate to Sign Manifest dialog box, click Browse, and then navigate to the publisher certificate that was generated by Visual Studio when you first published the application (for example, C:\CompositeWPF\QuickStarts\Modularity\ConfigurationModularity\ConfigurationModularity\ConfigurationModularity_TemporaryKey.pfx). Figure 3 illustrates this dialog box.

    Ff921130.d5468a48-fb41-4ba5-9019-8a7bc027252b(en-us,PandP.10).png

    Figure 3
    Manifest signing dialog box

  10. Click Save and Sign.

Outcome

The published ConfigurationModularity application is ready for users to launch. In this case, you would provide them with a link to http://<yourmachinename>/ConfigurationModularity/ConfigurationModularity.application. The downloaded application will include the ConfigurationModularity QuickStart modules that are dynamically loaded based on the application configuration file.

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.