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. |
If your Visual Studio Tools for Office solution must be usable offline, you have two main options:
Deploying to Each User's Computer
To deploy a document-level customization to each end user's computer
To deploy an application-level add-in to each end user's computer
Update the application manifest that is created when you build the solution so that it uses an environment variable to point to the assembly. Instead of using a specific drive letter and path, use %ProgramFiles% or %UserProfile% to begin the path. For example, the path might look like this: %ProgramFiles%/MyAddIn/MyAddIn.dll
The assembly path is specified by the codebase attribute of the installFrom element, which is a child of the dependency element. For more information, see <installFrom> Element (Visual Studio Tools for Office Reference).
Copy the assembly and the application manifest to each end user's computer. You can use the default Setup project that is included with your add-in project. For more information, see Setup Projects for Application-Level Add-ins (2003 System).
.gif) Note: |
|---|
To set an environment variable on the user's computer during installation, add a value to the key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment. The user must restart the computer after installation before the new value is recognized. |
Update the security policy on the computer to grant full trust to the assembly, and to any dependent assemblies. For more information, see How to: Grant Permissions to Folders and Assemblies (2003 System).
Deploying to a Web Server
You can deploy an assembly to a network location and still make it available to the user's local computer for offline use. The assembly must be located on a Web server and accessed through an HTTP or HTTPS path. You cannot use a UNC path or mapped network drives for offline solutions, unless you use IntelliMirror to synchronize folders instead of relying on the Internet Explorer cache. For more information, see Offline Model for Office Solutions (2003 System).
The application manifest and deployment manifest must use the correct HTTP or HTTPS path to the assembly. If you use the Publish Wizard, the manifests are created for you. For more information, see Deploying Document-Level Customizations (2003 System) and Deploying Application-Level Add-Ins (2003 System).
To set the assembly path
Tasks
Concepts
Other Resources