Deployment of office application vsto Software

Vsto Program Prerequisites for correct operation

Install the following content:

Vs2008Developed Components

. NET Framework 3.0/3.5

Vsto runtime environment 3.0

Office Pia installer [install the Office installer or an independent installation package, Office 2003/2007], office2003 requires special attention, the corresponding patch needs to be installed

 

Vs2010Developed Components

. NET Framework 4.0

Vsto runtime environment 4.0

Office Pia installer [install the Office installer or an independent installation package, office version 2007/2010]

 

Simple installation and logout Methods

Take a. vsto as an Example

Install

"% ProgramFiles % \ common files \ microsoft shared \ vsto \ 9.0 \ vstoinstaller.exe"/I "% Cd % \ A. vsto"

"% ProgramFiles % \ common files \ microsoft shared \ vsto \ 10.0 \ vstoinstaller.exe"/I "% Cd % \ A. vsto"

 

Uninstall

"% ProgramFiles % \ common files \ microsoft shared \ vsto \ 9.0 \ vstoinstaller.exe"/u "% Cd % \ A. vsto"

"% ProgramFiles % \ common files \ microsoft shared \ vsto \ 10.0 \ vstoinstaller.exe"/u "% Cd % \ A. vsto"

 

Registry Association

After the vsto program is installed, the corresponding component name item under the Registry HKEY_CURRENT_USER \ Software \ Microsoft \ Office \ word \ addins \ [word for example, Excel outlook is similar], the loadbehavior controls the loading behavior. The values that can be assigned include:

0 disconnected. the add-in is not loaded.

1 connected. The add-in is loaded.

2 load at startup. the add-in will be loaded and connected when the host application starts.

8 load on demand. the add-in will be loaded and connected when the host application requires it (for example, when a user clicks a button that uses functionality in the add-in ).

16 connect first time. the add-in will be loaded and connected the first time the user runs the Host application after registering the add-in.

Generally, 3 is the value of 1 and 2. After a component exception occurs, the value is automatically changed to 2. In this case, you need to manually or program the settings, in order to see the display of components normally.

 

Using these methods, you can check the cause of component not loading on faulty machines.