Develop Office Client Applications using Visual Studio
After you develop Office solutions with Visual Studio Tools for Office, you can use Visual Studio 2008 SP1 to simplify your deployment experience. First, you can take advantage of the smaller .NET Framework Client Profile to decrease download time. Next, the Office 2007 primary interop assemblies (PIAs) are included in-the-box with VS2008 SP1 to avoid having to generate bootstrapper manifests. Finally, you can also troubleshoot any installation problems with the event viewer.
Develop your Office 2007 solutions against the .NET Framework Client Profile. The large size of the .NET Framework 3.5 SP1 can lead to long download times. The .NET Framework Client Profile is only 25MB in size, so download times are reduced when installing from the component vendor's web site. For more information about how to configure your solution to use the .NET Framework Client Profile, see How to: Target a Specific .NET Framework.
Deploying the Office 2007 primary interop assemblies is now (mostly) hassle-free. Visual Studio 2008 SP1 includes the Office 2007 PIAs as part of the update. This relieves you from having to download the PIA installer, download a code sample that contains the bootstrapper manifests, move the manifests to a certain directory, compile the ComponentCheck.cpp file to verify that the correct version of Microsoft Office is installed, and dance the hula. Instead, developing with one of the Visual Studio Tools for Office project templates already marks the Microsoft Office 2007 primary interop assemblies as a prerequisites. All you have to do is right-click on the project in Solution Explorer and click Publish.
Troubleshooting the installation and deployment process is more transparent. Any errors that occur are now logged in the event viewer. For example, I deliberately installed the same Office solution twice to generate the following error in the event viewer. Developers commonly see this error when they build and debug an Office solution on their development computer, and then try to install the Office solution on the same development computer. To avoid this problem, use a different account to test the installer on the development computer, or use a different test computer. For more information about the event viewer, see Event Logging (2007 System).
Visual Studio 2008 SP1 also introduced ClickOnce manifests that do not need to be signed. However, Visual Studio Tools for Office relies on signed manifests to identify the publisher and determine if the Office solution is trusted. Optional signing is a feature in VS2008 SP1 that does not apply to Office developers. For more information about trusting Office solutions, see Granting Trust to Office Solutions (2007 System).
Mary Lee, Programming Writer.
Rachel Shaw, Program Manager.
PingBack from http://blog.a-foton.ru/index.php/2009/02/03/best-practices-for-deployment-with-visual-studio-2008-sp1-mary-lee-rachel-shaw/
Hi Mary and Rachel,
I developed 3 Addins in one solution, with an setup project (bootstrapper) to create one setup installer for the add-ins. Works for so far. Now I want the Addins to behave as clickonce apps. So the addins can check for new versions on a specified url. Is this possible, and how?
Rutger van Hagen
Setup projects do not have the automatic update capability like ClickOnce does. You can try to combine the the Setup project and ClickOnce deployment strategies as demonstrated in this section: http://msdn.microsoft.com/en-us/library/cc616991.aspx#VSTO3Solutions2_DeployingtotheClickOnceCache
another option: starting in VS2010 Beta1, ClickOnce does the capability to deploy multiple add-ins in a single installer. this way, you can deploy in a single installer, update a single location with new assemblies, and have the individual Office solutions look in that location for updates on a regular basis. for more information, see http://blogs.msdn.com/vsto/archive/2009/05/20/deploying-multiple-office-solutions-in-a-single-installer.aspx
Thanks for your answer!
Is it true that a VSTO solutin for Office 2003 applications does not support ClickOnce deployment?
Is is possible to use user / application settings, e.g. MyDll.dll.config, when using ClickOnce for Addins?
E.g. I would like to change a connectionstring located in a config file, after I have installed with ClickOnce..
I am creating a excel application using vsto 2008 + excel 2003.
I m going to publish output of my solution.
But when i tried to open this Excel workbook, i m getting a error
Office document customization is not avilable.
The Customization assembly could not be found or could not be loaded.you can still edit & save the document.Contact your administrator or author of this document for further assiatance.
Can any one guide me how can i resolve this issue?
Thanks & Regards,
Gaurav Jain begin_of_the_skype_highlighting
For assistance, please post your question in the VSTO forum at social.msdn.microsoft.com/.../threads