Create a Word Document project with the name WordDeployment. Make sure that Create a new document is selected. For more information, see How to: Create Visual Studio Tools for Office Projects.

In Solution Explorer, right-click the ThisDocument (for Word) code file and click View Code.

Add the following code in the ThisDocument_Startup event handler. This code displays a message when the document opens, which will make it easy to verify whether the solution has been deployed successfully.

MessageBox.Show("The deployment is successful")

MessageBox.Show("The deployment is successful");

For more information about the Startup event, see Visual Studio Tools for Office Project Events.

Press F5 to build and run the project. Verify that the message appears.

Create a new Console Application project. For more information, see How to: Create Solutions and Projects.

Add a reference to the Microsoft.VisualStudio.Tools.Applications.Runtime.dll assembly to the new project.

Add the following using statement (C#) or Imports statement (Visual Basic) to the top of the Program.cs or Module1.vb code file.

Imports Microsoft.VisualStudio.Tools.Applications.Runtime

using Microsoft.VisualStudio.Tools.Applications.Runtime;

Add the following code in the Main method to update the embedded application manifest. Replace <full document path> with the full path of the document in its build location on the development computer—for example, <project folder>\bin\debug\WordDeployment.doc. Replace <full assembly path> with the full path of the assembly in the network folder it will be deployed to—for example, \\DeploymentServer\DeploymentFolder\WordDeployment.dll.

Dim sd As ServerDocument = Nothing
Try
    sd = New ServerDocument("<full document path>")
    sd.AppManifest.Dependency.AssemblyPath = _
        "<full assembly path>"
    sd.Save()
Finally
    If Not sd Is Nothing Then
        sd.Close()
    End If
End Try

ServerDocument sd = null;
try
{
    sd = new ServerDocument(@"<full document path>");
    sd.AppManifest.Dependency.AssemblyPath = 
        @"<full assembly path>";
    sd.Save();
}
finally
{
    if (sd != null)
    {
        sd.Close();
    }
}

Build and run the project. The console application updates the assembly path in the embedded application manifest and then closes.

Note
Make sure that the document is not open in an instance of Word or the project designer. If the document is open, the attempt to access the document using ServerDocument will fail.

Close the Console Application project.

Create a folder named DeploymentFolder on a network computer, and share the folder to yourself. For example, if the network computer is named DeploymentServer, the new network share would be \\DeploymentServer\DeploymentFolder. Make sure that the network share has the same name that you specified in the <full assembly path> placeholder when you edited the embedded application manifest in the previous steps.

Copy the document and the assembly from the build output folder (typically <project folder>\bin\debug or <project folder>\bin\release) to the \\DeploymentServer\DeploymentFolder network share.

Open the document in the \\DeploymentServer\DeploymentFolder network share. You will see an error message that states that the customization assembly could not be found or could not be loaded. This is because you have not granted full trust to the document and the assembly in the network folder.

Click OK, and then close the document.

Click Start, point to All Programs, point to Accessories, and then click Command Prompt.

Type the following command to create a new code group that grants full trust to the assembly.

%windir%\Microsoft.NET\Framework\v2.0.50727\caspol -m -ag LocalIntranet_Zone -url "<full assembly path>" FullTrust -n "Test_Deployment_Assembly"

Replace <full assembly path> with the full path of the assembly in the network folder—for example, \\DeploymentServer\DeploymentFolder\WordDeployment.dll.

The -n parameter specifies a name for the new code group. This parameter is not required, but specifying a label makes it easier to later identify and remove the new code group after you complete this walkthrough.

Type yes when prompted to confirm that you want to perform the operation, and press ENTER.

Type the following command to create a new code group that grants full trust to the document and then press ENTER. You must grant full trust to the document because you as the end user will open it from the network folder. Documents do not require full trust if they are on the end user computer.

%windir%\Microsoft.NET\Framework\v2.0.50727\caspol -m -ag LocalIntranet_Zone -url "<full document path>" FullTrust -n "Test_Deployment_Document"

Replace <full document path> with the full path of the document in the network folder—for example, \\DeploymentServer\DeploymentFolder\WordDeployment.doc.

The -n parameter specifies a name for the new code group. This parameter is not required, but specifying a label makes it easier to later identify and remove the new code group after you have completed this walkthrough.

Type yes when prompted to confirm that you want to perform the operation, and press ENTER.

On your development computer, open the document in the \\DeploymentServer\DeploymentFolder network folder and verify that the message appears.

Save the document to a folder the development computer, and then close the document.

Open the document on the development computer, and verify that the message appears.

This works because the embedded application manifest includes the full path of the assembly on the network computer. If you did not edit the path of the assembly in the embedded application manifest, the solution would run only if you open the document from the network folder.

Click OK, and then close the document.