Deployment and installation of the vsto Program

Many things need to be installed when you use Windows installer to install the vsto program: (1) Ensure that the client has installed the program on the machine. net2.0framework (2) office2003 (vsto supported) (3) install the main interoperability assembly (PIA) from Http://www.microsoft.com/downloads/details.aspx? Familyid = 3c9a983a-ac14-4125-8ba0-d36d67e0f4ad & displaylang = enYou can also install the SDK by following these steps:

Install main office interoperability assembly

1. On the Control Panel, select add or delete programs ".
2. In the "currently installed programs" list, select "Microsoft Office ".
3. Click Change ".
4. Select "add or delete function" and click "Next ".
5. Select "select Advanced Application Customization" and click "Next ".
6. Expand Microsoft Office Excel, click the box next to. Net programmable support, and then click Run from local machine ".
7. Expand Microsoft Office outlook, click the box next to. Net programmable support, and then click Run from local machine ".
8. Expand Microsoft Office Word, click the box next to. Net programmable support, and then click Run from local machine ".
9. Expand office tools, click the box next to Microsoft forms 2.0. Net programmable support, and then click Run from local machine ".
10. Under office tools, click the box next to smart tag. Net programmable support, and then click Run from local machine ".
11. Under office tools, expand Microsoft Graph, click the box next to. Net programmable support, and then click Run from local machine ".
12. Install the main interoperability assembly for any other office application as needed.
13. Click Update ".

The main interoperability assembly is immediately installed in the global assembly cache.

(4) install the vsto Runtime Library:

Install the Runtime Library

1. Install. NET Framework 2.0 on the end user's computer. Install the. NET Framework before installing the Visual Studio Tools for office Runtime Library.
2. Run vstor.exe on the end user's computer. Vstor.exe is located in the installation media of Visual Studio Tools for office, or from the Microsoft download center (Http://go.microsoft.com/fwlink? Linkid = 49612 & clcid = 0x409) To obtain the reusable package.
3. If Windows has non-English settings, you can install the Visual Studio Tools for office Language Pack to view the message of the Visual Studio Tools for office Runtime Library in the language used by windows. If an end user runs a solution on a Windows system that uses non-English language settings, the Language Pack is required to view the runtime messages in a Windows language. Visual Studio Tools for office language packs can be downloaded from the Microsoft download center (Http://www.microsoft.com/downloads/details.aspx? Familyid = d64ba959-82c5-42cd-9af7-bd57f6eff12c & displaylang = ZH-CN.

(5) grant full trust 1. Configure and deploy. NET Framework 2.0First, you must fully trust the document and assembly.. NET Framework 2.0 is deployed below the configuration and must be deployed to the security level of the computer. It is invalid to deploy it to the user level. Computer -- code group -- all code right-click all code to create a security policy. Generally, the URL and site conditions are met. When selecting a site, you only need to enter the site name. You can also use * to replace all file URLs in a directory to set the path of DLL and XML files. The DLL files cannot be copied from the SharePoint website, so they can only be placed on the server's hard disk, allow remote calls from the client. Set permissions to fulltrust (full trust) Ii. Packaging of security policies:Right-click the security policy of the running database, create a deployment package, and select the computer level. After adding the name of the deployment package, you only need to double-click the package during installation. After the installation is successful, no prompt will appear. If the above program has been correctly configured and the plug-in has not been correctly loaded, I can't solve it. It is probably another bug of Microsoft, after the above configuration, the plug-in can be correctly loaded.