Note: There are other Quick Starts in this series, including:
Please send us your feedback on these Quick Starts!
This Quick Start demonstrates how to deploy a Microsoft Visual Studio 2005 Tools for the Microsoft Office System solution for Microsoft Office Word 2003 or Microsoft Office Excel 2003 so that the document and the assembly are located in different folders on the end user computer. This Quick Start is intended for users who have little or no experience with deploying Visual Studio 2005 Tools for Office solutions.
This Quick Start includes the following sections:
This Quick Start assumes the end user computer already has the following prerequisites installed for running Visual Studio 2005 Tools for Office solutions:
This Quick Start does not show you how to install these prerequisites on the end user computer. For more information about the prerequisites, see How to: Prepare End User Computers to Run Office Solutions.
Creating a Solution to Deploy
In the following steps, you will create a basic Visual Studio 2005 Tools for Office solution to deploy. If you already have a solution that you want to deploy, you can skip this section and proceed to the Deploying the Solution section.
Deploying the Solution
In the following steps, you will deploy the document and assembly to different folders on the end user computer.
Setting Security Policy
In the following steps, you will grant full trust to the assembly in the .NET Framework 2.0 security policy of the end user. This Quick Start shows how to grant full trust to the assembly using the Code Access Security Policy tool (Caspol.exe). For more information about using Caspol.exe, see Code Access Security Policy Tool (Caspol.exe) and Configuring Security Policy Using the Code Access Security Policy Tool (Caspol.exe).
Security Note: These are basic steps for setting a security policy based on URL evidence for the purpose of completing this Quick Start. Do not use these steps to grant trust to assemblies in a real-world solution if you are not certain that the location is safe and secure. You should also base the security of a real-world solution on more evidence than the URL of the assembly. For more information, see Security Requirements to Run Office Solutions.
To grant full trust to the assembly:
There are many other ways to deploy Visual Studio 2005 Tools for Office solutions, such as deploying the document and assembly to a remote computer or using a deployment manifest to enable automatic assembly updates. Refer to the following topics in the Visual Studio 2005 Tools for Office documentation more detailed information about deploying solutions.
For more information about deployment models for for Word and Excel solutions, see:
For more information about the embedded application manifest, see:
For more information about security in Visual Studio 2005 Tools for Office solutions, see:
-- McLean Schofield
-----This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm.