22 Answers Found
make sure u r client got admin privileage.
Yes, the client has got admin privilege. The client computer (that I have tested) is another computer other than development computer in our office.
I have tested the Excel Addin setup by building the project given in the vsto 3.0 Runtime samples directory. It is installed successfully. When I opened the Excel 2007 application, the ExcelAddin.vsto file launched automatically and asked for installation.
However, the word Addin that I developed in the similar way as Excel Addin is installed, but when I open Word 2007 application, the WordAddin.vsto file is not being launched automatically.
what is the OS u r client using,If its Vista,Win7 u need to fallow some steps to overcome the security.
Can you provide the error details.and also make sure value are present in registry as defined in the above documents
I'm not sure that you're not mixing up the two types of deployment: .msi vs. ClickOnce. If I'm not mistaken, a *.vsto file is only generated for a ClickOnce type of deployment, and can only work with ClickOnce.
The links to which you point describe how to create a setup (.msi) type of deployment, which is more complex, but also provides more flexibility.
You need to use one, or the other.
If a *.msi type of setup installs correctly, the Add-in should be registered and Word should load it automatically (and transparently) when Word is launched. There should be no need of a *.vsto file.
If *.vsto is not required for deployment, then what should be value for the Registry Entry "Manifest" (I have given the .vsto file's path as value "[TARGETDIR]Word2007AddIn.vsto|vstolocal").
Do we not need to package the *.vsto file in the Setup project?
What should we include in the Security Policy? Currently, I am giving the <RSAKeyValue> found in the *.vsto file?
My mistake - I misread something in your original message. Please ignore my reply!
But I did not get the solution for the issue. All the files 'WordAddin.dll', 'WordAddin.dll.manifest', ''WordAddin.vsto' are installed in a location and the *.vsto is added in the inclusion list.
The same process is working with ExcelAddin. However, for the word after launching Word Application, the Windows Customization Installer is not launching.
Even the Word Addin is not appearing in the list 'Active Application Add-ins' of Word 2007 application.
Can anybody help on this?
What do you see as a LoadBehavior value in HKCU\Software\Microsoft\Office\Excel\Addins\<AddIn Name>
Do you have office 2007 PIA's installed? What about VSTO Runtime 3.0?
Can you please run
VSTO Troubleshooter and then check if all the pre-requisites are available on the machine?
To troubleshoot the issue further can you please set VSTO_SUPPRESSDISPLAYALERTS value to 0. For more details follow MSDN article
Debugging in Application-Level Projects
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
The value of the LoadBehavior is 3 in the registy entry for the addin.
All the prerequisites are correctly installed. If i click on the "addin.vsto" file manually, the addin is being installed. But it is not being done programatically as said in this
The same Excel Addin mentioned in the above walkthrough works well and is being installed successfully.
But, the Word Addin I developed with all the similar steps mentioned in the walkthrough, its not being installed. First of all, on opening the Word 2007 application, the dialog 'Microsoft Office Customization Installer' is not being launched automatically
as shown in the walkthrough.
I want to know, if any thing more is to be done in the Setup Project for installing Word Addin.
Did you run VSTO Troubleshooter? What were the results.
Did you add VSTO_SUPPRESSDISPLAYALERTS environment variable?
Yes, I have run VSTO Troubleshooter and please check the status here -
The LoadBehaviour value is 3. I have added VSTO_SUPPRESSDISPLAYALERTS environment variable and set to 0. But no error message is shown when Word 2007 is opened.
Are you deploying the add-in to HKCU\Software\ or HKLM\Software\ ??
I am deploying addin to
what version of Visual Studio are you using to develop your add-in and setup project? as others have asked, are you deploying to HKLM or HKCU? is the test computer 32-bit or 64-bit?
if the vsto 3.0 MSI deployment sample is working, that computer already has all the prerequisites installed and the VSTO troubleshooter won't really tell you much.
if you are using VS2008 SP1, can you look in the event viewer and see if there are any exception messages logged by the VSTO runtime.
I have created a wordaddin following the exact steps as mentioned ,it works perfectly for me.
u can validate the registry entry as shown below
Registry path- HKCU\Software\Microsoft\Office\Word\Addins\MywordAddin
FriendlyName,Description of type String value MywordAddin
LoadBehavior of type DWORD value 3
Manifest of type String value [TARGETDIR]MywordAddin.vsto|vstolocal
Make sure u have included .dll.manifest and .vsto files
Also can u check Event log for more on error details
Does the Microsoft Office Customization Installer popup window is being launched automatically after opening word application on your computer?
I want to clearly say that all the things registry entries, prerequisites are the add-in files .dll, .dll.manifest, .vsto are
perfectly installed on my computer. Even the registry entry for including the add-in in the inclusion list is perfectly added.
The only problem is the Microsoft Office Customization Installer popup window is not being launched automatically after opening word application. I have to manually select the .vsto file to install the add-in.
But I cannot provide for a client an installation file that he has to install manually.
just by chance
Try to check disabled add-in in MS Word options
1, Office button
2, Word options
4, in the combobox bellow select "Disabled items" and then the click on the button "Go"
5, check if there is any
The only problem is the Microsoft Office Customization Installer Popup Window (that installs add-in into word) is not launching automatically after opening word 2007 (as mentioned in the Walkthrough
Deploying a Visual Studio Tools for the Office System 3.0 Solution for the 2007 Microsoft Office System Using Windows Installer (Part 1 of 2) ).
the Microsoft Office Customization Installer dialog box appears to the end user if the certificate used to sign the application and deployment manifests are not already trusted on the end user's computer. the inclusion list APIs grants this pre-trust to
so if you are using the inclusion list APIs and the dialog box is still appearing, the inclusion list APIs are not being used correctly. if you are using the inclusion list APIs and the dialog box is NOT appearing, the inclusion list APIs are being used
First of all, I want to understand why the Microsoft Office Customization Installer Popup Window is launching in Excel and not launching for Word automatically.
Please confirm this.
every time you create a new Office solution, such as a different Excel or Word add-in, Visual Studio generates a new temporary certificate (.pfx). each certificate has a different thumbprint. if you are using the exact same inclusion list code
for both the Excel add-in and Word add-in, you are only pre-trusting one of the certificates and the other one still remains untrusted - which is why you only see the Microsoft Office Customization Installer dialog box once.
if you want the dialog box to appear for both Excel and Word, just remove the InclusionListCustomAction from your setup projects and simplify your deployment.
The only difference between deploying an Excel add-in and a Word add-in is the registry key that you add (HKCU\Software\Microsoft\Office\Word\Addins\). if you can get your Excel add-in to deploy correctly, repeat the same steps for a Word add-in.
Thank you Mary. I have verified all the project thoroughly each and every step.
I found that I have done a mistake in registry entry that I misspelled the entry 'LoadBehavior' as 'LoadBehaviou r'. Due to this the Word application is unable to load the add-in.
I thank all who answered me. I learnt a lot from all of you.
I see a problem doing things this way (add entries manually into registry). Let's say we create a sample Addin (ISAddin). Inorder to deply to my client system, I prepare a MSI and make the entries in registry
CommandLineSafe - 3
Description - ISAddin
FriendlyName - ISAddin
LoadBehavior - 3
Manifest - C:\Program Files(x86).....\ISAddin.vsto
All goes well and the user can see the ribbon(I created in the VSTO project) and menus in it. But then if there are any calls in my implementation like the following -
isf = IsolatedStorageFile
, API keeps failing...I am not sure why. Try the same with ClickOnce installation, it works like Gem. Can some tell me if I am missing something.