How to: Deploy Solution Files Using the Publish Wizard (2003 System)
Applies to |
|---|
The information in this topic applies only to the specified Visual Studio Tools for Office projects and versions of Microsoft Office. Project type
Microsoft Office version
For more information, see Features Available by Application and Project Type. |
The Publish Wizard enables you to deploy Visual Studio Tools for Office solutions to a Web site, network file share, or your local computer. It automatically creates an application manifest and a deployment manifest for the solution during the first deployment, or updates existing manifests.
To use the Publish Wizard to publish directly to the final deployment location, you must have permission to write to the deployment location. If business procedure requires separation of development and deployment, an IT administrator must deploy to the final location manually. For more information, see How to: Deploy Solution Files Manually (2003 System).
Note
Your computer might show different names or locations for some of the Visual Studio user interface elements in the following instructions. The Visual Studio edition that you have and the settings that you use determine these elements. For more information, see Visual Studio Settings.
To deploy office solutions using the Publish Wizard
Right-click the project node in Solution Explorer.
Click Publish on the shortcut menu.
The Publish Wizard appears.
In the Specify the location to publish this application box, type the path to the folder where you want to deploy the solution. Optionally, you can click Browse and navigate to the folder using the dialog box that appears.
If you have Internet Information Services (IIS) installed on your development computer, the Specify the location to publish this application box displays https://localhost/project name/ by default. Otherwise, this box displays \publish by default. The \publish folder is located in the project folder.
Verify that the path is correct, and then click Finish.
The document, assemblies, and manifests are copied to the publish location, with the assemblies and application manifest in a subdirectory under the document and deployment manifest. For more information, see Deploying Document-Level Customizations (2003 System) and Deploying Application-Level Add-Ins (2003 System).
Make changes to security policy so that each end user can run the solution. For more information, see Security Requirements to Run Office Solutions (2003 System).
Note
If you publish the solution to a folder under https://localhost and you want to run the solution from the development computer, you must grant full trust to the assembly by specifying the computer name in the assembly path, instead of "localhost". For example, if you publish a solution to https://localhost/ExcelWorkbook1, you must specify the path http://computer name/ExcelWorkbook1 when you grant full trust to the assembly.
See Also
Tasks
How to: Deploy Office Solutions (2003 System)
How to: Deploy Solution Files Manually (2003 System)
How to: Deploy for Offline Use of Documents (2003 System)
Concepts
Deploying Document-Level Customizations (2003 System)
Deploying Application-Level Add-Ins (2003 System)
Deploying Office Solutions (2003 System)