It's hard to say; "data programming" is a rather broad term...
VSTO 2005 SE will only let you create Add-ins. I can't tell whether that would do the job for you.
The full VSTO 2005 will let you create document-level projects, including data caching and binding to WinForm controls in the document. But you can only design these against Office 2003 (they should run in Office 2007 on the client machine).
Currently, there is no VSTO designer for Office 2007. That will be part of Orcas.
VSTO 2005 was designed to support Office 2003. In particular, you get design-time support for document (Excel/Word) customizations.
VSTO 2005 SE adds Office 2007 support for managed Add-Ins, Ribbon, Custom task panes and Outlook Form Regions. The VSTO 2005 SE runtime includes the support for customized documents from VSTO 2005, but there is no design support.
The rules would be something like this:
- if you want to do your Excel/Word data programming through a managed add-in, VSTO 2005 SE should be enough.
- if you want to create customized Word or Excel documents, you need to use VSTO 2005
- You can run customized documents created with VSTO 2005 in Office 2007 through the VSTO 2005 SE Runtime.
This link should help:
Visual Studio 2005 Tools for Office Second Edition
>VSTO 2005 SE will only let you create Add-ins. I can't tell whether that would do the job
Thank you for the info. At this point, I can't tell whether Add-ins are
enough either since going to the Add-in dialog in Excel 2007 on my
machine always results in an error that immediately closes Excel. This
is what has prompted me to begin looking at alternative methods for
upgrading an XLA add-in that has been in use for ~10 years.
> - if you want to create customized Word or Excel documents, you need to use VSTO 2005
And now that I have VSTO 2005, it looks to me as if one must also
retain Office 2003 on the development machine rather than replace it
with Office 2007. Correct
Furthermore, if design-time support for document customizations in
Office 2007 does not exist, is it planned for a future release
VSTO Installation Requirements for Office 2007
Marius Mihalec
Hi Douglas
It's hard to say; "data programming" is a rather broad term...
VSTO 2005 SE will only let you create Add-ins. I can't tell whether that would do the job for you.
The full VSTO 2005 will let you create document-level projects, including data caching and binding to WinForm controls in the document. But you can only design these against Office 2003 (they should run in Office 2007 on the client machine).
Currently, there is no VSTO designer for Office 2007. That will be part of Orcas.
Barry KOO
Hi Douglas
Have you discussed the problems you've been having with the Excel UI (crash, etc.) in the Excel.programming newsgroup
pc_bond
Hi Dough,
VSTO 2005 was designed to support Office 2003. In particular, you get design-time support for document (Excel/Word) customizations.
VSTO 2005 SE adds Office 2007 support for managed Add-Ins, Ribbon, Custom task panes and Outlook Form Regions. The VSTO 2005 SE runtime includes the support for customized documents from VSTO 2005, but there is no design support.
The rules would be something like this:
- if you want to do your Excel/Word data programming through a managed add-in, VSTO 2005 SE should be enough.
- if you want to create customized Word or Excel documents, you need to use VSTO 2005
- You can run customized documents created with VSTO 2005 in Office 2007 through the VSTO 2005 SE Runtime.
This link should help:
Visual Studio 2005 Tools for Office Second Edition
http://msdn2.microsoft.com/en-us/office/aa905543.aspx
edwin11
Thank you for the info. At this point, I can't tell whether Add-ins are enough either since going to the Add-in dialog in Excel 2007 on my machine always results in an error that immediately closes Excel. This is what has prompted me to begin looking at alternative methods for upgrading an XLA add-in that has been in use for ~10 years.
MickJ27
And now that I have VSTO 2005, it looks to me as if one must also retain Office 2003 on the development machine rather than replace it with Office 2007. Correct
Furthermore, if design-time support for document customizations in Office 2007 does not exist, is it planned for a future release