Develop Office Client Applications using Visual Studio
Today we released the Microsoft Office 2010 Primary Interop Assemblies (PIA) Bootstrapper Installer which adds the Microsoft Office 2010 Primary Interop Assemblies to the Prerequisites Dialog Box in Visual Studio 2010 or Visual Studio 2008. Then when you deploy with ClickOnce or Windows Installer, you can select this option to deploy the Microsoft Office 2010 PIAs to end-user computers.
Download it here: Microsoft Office 2010 Primary Interop Assemblies (PIA) Bootstrapper Installer
Make sure to read the instructions on the download page in order to properly set up the bootstrapper to appear in Visual Studio. Now when you create Office 2010 solutions with Visual Studio 2010 you can select to deploy this prerequisite component with your solution to your end users.
For more information on developing Office solutions with Visual Studio please visit the Office Development with Visual Studio Developer Center.
Enjoy, -Beth Massi, Visual Studio Community
What if I want to deploy to clients using either Office 2007 or Office 2010. Should I then do two clickonce publications, one with the 2007 and one with the 2010 pias? Or can I enable both and the installer will check and install the correct one according to which version of Office is available on the client machine?
This Bootstrapper at 9/7/2010 published release does not include "o2010pia.msi" file.
Then I couldn't choose install location "Download prerequisites from the same location as my application".
Please re-release Bootstrapper including "o2010pia.msi" file.
I came to know that Office 2010 don't need PIAs to be installed or they come with PIAs by default. Is it correct? If so what is the need for us to deploy them with the addin?
by default, Microsoft Office installs the PIAs if the .NET Framework 1.1 or later is installed on the computer before Office is installed. This is true for Office 2007 and Office 2010.
in addition, if your Office solution targets the .NET Framework 4, the required types are embedded into the Office solution. this reduces the need to deploy the PIAs separately. however, if the Office solution targets the .NET Framework 3.5, there is still a need for PIAs.
for more information, see msdn.microsoft.com/.../kh3965hw.aspx and msdn.microsoft.com/.../15s06t57.aspx
Mary Lee, Programming Writer.
I can't get the bootstrapper to work. The 2010 PIA prerequisite checkbox is not available in VS 2008 after installing office2010pia_bootstrapper.exe and copying the Office2010PIARedist folder from C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\ to C:\Program Files (x86)\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\
FWIW, the Office2007PIARedist folder has a MSI file (o2007pia.msi) but the Office2010PIARedist folder has no MSI files at all...
did you have VS2008 open when you installed the PIA bootstrapper package? if so, try closing VS and re-opening it.
there's no MSI in the Office 2010 PIA bootstrapper package because it is set to download the PIAs from the Microsoft Download Center (HomeSite).
if you want to change the PIA bootstrapper to include the PIAs along with the setup.exe, change the bootstrapper to SameSite, download the PIAs from www.microsoft.com/.../details.aspx and then add it to the folder for the Office 2010 bootstrapper package.
I did have VS open the first time I installed it, but I tried again, this time closing VS and re-installing the bootstrapper. Same result.
Incidentally, the bootstrapper appears in VS 2010, and my projects compile successfully there (after a few adjustments), so I may switch to VS 2010 if I don't encounter any problems installing the application on client machines.
I do want to install all of the prerequisites from the application's installation share. I've been trying to locate a good reference for creating a completely stand-alone installation of the following components using a setup project:
1) Access 2010 redistributable runtime
2) Office 2010 PIA
3) VSTO runtime
4) .NET 3.5 SP1
5) and of course, my add-in
I am able to create the setup project, but exactly how to include all of the prerequisites (especially the Access runtime) is a bit of a mystery. Do you have any recommendations?
there is a whitepaper at msdn.microsoft.com/.../ff937654.aspx that explains how to use a setup project to deploy an Office solution by using VS2010.
it looks like someone posted most of the package.xml file for the Access runtime redist at social.msdn.microsoft.com/.../27287dea-2fee-4d8d-b2c7-49d58c92b7d4 but if that doesn't help, there is also the Bootstrapper Manifest Generator tool at code.msdn.microsoft.com/bmg where you can generate your own. there are links to the Access runtime here: blogs.msdn.com/.../download-access-2010-runtime-database-engine-redistributable-and-source-code-control.aspx
.NET Framework 3.5 SP1 is only set up as HomeSite, so if you want to include it in your setup, the instructions are linked from blogs.msdn.com/.../how-to-include-net-framework-3-5-sp1-with-your-installer.aspx
Such as Jay Ward, I see nothing in Prerequisites dialog (Visual Studio 2008 Professional)...
does not work with visual studio 2012. i wish i had never upgraded!
I tried to install MS office 2010 on my VISTA home , it keeps on saying it cannot be installed due to BOOT STRAPPER. I tried to install "Microsoft Office 2010 Primary Interop Assemblies Bootstrapper Package" and nothing seem to work. Been very frustrated over this issues.