I'm very new with VSTO development. Is it possible to develop Ms Word Add-In that can be used in Word 2007 and Word 2010?
When I try debugging an add in for Word 2010 in a machine that have Word 2007, it is said that "the required version of the Microsoft Office Application is not installed". Same thing happen when I try debug add in for Word 2007 with a machine that have word 2010.
Thank you for your help.
It is certainly possible to create a vsto addin that runs on both office 2007 and 2010 but there are some restrictions on the what and how. Microsoft has created a rather comprehensive document about this topic: Running Solutions in Different Versions of Microsoft Office
Related
I am about to develop my first ever MS Outlook add-in (following this MS guide).
As I create my new project, I see this ...
Was there really such a change between these versions of Outlook? Does this mean that I will have two develop two copies of my add-in? Is there no forward/backward comparability?
Am I even following the correct guide? Should I be developing a VSTO? This question has an answer by Outlook Add-ins Team - MSFT (although their profile does not actually any actual MS affiliation), which starts
We recommend using the web add-in framework, instead of COM, for
writing an Outlook add-in. The web add-in framework enables developers
to:
Write once and have their add-in run across supported Outlook clients
enabling the add-in to reach millions of Outlook Desktop, Outlook for
Web, Outlook for Mac, and Outlook Mobile users.
The short answer is no, a 2013-2016 VSTO Addin will work with 2010. If you need it to work with Office 2007 you'll have to add the assembly Outlook 2007 Primary Interop Assembly (PIA).
I just need to ask to what degree Macros developed in Excel 2003 are compatible with Excel 2010 and 2013?
I would tend to think that there would be some issues, but from your experience, what percentage of macros developed in Excel 2003 can work in Excel 2010/2013?
The issue you are going to have is with 32/64 bit compatibility. Office 2003 is 32-bit only; starting with Office 2007, some versions are 64-bit.
Microsoft has a pretty good writeup of the issues on this page.
You should do some online searches for VBA features that were "deprecated" after Excel 2003. The single major feature that no longer works is Application.FileSearch
Just from msdn.microsoft.com:
Excel 2010 Object Model Changes Since Earlier Versions
What's New in Excel 2010
New Objects, Collections, and Enumerations_Excel.Dev
New Members and Constants_Excel.Dev
Tables of VBA Object Model Changes
VBA Object Model Changes
Word 2010 Object Model Changes Since Earlier Versions
What's new for VBA developers in Project 2013
And so on ...
I have written a couple of VSTO addins for Word 2010 and Excel 2010. I want to be able to do the same for Publisher and Access, but there aren't project templates in Visual Studio 2010 for those. I have tried Google and failed to find anything relevant.
Is it possible?
Thanks,
Chris
there is no rich object model for publisher or access, but just to add ribbon below link can be helpful
http://blogs.msdn.com/b/andreww/archive/2008/02/19/vsto-add-ins-for-access.aspx
Just a quick questions..
I have made an outlook add-in for 2007 version and when I tested it with version 2003 it did not seem to work.
Is there any special procedure I need to follow to enable to add-in in Outlook 2003 or it won't work at all? I hope I don't have to create a new one for 2003.
Thanks,
SL
Assuming that you are referring to an add-in created using VSTO.
When you create an add-in for Office 2007 the referenced Interop Assemblies will be the ones associated with Office 2007 and this is the main reason for your add-in not to work on Office 2003.
One alternative will be to reuse the custom add-in code but build it against Office 2003 Interop assemblies. This will work if you're not using any functionality inherent to Office 2007.
IIRC, a VSTO add-in developed for Office 2003 will possibly work on Office 2007 without change, but never the other way around.
I'm wondering if there's a way to manage VBA code authored in Excel 2007 using Visual SourceSafe? Office XP and 2000 apparently had 'developer additions' that supported this (e.g. http://msdn.microsoft.com/en-us/library/aa164419(office.10).aspx). Is this support missing in Office 2007?
The Office XP VSS addin worked fine in Excel 2007 last time I tried it (been a couple of years). It's really a VBA addin, and VBA hasn't changed much since Excel 2000 (eg, registered addins work across versions). You might need an MSDN subscription to download it, though- that's where I got it.