Here at work I have Visual Studio 2005 and Office 2007 installed. I'm trying to install the VSTO package to create a templated Word Document project. I installed the VSTO package via this link: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=8315654b-a5ae-4108-b7fc-186402563f2b#filelist
Whenever I create a new Word Template Office Project I receive an error message informing me that Office 2003 is not installed. It clearly states the package is for office 2003 and office 2007.
Any ideas why this isn't working?
Here's the error message: http:// i34.tinypic.com/2a4wg9u.png
You've got the wrong download. Office Second Edition is Office 2003.
You want this one for Office 2007
http://www.microsoft.com/downloads/details.aspx?familyid=5E86CAB3-6FD6-4955-B979-E1676DB6B3CB&displaylang=en
Related
I am working on making a Outlook Add-in for Outlook 2013. The issue is, I use Visual Studio 2010. I did some googling and found that I need the Developer Tool Kit and it lead me here. I installed the tool kit, but I am still not seeing any new Templates. What am I doing wrong, or what can I do to get that Outlook Add-in?
Thanks in advance!
Unfortunately VSTO allows creating version-specific add-ins. VSTO 2010 (Visual Studio 2010 Tools for Office Runtime) is shipped with Visual Studio 2010 Professional edition or above. It supports creation and editing of document- and application-level add-ins for Office 2007 and Office 2010. You need to use later Visual Studio versions for creating COM add-ins for Office 2013. However, you can run solutions in Office 2013 that were created in earlier Visual Studio versions, see Running Solutions in Different Versions of Microsoft Office for more information.
We need to develop add-in for the Office 2016. We are using the Visual studio 2013. It is only showing the Office 2013 add-in templates. Is it possible to create Office 2016 add-in from Visual studio 2013? If so, kindly let me know the steps.
You need VS 2015 to get the specific templates for Office 2016. VSTO only ever provides templates for "current" versions of Office.
If Office 2013 is installed you can develop an Add-in for it. There should be no problem installing and running it in Office 2016 - unless you want to use technology specific to 2016. In that case, you could use late-binding (PInvoke) for the 2016-specific portions, but debugging/testing would be a bit of a pain.
You can download the free Visual Studio 2015 Community edition (https://www.visualstudio.com/en-us/downloads/download-visual-studio-vs.aspx) as well as the VSTO package (https://www.visualstudio.com/en-us/features/office-tools-vs.aspx): VSTO does integrate into the Community edition for version 2015 (and 2013, for that matter). Licensing restrictions would apply, of course.
Other than that, you'd need to upgrade to a full VS 2015.
You can develop and run Office 2016 addins in VS2013. No need to upgrade to VS2015.
Install VSTO 4.0 extension for VS2013
Create Office 2013 plugin using Visual Studio template
Open project file and replace office version string "15.0" to "16.0" in ProjectExtensions section. Look for this of similar string to edit:
OfficeVersion="15.0" VstxVersion="4.0" ApplicationType="Outlook" Language="cs" TemplatesPath="" DebugInfoExeName="#Software\Microsoft\Office\15.0\Outlook\InstallRoot\Path#outlook.exe"
Yes, it is possible. The add-in created in Visual Studio 2013 can be run in Office 2016. You can read more about that in the Running Solutions in Different Versions of Microsoft Office article.
In case if you need to use new methods and properties available only in Office 2016 you can use the Reflection mechanism (see Type.InvokeMember).
there is an example for Outlook, i tried it for Excel and it works as well.
my example:
<ProjectProperties HostName="Excel" HostPackage="{29A7B9D7-A7F1-4328-8EF0-6B2D1A56B2C1}" OfficeVersion="16.0" VstxVersion="4.0" ApplicationType="Excel" Language="vb" TemplatesPath="" DebugInfoExeName="#Software\Microsoft\Office\16.0\Excel\InstallRoot\Path#excel.exe" DebugInfoCommandLine="/x" AddItemTemplatesGuid="{DCFE8D25-4715-4C33-9EAB-A34A9EBC9544}" />
i changed
OfficeVersion="15.0"
to
OfficeVersion="16.0"
and the path to Excel
#Software\Microsoft\Office\16.0\Excel\
as well, finally it starts in Excel 2016...
I have developed word addin 2010 using visual studio 2012. I have created setup file using below MSDN link.
http://msdn.microsoft.com/en-us/library/cc442767.aspx
When i run this for ofice 2010 or office 2013 it works fine but it doesn't work for office 2007.
I though it would be word addin issue so I have created word addin 2007 and still have issue.
Can somebody suggest what can be the issue?
Add-in functionality changed again between Office 2007 and 2010, to support new features like the changed UI (RibbonBar). The addin you created for Office 2010 uses features that did not exist in the Office 2007 apps (Word/Excel etc).
Office Add-ins are typically forward compatible only. That is future version of Office support older older plugins, but the opposite is simply not possible as new features get added all the time.
e.g.
Write an Office 2007 addin and it will likely work on Office 2007, Office 2010 and Office 2013.
Write an Office 2010 addin and it will likely work on Office 2010 and Office 2013.
Write an Office 2013 addin and it will likely only work on Office 2013.
Please note that while they "work" they will often look very old-fashioned as they typically use the older UI elements and not the latest version.
Create a 2007 add-in instead
If you really need Office 2007 support, you need to create a 2007 Add-in instead (as well?). Otherwise you will likely be using features that simply do not exist in Office 2007. The only possible (unlikely) alternative is to add Office 2010 DLLs to the machines, but as you are then effectively upgrading Office I doubt that is legal without a Office 2010 licence (so you might as well upgrade them anyway).
Try to attach to the project the Interop.Word dll of Word 2007.
Also exchange the Office Object Library dll 12- which comes along with Word 2007.
Hope this helps.
Came to work this morning, my PC (Win7 x64) had force rebooted by Windows Update. Now, SQL Server Management Studio (SQL Server 2008 r2) fails when connecting to a database and trying to expand the tree view, citing:
Unable to cast COM object of type 'System.__ComObject' to interface
type 'Microsoft.VisualStudio.OLE.Interop.IServiceProvider'. This
operation failed because the QueryInterface call on the COM component
for the interface with IID '{6D5140C1-7436-11CE-8034-00AA006009FA}'
failed due to the following error: No such interface supported
(Exception from HRESULT:0x80004002 (E_NOINTERFACE)).
(Microsoft.VisualStudio.OLE.Interop)
The following updates were installed during the night:
Security Update for Microsoft Office 2007 System (KB2553090)
Update for Microsoft Visual Studio 2010 Service Pack 1 Web Platform Tools (KB2548139)
Update for Microsoft Visual Studio 2010 Service Pack 1 Report Viewer (KB2549864)
Update for Microsoft Visual Studio 2010 Service Pack 1 TFS Build Explorer (KB2522890)
Security Update for Microsoft Office Excel 2007 (KB2553073)
Security Update for Microsoft Office Groove 2007 (KB2552997)
Update for Microsoft Office Outlook 2007 Junk Email Filter (KB2553110)
Security Update for Windows 7 for x64-based Systems (KB2570947)
Update for Microsoft Visual Studio 2010 Service Pack 1 (KB2547352)
Security Update for Microsoft Office 2007 System (KB2553089)
Update for Microsoft Visual Studio 2010 Service Pack 1 (KB2529927)
Security Update for the 2007 Microsoft Office System (KB2553074)
Update for Microsoft Office Outlook 2007 (KB2583910)
Security Update for Microsoft Office 2007 System (KB2584063)
Update for Windows 7 for x64-based Systems (KB2616676)
Windows Malicious Software Removal Tool x64 - September 2011 (KB890830)
So, quite a bit. The Event Viewer shows no errors (not regarding this, anyway) and all updates were successfully installed. I'm kind of stuck here right now, I've seen some articles recommending re-registering DLLs, but so far that hasn't worked.
Any help would be most welcome!
Finally found a fix!
Seems like Internet Explorer is the culprit, for some very strange reason.
Launch command line in administrative mode.
Go to C:\Program Files\Internet Explorer or c:\Program Files (x86)\Internet Explorer if you have Win x64.
Execute regsvr32 /u ieproxy.dll (this might throw an error if it isn't loaded)
Execute regsvr32 ieproxy.dll
This did the trick for me (actually, I registered/unregistered one extra time, but that shouldn't have anything to say?)!
Hope this helps anyone!
On the download page for 2.3.1 it only mentions compatability with Office 2007.
I tried installing v2.0 but I couldn't see the wizards in the project types.
The docs contain this phrase near the top:
Applies to: 2007 Microsoft Office
System, Microsoft Office 2003,
Microsoft Office XP, Microsoft Office
2000
User comment in this employee blog post:
A small update : Just tried it on a PC
with Outlook 2003 and the addin works!
Good enough?