none
How to a run Word 2010 Document-Level Addin from Template which is installed in Program Files Folder? RRS feed

  • Question

  • Hi!

    I'm trying to deploy a Word 2010 / .NET 4.0 document-level addin using MSI to the program files folder. When I open the template, the addin does not get loaded, although I even added the installation path as trusted location. When I install the template to some non-special folder like D:\Temp the addin loads without problems.

    Are there some limitations regarding the program files folder which I'm not aware of and how can I achieve correct loading of the plugin from the program files folder?

    Best Regards,
    Oliver Hanappi 

    Friday, December 9, 2011 2:06 PM

Answers

  • I think the user would have to have system administrator rights in order to have the document level add-in work from the Program Files directory.  That was a change that came about with Office 2007. 
    Kind Regards, Rich ... http://greatcirclelearning.com
    Tuesday, December 13, 2011 1:03 PM
  • I managed to get it working by using ServerDocument.AddCustomization during the installation process to decouple the document location from the dll location by specifying the absolute path to the installation directory. Even though the document is still located in the installation directory, it works now. Details under http://msdn.microsoft.com/de-de/vsto/ff937654.aspx (see Changing the Location of the Deployed Document).

    Regards,
    Oliver Hanappi 

    Friday, January 27, 2012 5:07 PM

All replies

  • Hi Oliver,

     

    Thanks for posting in the MSDN Forum.

     

    I tried to reproduce your issue on my side. I never see the situation like your description. The document-level application works fine after I installed it to program files folder. Did you try it on other computers?

     

    Have a good day,

     

    Tom


    Tom Xu [MSFT]
    MSDN Community Support | Feedback to us
    Tuesday, December 13, 2011 9:22 AM
    Moderator
  • I think the user would have to have system administrator rights in order to have the document level add-in work from the Program Files directory.  That was a change that came about with Office 2007. 
    Kind Regards, Rich ... http://greatcirclelearning.com
    Tuesday, December 13, 2011 1:03 PM
  • I managed to get it working by using ServerDocument.AddCustomization during the installation process to decouple the document location from the dll location by specifying the absolute path to the installation directory. Even though the document is still located in the installation directory, it works now. Details under http://msdn.microsoft.com/de-de/vsto/ff937654.aspx (see Changing the Location of the Deployed Document).

    Regards,
    Oliver Hanappi 

    Friday, January 27, 2012 5:07 PM