none
VS2008 and VSTO prerequisites RRS feed

  • Question

  • I have an add-in for Outlook that monitors the calendar for changes to appointments with a certain subject pattern and when they change entries are made to a database. This works perfectly with a ClickOnce deployment. I change from PIA 2007 to 2010 and it works on 2010. However, this is because VSTO v4 is being used but VS2008 does not have the VSTO v4 as a bootstrapped prerequisite.

    I would like to have the VSTO v4 as a selectable prerequisite, is this possible?

    Tuesday, June 12, 2012 11:36 AM

Answers

  • Creating a custom bootstrapper has solved deploying via CO or MSI in this case and as I am only attaching handlers for moving and delete events fucntionality is always there.

    Basic functionality means the likelihood of problems will be DB connection related. Shim would be the ideal scenario Ken but due to finance and deployment arguments I've been told this is the way :(


    • Edited by _Ritchie_ Thursday, June 14, 2012 8:46 AM
    • Marked as answer by _Ritchie_ Thursday, June 14, 2012 8:46 AM
    Thursday, June 14, 2012 8:45 AM

All replies

  • You would need to use VS2010 for that.

    --
    Ken Slovak
    [MVP-Outlook]
    http://www.slovaktech.com
    Author: Professional Programming Outlook 2007
    "_Ritchie_" <=?utf-8?B?X1JpdGNoaWVf?=> wrote in message news:fd780129-73d2-4787-be31-32ba04ac444e...

    I have an add-in for Outlook that monitors the calendar for changes to appointments with a certain subject pattern and when they change entries are made to a database. This works perfectly with a ClickOnce deployment. I change from PIA 2007 to 2010 and it works on 2010. However, this is because VSTO v4 is being used but VS2008 does not have the VSTO v4 as a bootstrapped prerequisite.

    I would like to have the VSTO v4 as a selectable prerequisite, is this possible?


    Ken Slovak MVP - Outlook
    Tuesday, June 12, 2012 3:17 PM
  • So MS doesn't have any bootstrapper package for VSTO v4 like it does for o2010pia.msi?
    Wednesday, June 13, 2012 2:23 PM
  • You could load the VSTO 4 runtime but it still wouldn't allow you to use it with VS2008, just as you cannot develop for VSTO 3 on VS2005.


    Ken Slovak
    [MVP-Outlook]
    http://www.slovaktech.com
    Author: Professional Programming Outlook 2007
    "_Ritchie_" <=?utf-8?B?X1JpdGNoaWVf?=> wrote in message news:968336ea-c5d2-48d7-931e-4f592e33c182...
    So MS doesn't have any bootstrapper package for VSTO v4 like it does for o2010pia.msi?

    Ken Slovak MVP - Outlook
    Wednesday, June 13, 2012 2:38 PM
  • That makes sense but I'm now wondering why my add-in works then.

    Built in VS2008 for Outlook 2007 on Vista x86. Deployed with o2010pia.msi and vstor40_x86.exe to Windows XP and Windows 7. Works perfectly?

    I'm attempting to bundle as a custom bootstrapper at the moment in pure hope.

    Wednesday, June 13, 2012 3:03 PM
  • I can run addins I developed in VS2008 for Outlook 2007 on Outlook 2010, they run OK but they don't support any of the new properties/methods/events. As far as forcing a VSTO version into something it wasn't designed for it might work but can you guarantee that at just the worst time something won't crash? VSTO hides a lot of what it does in those runtimes and I wouldn't necessarily trust that things will work in all cases if it's used in a way that wasn't intended.
     
    What I do when I want to support multiple versions of Outlook with one addin is to use a shared addin with a COM addin shim. I develop it on a machine with the oldest versio of Office installed that I want to support, and an appropriate version of VS.

    --
    Ken Slovak
    [MVP-Outlook]
    http://www.slovaktech.com
    Author: Professional Programming Outlook 2007
    "_Ritchie_" <=?utf-8?B?X1JpdGNoaWVf?=> wrote in message news:e950a7da-57c5-4d34-a403-1a231a8a5fa5...

    That makes sense but I'm now wondering why my add-in works then.

    Built in VS2008 for Outlook 2007 on Vista x86. Deployed with o2010pia.msi and vstor40_x86.exe to Windows XP and Windows 7. Works perfectly?

    I'm attempting to bundle as a custom bootstrapper at the moment in pure hope.


    Ken Slovak MVP - Outlook
    Wednesday, June 13, 2012 3:38 PM
  • Creating a custom bootstrapper has solved deploying via CO or MSI in this case and as I am only attaching handlers for moving and delete events fucntionality is always there.

    Basic functionality means the likelihood of problems will be DB connection related. Shim would be the ideal scenario Ken but due to finance and deployment arguments I've been told this is the way :(


    • Edited by _Ritchie_ Thursday, June 14, 2012 8:46 AM
    • Marked as answer by _Ritchie_ Thursday, June 14, 2012 8:46 AM
    Thursday, June 14, 2012 8:45 AM