locked
VSTO 2007 Word Addin Deployment and Installation RRS feed

  • Question

  • Hi,

    We are using Publish Wizard for deploying the VSTO word Addin for 2007 application. We would like to

    • Specify the destination folder where the addin is getting installed on users m/c .Right now it is getting installed under C:\Documents and Settings\<LoggedInUserId>\Local Settings\Apps\2.0\<GUID> . This GUID is getting changed each time when we are installing a newer version. So we want to specify  a predefined installation folder.
    • Our Addin Installer also should be able to download a schema file to the client m/c
    • Also the installer should be able to set the service URLs  in Addin configuration file

    Is there any way to achieve any of these or of all of them using Publish Wizard availble with VSTO 2007 Addin. If It is noty possible using Publish Wizard , Can anybody suggest any other alternatives?? 

     

     

    Regards,

    Sunday, September 7, 2008 9:04 AM

Answers

  • Hi

     

    Unfortunately I think you are pushing the boundaries of the Publishing wizard. You will have to create your own setup program making sure the pre-requisites are installed and the registry keys created for the Addin project and manifest file that ideally should be signed for trust purposes. Then your service URL's could be stored in registry and or config files but remember the permissions required to edit the config file if installed in Program Files

     

    Regards

     

     

    Sunday, September 7, 2008 4:53 PM
  • And here is the link to the whitepaper explaining how to create a Windows Installer package for VSTO 3.0 solutions:

    http://msdn.microsoft.com/en-us/library/cc563937.aspx

     

    Monday, September 8, 2008 5:35 AM

All replies

  • Hi

     

    Unfortunately I think you are pushing the boundaries of the Publishing wizard. You will have to create your own setup program making sure the pre-requisites are installed and the registry keys created for the Addin project and manifest file that ideally should be signed for trust purposes. Then your service URL's could be stored in registry and or config files but remember the permissions required to edit the config file if installed in Program Files

     

    Regards

     

     

    Sunday, September 7, 2008 4:53 PM
  • And here is the link to the whitepaper explaining how to create a Windows Installer package for VSTO 3.0 solutions:

    http://msdn.microsoft.com/en-us/library/cc563937.aspx

     

    Monday, September 8, 2008 5:35 AM