Does Office 2007 PIA also require Office 2007 to be installed?
Can I deploy Office 2007 PIA with VSTO 3.0 (without having Office 2007 installed)?
EDIT: I have a windows application that generates MS Word files. I have added the Office 2007 PIA as custom pre-requisite in the setup, but Office 2007 PIA needs MS Office 2007 to be installed.
I just wanted to know that if VSTO does not require Office Installation, then maybe i can convert my application to VSTO.
In order to use VSTO you must have Office Installed. The VSTO PIA's only provide a shim between .NET and the COM interfaces that Office exposes. So the PIA's can do nothing w/o Office.
note: you can generate docx (word 2007) files without office.
What do you want to do with the Primary Interop Assemblies exactly? I think you need to clarify your question a bit.
If you plan on making any method calls to the Microsoft Office PIA DLLs without Office installed you can expect your code to blow up with a COMException when you run it since Office isn't there to inter-operate with.
If what you want to do is create Word documents without MS Word being installed then your best option is to use one of the available programs to do this. This is usually how Word/Excel documents are created on a web server for instance.
To generate MS Word documents we've used both Syncfusion DocIO (and XlsIO for Excel) and OfficeWriter and they have been much easier and literally 5 to 30 times faster in document generation than MS Word (depending on the complexity of the document). However, these tools are not free. I suppose it's theoretically possible to generate docx files manually (as hinted by Tracker1) but that would be a lot of work unless there are free libraries to assist in doing that.
Related
I am trying to create an Office add-in, mainly for Word, that consists of a simple Task Pane that displays search results from a website. I need it to work in every version of office, as far back as Office 2010. So I have chosen to create it in VSTO, as that seemed to be the most backward compatible approach. My problem is I don't have Word 2010, 2013, 2016, 2019, etc, to test that the add-in works in them, nor do I have any idea of how to build the add-in for backward compatibility in the first place.
I've searched through countless tutorials, Microsoft docs, Stack Overflow answers. I'm stuck. I know it's technically possible because the Grammarly add-in works in Office 2007 thru 2021/365.
Is it even possible for a little dev like me to create an add-in for Word 2010 in 2022?
I am using Visual Studio 2021.
As far as I know Grammarly uses a shimmed COM add-in skeleton (most probably written in C++) which implements the IDTExtensibility2 interface. But VSTO does this for you out of the box by hiding all the complexity COM add-ins could have on board.
Is it even possible for a little dev like me to create an add-in for Word 2010 in 2022?
Yes, of course. It is not necessarily to create C++ COM add-ins, you can easily start creating VSTO add-ins for that. You just need to choose the right .net framework version for that.
The Run solutions in different versions of Microsoft Office article shows Office versions that can be supported by your add-in created with Visual Studio 2022 or earlier and target .net frameworks that can be used for that. Depending on the .net framework chosen you can support different ranges of Office application versions, in short.
The Visual Studio Tools for Office Runtime page lists the VSTO Runtime releases and the corresponding version of Office for which its support lifecycle follows. The Visual Studio 2010 Tools for Office Runtime (VSTO Runtime) ships with various versions of Visual Studio and Microsoft Office and follows the support lifecycle of the parent product. It is recommended that developers install the latest version of the VSTO Runtime with their applications. It will be supported when running with supported versions Office. If the VSTO Runtime needs to be serviced, only the latest version will be updated.
We have a Microsoft word add-in that is working fine on the majority of pc's.
On a particular windows 7 pc, it has the visual studio 2010 tools for office installed correctly.
But when a user creates a new template word document, they get teh following error:
The customization assembly could not be found or could not be loaded.
You can still edit and save the document. Contact your administrator
or the author of this document for further assistance.
We have tried unloading all dependencies but still does not make any difference.
This is an issue effecting a small amount of windows 7 pc's with office 2016 installed. It seems to be pc related rather than the application.
Usually, the reason behind such an error is that the permissions for loading the VSTO solution are missing. One thing that often gets "missed" when deploying VSTO solutions is that the document must be in a "trusted location". You might want to check that this is the case by looking in the Word "Trust Center" (in the Options). You also need to be sure you've installed the correct version of the VSTO run-time for the version of Windows and Office. Read more about that in the Troubleshooting Run Time Errors in Office Solutions article.
Also it may indicate that you didn't include all required dependencies to your add-in's installer (any platform-specific assemblies). Something is missing on the target machines, so I'd suggest looking for any difference between machines. You can add the .NET Framework, the Visual Studio Tools for Office runtime, and the Office primary interop assemblies to your Setup package as prerequisites that are deployed with your Office solution. For information about how to install the primary interop assemblies, see Configuring a Computer to Develop Office Solutions and How to: Install Office Primary Interop Assemblies.
The required steps for deploying Office solutions are described in the following articles:
Deploying an Office Solution by Using ClickOnce
Deploying an Office Solution by Using Windows Installer
You can use the event viewer in Windows to see error messages that are captured by the Visual Studio Tools for Office runtime when you install or uninstall Office solutions. You can use these messages from the event logger to resolve installation and deployment problems. For more information, see Event Logging for Office Solutions.
See Troubleshooting Office Solution Deployment for more information.
I have created an office addin for Word 2010 targeting .net 4 and this should apparently work in office 2007.
I have created the installer per this article with the exception that I include a dll in the dependencies rather than in the bootstrapper for the prerequisites.
The installer installs the vsto and the registry keys in
HKCU\Software\Microsoft\Office\Excel\Addins\ProjectName
The pc also has .Net 4 and the Office 2007 Primary interop assemblies.
The addin doesn't appear in Word 2007, any ideas where I could be going wrong?
UPDATE:
You have to sign your addin, this was pretty obvious! Office now recognises the addin but its gets a runtime error that I can't debug. Tried to debug with these steps with no luck!
Had to build for correct CPU version of office, in my case 32bit, Any CPU didn't work!
Hello I have been fighting some complexities with understanding deployment of Primary Interop Assemblies (PIA) for MS Office. I have Visual Studio Com Add-IN built in VS 2008 on pure com technology (not VSTO see bottom of this for more on that), which references 2003 Primary Interop Assemblies but the add-in may be used on 2003, 2007 or now 2010 Office machines. Because I never know if the customer will be using 2003, 2007, or 2010, I cannot simply deploy one PIA version as a prerequisite (unless I make 3 installers which I do not want to do). Now, my understanding is that when you follow the steps here to add 2003 and 2007 PIA to the prerequisite lists that show up in a Visual Studio (2008) setup package, the prerequisites are smart enough to determine which office version is running on the client you are targeting. So if you were to select 2003 primary interop assemblies and 2007 primary iterop assemblies as both being prerequisites then when this installs on a machine that has 2003 it should be intelligent enough to only try to add the 2003 PIA if those are missing on this machine and if this is a 2007 Office machine then it will only install 2007 PIA (and not try to install 2003 PIA).
Question 1 is this a correct understanding (that the prerequisite packages are this intelligent to only install what it needs based on the version of Office?)
Question 2 is there a way to get the 2010 PIA to show in the list of prerequisites in VS 2008 like 2003 and 2007 do? I do not want to upgrade this project to VS 2010 b/c it is considered a legacy app now with many customers from all around the world using it.
Question 3 Even though the actual assembly references 2003 primary interops, I do not presently deploy those interops with the add-in to the install location. Instead, I am assuming that if I can get the correct PIA installed then I don't need this present in the installation path, since the PIA would be in the GAC. However, one possible approach may be to just include the 2003 assemblies that are referenced (in my case excel and word) in the install path and not worry about the PIA. I suspect this would work on 2003 machines but perhaps not on 2007 and 2010 machines b/c on the latter, even if the 2003 interops that are referenced are found at run time in the install path of the assembly, I think if there is not a Policy.11.0.Microsoft.Office.Interop.Excel/Word(etc) in the GAC, then 2007 and 2010 will likely not know what to do with the 11.0 (2003) interops (as I think the Policy.11.0.Microsoft.Office.Interop files redirect requests for the 2003 interops to 2007 or 2010). Any thoughts on this?
Question 4: There is a well known bug with Framework 2.0 apps Office Add-Ins and Office 2003 where the add-in won't load. This was addressed by KB907417 aka KB908002. Dopes anyone know if this KB necessary if you develop on the 3.0 or 3.5 framework (and make 3.0 or 3.5 a prerequisite) since this problem was specific to framework 2.0? Or does the KB still need to be deployed b/c it's office 2003 that is the problem and not the version of the framework?
As you can tell by my 3 questions what I am trying to ascertain is whether we can build one single installer via the VS setup utility. If the PIAs can be done with one installer but the KB above is the obstacle (as perhaps the answer will come back that even on the 3.0 or 3.5 framework 2003 customers will need the KB) then maybe the path to one installer is to just make the KB a prerequisite across the board and install it on 2007 or 2010 machines, though they technically do not need them. Any thoughts on that option would be appreciated as well. Finally, I am aware that writing a manged Com Add-IN for excel or word is now generally done with VSTO instead of pure managed framework code, but this is not an option presently to change the legacy app to this direction. Also it is reported that the 4.0 framework now can be used to deploy add-ins without making any PIA a prerequisite but again, this is not a viable option right now.
Does the code use any Office 2007+ methods or classes? If not, are you sure you cannot use the 2003 PIAs in all cases? The later apps should be backward-compatible (supporting the same API) so the only reason you'd need an updated PIA is if you needed to access some feature added by 2007 or later, I think.
You may want to take a look at Add-in Express, which promises a one-for-all-versions installer, and is pretty easy to use.
As you can tell by my 3 questions what I am trying to ascertain is whether we can build one single installer via the VS setup utility
You cannot. You must create custom installer packager (setup bootstrapper).
Many years ago I used dotNetInstaller with HTML GUI builder, today WiX toolset would be better solution, I think.
Check how PIA .msi installers are constructed with Orca or .msi and .exe installers flow checking windows installer logs.
Based on registry checks, file checks, installed product checks, windows versions, office versions you can create conditions whether component should be installed or not.
Oh and I advise making plugin installers without prerequisites and installing them conditionally with your custom installer bootstrapper.
I have a requirement to create an installer for an Outlook 2003 add-in that was created with VSTO.
We currently are using Wix for our installers as they play nice with MSBuild and I need to use it to create the installer for the outlook add-in.
I have no experience with outlook add-ins and am unsure exactly what is involved and how to go about creating the installer.
Can anyone share any experience/tips/examples that would help me please?
Thanks in advance,
B
I found this Microsoft article on VSTO add-ins deployment to be an absolute life-saver; I don't know about Wix, though. http://msdn.microsoft.com/en-us/library/bb332052.aspx
I've not done this in WiX but I have done it in InstallShield. Below with my notes from that time:
http://blog.deploymentengineering.com/search?q=vsto
One problem you will have is that WiX doesn't have a bootstrapper so you will have to find a way to chain the .NET Framework and VSTO redist ( also possibly the Office 2003 PIAs; you didn't say which version of VSTO you are using ) with your installer unless you choose to take the route that merely gates the install if those aren't found.
I recall using a DTF custom action to publish a certificate but I can't recall if that was needed for Office 2003 or only for Office 2007.