ServerDocument.AddCustomization Method (String, String, Guid, Uri)
Attaches a customization to the specified document by using the specified document, assembly name, solution ID, and deployment manifest.
Assembly: Microsoft.VisualStudio.Tools.Applications.ServerDocument (in Microsoft.VisualStudio.Tools.Applications.ServerDocument.dll)
'Declaration Public Shared Sub AddCustomization ( _ documentPath As String, _ assemblyName As String, _ solutionId As Guid, _ deploymentManifestUrl As Uri _ )
- Type: System.String
The full path of the document to which you want to attach a customization.
- Type: System.String
The full path of the assembly for the customization. The path must be on the local file system or a UNC share; you cannot specify an HTTP location.
- Type: System.Guid
A GUID that the Visual Studio Tools for Office runtime uses to identify the solution.
- Type: System.Uri
The URL of the deployment manifest for the solution.
documentPath or assemblyName is Nothing or empty.
documentPath or assemblyName refers to a file that does not exist.
The document specified by documentPath already has a customization.
The document specified by documentPath is corrupt, or has restricted permissions.
The document specified by documentPath has a file name extension that is not supported by the Visual Studio Tools for Office runtime.
The AddCustomization method associates the specified customization with the document by adding the _AssemblyName and _AssemblyLocation custom document properties to the document. These properties identify that the document has a customization and specify the location of the deployment manifest. After this method is successfully called, the next time a user opens the specified document, the runtime attempts to install the Office solution. For more information about the custom document properties, see Custom Document Properties Overview.
The GUID that you pass to the solutionID parameter is specified in the application manifest of the solution that you are attaching to the document. You must pass the same GUID that is specified in the solutionId attribute of the vstov4:document element in the application manifest. For more information, see Application and Deployment Manifests in Office Solutions and <document> Element (Office Development in Visual Studio).
If you are attaching a customization from a publish location, make sure that you specify the correct file name for the assembly in the assemblyName parameter. When you publish an Office solution, the assembly that is copied to the publish folder has the .deploy file name extension. For example, if the assembly name is WordDocument1.dll, the file name of the assembly in the publish folder is WordDocument1.dll.deploy. For more information, see Deploying an Office Solution by Using ClickOnce.
If the specified document does not contain a control that the customization expects the document to have, the AddCustomization method will succeed, but the assembly will fail to load when the user opens the document.
The fileType parameter must specify a document that has a file name extension that is supported for document-level customizations for Microsoft Office Word and Microsoft Office Excel. You cannot attach a customization to a document that is saved in the Word XML Document (*xml) or Word 2003 XML Document (*xml) file formats. For more information about the supported file types, see Architecture of Document-Level Customizations.
The following code example uses the AddCustomization method to attach a customization to the specified document.
This example requires:
A console application project or some other non-Office project.
References to the following assemblies:
Microsoft.VisualStudio.Tools.Applications.ServerDocument.dll and Microsoft.VisualStudio.Tools.Applications.Runtime.dll (if the project targets the .NET Framework 4 or the .NET Framework 4.5).
Microsoft.VisualStudio.Tools.Applications.ServerDocument.v10.0.dll and Microsoft.VisualStudio.Tools.Applications.Runtime.v9.0.dll (if the project targets the .NET Framework 3.5).
Private Sub AddCustomizationUsingAssemblyPath(ByVal documentPath As String, _ ByVal assemblyName As String, ByVal solutionID As Guid, ByVal deployManifestPath As String) Dim runtimeVersion As Integer = 0 Try ' Make sure that this document does not yet have any Visual Studio Tools ' for Office customizations. runtimeVersion = ServerDocument.GetCustomizationVersion(documentPath) If runtimeVersion = 0 Then Dim deploymentManifestUri As New Uri(deployManifestPath) ServerDocument.AddCustomization(documentPath, assemblyName, solutionID, deploymentManifestUri) MessageBox.Show("The document was successfully customized.") Else System.Windows.Forms.MessageBox.Show("The document is already customized.") End If Catch ex As System.IO.FileNotFoundException System.Windows.Forms.MessageBox.Show("The specified document does not exist.") Catch ex As UnknownCustomizationFileException System.Windows.Forms.MessageBox.Show("The specified document has a file " & _ "extension that is not supported by Visual Studio Tools for Office.") Catch ex As DocumentNotCustomizedException System.Windows.Forms.MessageBox.Show("The document could not be customized." & _ vbLf & ex.Message) End Try End Sub
- Full trust for the immediate caller. This member cannot be used by partially trusted code. For more information, see Using Libraries from Partially Trusted Code.