none
First VSTO AddIn - 2 questions RRS feed

  • Question

  • I have just successfully developed and deployed my first VSTO AddIn and I want to ensure I did everything correctly.  The fact that it works does not mean I did things according to best practices.

    I am using VS2010/VSTO and have to support Word/Excel/Outlook/PowerPoint 2007, 2010/32bit and 2010/64bit.

    I am deploying via an MSI.

    After developing and testing the AddIns I published via ClickOnce them to a local folder.  I copied the manifests, assemblies and *.deploy.  The manifests were looking for files in the

    “\OfficePlugin\WordAddIn2010\publish\Application Files\Office.Word.AddIn.2010_3_11_3_0” directory structure so I had to recreate this directory structure during deployment.  Is there a way to flatten this out?

    I have to support 32 and 64 bit platforms – OS’s and Office.  Will building the AddIn “AnyCPU” cover this this or do I have to build multiple releases?

     

    Thanks in advance,

    Steve

     

     


    Steve
    Wednesday, June 1, 2011 1:27 PM

All replies

  • Marco...
    Steve
    Friday, June 3, 2011 2:12 PM
  • Hi Slomicka,

    As for the first problem, I think we need to make sure the path of the manifest is correct and clickonce wizard have helped us to generate the the directory. We can copy all of them to the target machine and install it via setup.exe. Here is a blog article about deploying via clickonce:

    http://blogs.msdn.com/b/pstubbs/archive/2007/05/17/vsto-my-favorite-feature-clickonce-deployment.aspx

     

    As for the second problem, building the AddIn based on "AnyCPU" is ok for 32 and 64bit platform.

    Hope the suggestion can help you.

    Best Regards,


    Bruce Song [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Tuesday, June 7, 2011 5:35 AM
  • Bruce,

    Thank you for your reply.

    My task is to create custom MSI.  We use InstallShield to author MSI installs.  I actually have the installs working but certain things really tasted funny.  For example:

    With Word I have to replicate the directory structure that click once created in my deployment in order to get Word to load the AddIn.  The manifest contained relative paths where it was looking for the assemblies.  I needed to ship the *.deploy files as well.

    With Outlook I was able to deploy all assemblies to a single folder.  No *.deploy files required.

    While the deployments “work” I still don’t definitively understand what files I have to deploy.  I have two Addins that work in QA on clean machines with seemingly totally different deployment requirements.

    Thank you for the “AnyCPU” answer.  Saves quite a bit of work.

    Steve


    Steve
    Wednesday, June 8, 2011 2:35 PM
  • Marco
    Steve
    Friday, June 10, 2011 1:32 PM
  • We have to support Office 32/64 and Windows 7 32/64.  Can we create one installer to accommodate this?  We already install the correct VSTO runtimes.  We build our assemblies “AnyCpu” so I am not certain if they go under \ProgramFiles\ or \ProgramFiles (x86)\ or if it matters.  It sounds more reliable to create two installers and this article recommends that:

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

    Before we go through the work of creating two installers I was hoping for some confirmation.

     


    Steve
    Wednesday, June 15, 2011 3:01 PM
  • To follow-up this article says it can be done it one installer:

    http://blogs.msdn.com/b/vsto/archive/2010/03/08/deploying-your-vsto-add-ins-to-all-users-saurabh-bhatia.aspx

    This article recomends two:

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

    What is the recomendation?

    Steve

     

     

     

     

     

     


    Steve
    Wednesday, June 15, 2011 4:43 PM