The Phases of the ClickOnce Trust Prompt (Mary Lee)

Signing your Office solutions with a certificate is a mandatory step, but there are several optional steps that can change the way the certificate is presented to the end user or customer. This example uses a Visual Studio generated test certificate, but the dialog box is similar to what you would see if you are… Read more

Installing Office 2007/VSTO 3.0 Solutions on Computers with Office 2010 (Mary Lee)

You have probably been reading and hearing about Microsoft Office 2010 for some months. Now, you may be wondering how much work is necessary to install your existing Office 2007/VSTO 3.0 solutions on customer computers that have Office 2010. Perhaps you’re thinking about migrating the Windows Installer Setup projects or ClickOnce deploymen projects? The answer… Read more

When Do I Need to Deploy the VSTO Runtime? (Mary Lee)

Aaron wrote a great article about the VSTO runtime components earlier, which explained the Office extensions for .NET Framework 3.5 and Office extensions for .NET Framework 4. He also explained that starting in Microsoft Office 2010, the Visual Studio 2010 Tools for Office runtime is included and does not need to be deployed alongside your… Read more

Deploying the *.Utilities assemblies by using Windows Installer (Mary Lee)

Office solutions for .NET Framework 4 have dependencies on files that are distributed in the Visual Studio 2010 Tools for Office runtime, but there are also files outside of the runtime that are required for Office solutions to run on end-user computers. These files are the following: Microsoft.Office.Tools.Common.v4.0.Utilities.dll Microsoft.Office.Tools.Excel.v4.0.Utilities.dll Microsoft.Office.Tools.Outlook.v4.0.Utilities.dll Microsoft.Office.Tools.Word.v4.0.Utilities.dll For some information about… Read more

Why Should I Upgrade from .Net Framework 3.5 to .Net Framework 4 ? (Navneet Gupta)

I was chatting with some of my friends about Visual Studio 2010 and .Net Framework 4 and they asked me why should they move their application to .Net Framework 4, I am answering the question here for everybody to benefit. Frankly speaking there is no definitive answer; it is like there is no single pill… Read more

Why is FrameworkVersionMismatchException thrown? (Hamed Ahmadi)

The “Microsoft.VisualStudio.Tools.Applications.Deployment.FrameworkVersionMismatchException” is thrown due to the specific implementation of how VSTO 2010 runtime loads the appropriate CLR to install a VSTO customization. This exception is thrown when both .NET Framework 3.5 (CLR 2.0) and .NET Framework 4 (CLR 4) are installed on a machine and a VSTO customization which targets .NET Framework 4 is… Read more

Changes in the Security Model for Office Solutions (Mary Lee)

You can use two methods to trust an Office solution created in Visual Studio and not show a trust prompt to the end-user. Sign your Office solution with certificate that chains to a trusted root authority and is in the Trusted Publisher list. Sign your Office solution with a certificate and trust that certificate by… Read more

Deploying your VSTO add-ins to All Users (Saurabh Bhatia)

An often-requested feature for VSTO add-ins is the ability to install an add-in for all users of a machine. Misha Shneerson had blogged about a workaround to enable this scenario here. This workaround is not recommended. Now, deploying an add-in to All Users is supported for both Microsoft Office 2007 (through a hotfix) and Microsoft… Read more

VSTO 2010 Runtime components explained (Aaron Cathcart)

  During development of the VSTO 2010 Runtime we added a feature, dubbed Install on Demand, to support VSTO customizations that target both .NET Framework 3.5 and .NET Framework 4 without enforcing installation of both frameworks prior to installation of VSTO 2010. To facilitate this we needed to break the runtime into 3 components as… Read more

Visual Studio 2010: Specify advanced publishing options (Saurabh Bhatia)

I have previously posted how you can specify various properties for a VSTO solution like the Publisher and Product Names by tweaking a few files in Visual Studio 2008. With Visual Studio 2010 (Beta 2) you can edit these properties directly through the Publish Page. All Office projects in Visual Studio 2010 now have an… Read more