Problem after installing VSTO runtime 2010 and .Net framework 4

Question

Our entire team was installed VS 2010 (it has both VSTO runtime 2010 and .net framework 4). After installation, some of our developers get the error below (but for most of them it works fine), opening a deployed VSTO application from a server developed in 3.5 and VSRO runtime 3:

***** Exceptional text ******* Microsoft.VisualStudio.Tools.Applications.Runtime.CannotCreateCustomizationDomainException: the setting does not have the permissions necessary to create the application domain. ---> System.Security.SecurityException: the custom functions in this application will not work, because the administrator has listed the file: //fmrdmwaprd2/CA-INSTALL/Demand/Templates/GeoDSS_Templates_UTT/APAC_RevOpt_OEM_Good_Bad_News/APAC_RevOt_adewtut_adewtut_ovewptutadvt_adewtwt_vew_ptvut_adwt_advt_advt_advt_advt_advt_advt_advt_advt_advt_advt_advt_advt_advt_advt_advt_advt_advt_advt_advt_add_new_tw. Contact your administrator for further assistance. at Microsoft.VisualStudio.Tools.Office.Runtime.RuntimeUtilities.VerifySolutionUri (Uri uri) at Microsoft.VisualStudio.Tools.Office.Runtime.DomainCreator.CreateCustomizationDomainInternal (String solutionLocation, String manifestName, String documentNamerpurmenterpumentleurpumentleurpumentleurpumentleurpumentleurpluentrlementpluentrturpu executor) Build failure zone: MyComputer

Answer 1

It appears that your computers have "trust issues." Here is a link to more information about trust levels for different locations / elements and how to change them:

http://msdn.microsoft.com/en-us/library/6exya3kf(v=vs.80).aspx

I also found this SO article, which may be close enough to your problem to help you:

Installing VSTO 4.0 causes VSTO 3.0 Addin to stop working

Answer 2

I ran into this problem and solved it. This is because VSTO creates a custom AppDomain at boot time for VSTO AddIn. The action uses Shadow Copy to copy VSTO.DLL to a temporary location and loads it from there.

Anti-virus tools such as McAfee actively kill this shadow copy operation, so AddIn will not load onto protected computers or with tight security permissions.

To bypass the shadow copy, ask the installer to place your .DLL AddIn in the global assembly cache. With its help, the Shadow Copy process is avoided in the GAC and the .DLL is loaded.

Keep in mind - this can cause development problems, so do not deploy .DLL to the GAC on your development machine. If you do this, you will not be able to run your changes in Visual Studio (the DLL in the GAC will work instead).