If you deploy a solution named ExcelWorkbook1 to the folder C:\DeployFolder, the file structure will look like this:

C:\DeployFolder

This folder contains the following two files and subfolder:

• The workbook (ExcelWorkbook1.xls).

• The deployment manifest (ExcelWorkbook1.application).

  C:\DeployFolder\ExcelApplication1_1.0.0.0

  This folder contains the following files:

  • The assemblies.

  • The application manifest (ExcelWorkbook1.dll.manifest).

  • A copy of the workbook.

  • A copy of the deployment manifest.

If you update the assembly and republish the solution, the directory structure will look like this:

C:\DeployFolder

This folder contains the following two files and subfolders:

• The workbook (with an updated embedded application manifest).

• The deployment manifest (updated to point to the application manifest in C:\DeployFolder\ExcelWorkbook1_1.0.0.1).

  C:\DeployFolder\ExcelWorkbook1_1.0.0.0

  This folder contains the following files:

  • The original assemblies.

  • The original application manifest.

  • The original workbook.

  • The original deployment manifest.

  C:\DeployFolder\ExcelWorkbook1_1.0.0.1

  This folder contains the following files:

  • The updated assemblies.

  • The updated application manifest.

  • A copy of the updated workbook.

  • A copy of the updated deployment manifest.

This structure will be repeated every time that you update the assembly. If you update the document or workbook so that it is no longer compatible with the existing assembly, you should deploy the solution to a new deployment folder.

You can also use MSBuild at a command prompt to publish your solution. When you use MSBuild at a command prompt, you can publish your solution files to one location, and simultaneously modify the application manifest embedded in the workbook or document to point to a deployment manifest at a different location. To run MSBuild at a command prompt to publish your solution, use the following syntax.

msbuild.exe /target:Publish /property:UpdateUrl=<update location> /property:PublishDir=<publish location> <project file>

For example, if you want to publish a C# project named ExcelWorkbook1 to the shared folder \\PublishServer\PublishFolder, but you expect to move the deployment manifest, external application manifest, and the assembly to the shared folder \\DeploymentServer\DeploymentFolder in the future, you would run the following command.

msbuild.exe /target:Publish /property:PublishDir=\\PublishServer\PublishFolder\ /property:UpdateUrl=\\DeploymentServer\DeploymentFolder\ C:\ExcelWorkbook1\ExcelWorkbook1.csproj

For more information about using MSBuild at a command prompt, see Building ClickOnce Applications from the Command Line.

You might change the deployment manifest for a solution several times during the lifetime of the solution. There are two main reasons why you would update the deployment manifest:

• You deploy a new version of the solution assembly. For more information, see How to: Update Deployed Assembly Files (2003 System).

• You change the location of the solution assembly. For more information, see How to: Change the Location of Document-Level Customizations (2003 System).

You might not ever have to directly update an existing application manifest that is in use in a solution. Usually, you create a new application manifest and use the deployment manifest to load the new application manifest into the solution. However, there are two main reasons why you might want to update an application manifest in a document directly:

• The deployment manifest and the assemblies have been moved to a new server because the original server is being taken out of service. In this case, you must change the paths to those items in the application manifest. For more information, see How to: Change the Location of Document-Level Customizations (2003 System).

• You want to remove the application manifest from the document. For example, you might want to archive the document and you do not want it to run code and possibly change, or you might want to send the completed document out of your workgroup without any reference to the code. For more information, see How to: Remove Managed Code Extensions from Documents (2003 System).