T
Tadwick
I posted this to an MSDN forum on VSTO and got no replies yet so hope you
don't mind me trying this forum. I'm new to add-ins and have not used VSTO
before. Can someone pls confirm my understanding of the following with
regard to VSTO and Outlook:
1. You can only deploy to Outlook 2003 (and later).
2. You have to ensure users have a number of prerequisites before they
install your VSTO-developed add-in:
- .NET 2.0
- Outlook 2003 SP 1
- Outlook 2003 Primary Interop Assemblies (redist)
- VSOT run time
3. You have to purchase VSTO ($550 for upgrade).
So, aside from the loss of backward compatibility with pre 2003 versions of
Outlook and the purchase cost (which is very unfortunate given that I've
already paid $550 for VS Pro), are there other cons to using VSTO? I
thought I read that users also have to be running Office _Professional_ to
get VSTO solutions to work - is this true? Does VSTO make it very easy to
transform VBA code to a professional deployable solution that will cause
users/admin minimum fuss to deploy?
Thanks
Tad
don't mind me trying this forum. I'm new to add-ins and have not used VSTO
before. Can someone pls confirm my understanding of the following with
regard to VSTO and Outlook:
1. You can only deploy to Outlook 2003 (and later).
2. You have to ensure users have a number of prerequisites before they
install your VSTO-developed add-in:
- .NET 2.0
- Outlook 2003 SP 1
- Outlook 2003 Primary Interop Assemblies (redist)
- VSOT run time
3. You have to purchase VSTO ($550 for upgrade).
So, aside from the loss of backward compatibility with pre 2003 versions of
Outlook and the purchase cost (which is very unfortunate given that I've
already paid $550 for VS Pro), are there other cons to using VSTO? I
thought I read that users also have to be running Office _Professional_ to
get VSTO solutions to work - is this true? Does VSTO make it very easy to
transform VBA code to a professional deployable solution that will cause
users/admin minimum fuss to deploy?
Thanks
Tad