I have a Office Addin which works well in MS Office 2007. Can I port this Addin to Mac? Is this possible?
Sorry, the VSTO framework used to develop Office Add-ins is for Windows only :-(
Take a look at Microsofts system requirements for the VSTO framework: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=20479
Related
I want to create a Add-In. I will create in VS 2013. I just don't know what is minimum version support of Ms Office.
Can anybody please suggest me? So, I can take case of the requirement.
VS2013 will natively support 2010 and 2013, but it is possible to support 2007 as well.
Per Microsoft's article on running solutions in different version's of Office:
If you developed solutions for Office 2010, you can run the same solutions in Microsoft Office 2013. If your customer base uses the 2007 Microsoft Office system, you can use Visual Studio 2013 to develop solutions that work in all three versions of Office. In this scenario, the solution will run without errors in the 2007 Microsoft Office system only if the solution doesn’t use features that are new in later versions of Office. Microsoft Office applications can also run solutions that were created by using a previous version of Visual Studio.
I have an addin that is compatible with Outlook 2003 - 2013 by using the various versions of VSTO.
It seems that the majority of small businesses will have the Click To Release version, which is not compatible with addins.
Is there a way to make an addin compatible with 2013 C2R, or does it need to be rewritten to be an "App" using Napa?
C2R Office installation load COM addins in exactly the same way as the regular version of the Office, there is nothing you need to do.
What is the exact problem that you are running into?
I am currently in the process of re-writing some VBA macros that were written for office 2003. I was wondering if I wrote a C# add-in for 2007, if it would work for 2010 or maybe even 2013. Or if I wrote them for 2010 if they would work for 2007 and 2013 as well. I currently have access to 2007 but I could get access to 2010 if need be, no 2013 yet.
So, basically, how much does the version of office affect the plugins?
If you use Visual Studio Tools for Office 2010 (VSTO 4.0) then it will compatible for Office 2007 ,Office 2010 and with Office 2013.If you use earlier version other than the above then you can use that only for particular office versions only.As a example VSTO 3.0 only supports office 2003 and 2007 as shown below table.
For more information check this out Visual Studio Tools for Office and Visual Studio 2010 Tools for Office Runtime
compatibility Shows like below:
I hope this will help to you.
you can take a look at Netoffice, a wrapper for MS Office that enables you to create Addins for all supported versions of MS Office. You don't need VSTO and you can check within your own code which version of Office your AddIn is running in.
We need to create a VSTO add-in in C# that supports both Outlook 2007 and 2010.
To start off we created 3 projects:
File->New Project->Office->2007->Outlook 2007 Add-in
File->New Project->Office->2010->Outlook 2010 Add-in
File->New Project->Windows->Class library
All shared code is in project #3.
So far, we have partially developed the add-in and have been using ClickOnce deployments for testing.
One day, we noticed someone installed the 2010 add-in for 2007 Outlook and had no ill effects whatsoever.
So a few questions:
Is there any reason to create the
2007 VSTO project? Can we just
create the 2010 project?
Or is the only difference the version of
the office runtime that is
bootstrapped by the ClickOnce
installer? Can you just install the 2010 runtime for Outlook 2007?
If there is no difference, why are
there two Visual Studio project
templates?
In our final solution, we will be using a WiX installer, which is also working thus far. The WiX installer will be simplified greatly if we can use 1 project for the add-in.
Is there any reason to create the 2007 VSTO project? Can we just create the 2010 project?
You can just use the 2010 project, but if you accidentally reference any 2010 ONLY api's, for example accessing any of the new conversation API's will cause your add-in to blow up in 2007.
Or is the only difference the version of the office runtime that is bootstrapped by the ClickOnce installer? Can you just install the 2010 runtime for Outlook 2007?
Basically you are writing a VSTO 3.0 add-in, which works for both 2007 and 2010. VSTO doesn't actually care which template you are writing for, only that your add-in is a VSTO 3.0 add-in.
If there is no difference, why are there two Visual Studio project templates?
2 reasons that I can see, F5 debugging support, and to make sure you do not access a new API'
If you do go down the only 2010 add-in road, I suggest you do a compile of the solution against the Microsoft.Office.Interop.Outlook v12 PIA which will show you any new API's that you are accessing. If you do want to target some of these new API's only IF your add-in is hosted in 2010 then have a look at http://blogs.msdn.com/b/vsto/archive/2010/06/04/creating-an-add-in-for-office-2007-and-office-2010-that-quot-lights-up-quot-on-office-2010-mclean-schofield.aspx
How do I develop addin for MS Outlook that works with all
1. Outlook 2010
2. Outlook 2007
3. Outlook 2003
I have developed addin that works well with 2010 and 2007 BUT NOT with 2003.
I want something like this that works well with all the above three :)
You need VSTO (Visual Studio Tools for Office). Here is an article to get you started.
You can also check out Office Development Center.
You need to go for NetOffice.
It will allow you to abstract out from Outlook version.
Also it has a powerful diagnostic tool that will tell you which version of outlook your add-in is compatible with based on API features you use in your code.
Worked nicely for me.
http://netoffice.codeplex.com/