1

Closed

Unable to Load on 64 bit Vista

description

Thanks for creating the fantastic program. I installed it a few days ago on my XP workstation and I have really enjoyed it. I recently tried to install it on my Windows Vista Machine (running Vista Ultimate) and was unable to get the COM to load. I then downloaded it and tried to build from source. It still would not load. Here is the stack trace.
 
Customization could not be loaded because the application domain could not be created.
 
 
************** Exception Text **************
Microsoft.VisualStudio.Tools.Applications.Runtime.CannotCreateCustomizationDomainException: Customization could not be loaded because the application domain could not be created. ---> System.IO.FileLoadException: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)
at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Activator.CreateInstance(String assemblyName, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo, StackCrawlMark& stackMark)
at System.Activator.CreateInstance(String assemblyName, String typeName)
at System.AppDomain.CreateInstance(String assemblyName, String typeName)
at System.AppDomain.CreateInstanceAndUnwrap(String assemblyName, String typeName)
at System.AppDomain.CreateInstanceAndUnwrap(String assemblyName, String typeName)
at Microsoft.VisualStudio.Tools.Office.Runtime.DomainCreator.CreateCustomizationDomainInternal(String documentFullLocation, String documentName, String assemblyLocation, Boolean showUIDuringDeployment, IntPtr hostServiceProvider, IntPtr& executor)
--- End of inner exception stack trace ---
Closed May 7, 2010 at 3:28 PM by JohanDanforth

comments

RobertSOakes wrote Nov 21, 2008 at 5:33 AM

I did a bit of research on the error and what it might require to reproduce it, this post here describes my scenario exactly. I also have the Microsoft Math Add-In installed. This is very likely th source of the problem. I think I may spend a few minutes and see if I can create a workaround. I will let you know if I am successful.

http://blogs.msdn.com/vsod/archive/2008/11/01/vsto-2008-throws-cannotcreatecustomizationdomainexception-when-microsoft-word-math-add-in-is-installed.aspx

RobertSOakes wrote Nov 21, 2008 at 6:25 AM

I just spent a bit of time experimenting. It appears that the problem is due to having two instances of the IDTExtensibility2 running at the same time.

After uninstalling the Microsoft Math add-in, I was able to install, load and use Writespace without difficulty. I also attempted to create a shim com object (per the instructions in the above hyperlink). However, I received errors. Given the time of night, I wasn't tremendously excited to pursue solutions to the problems.

Anyhoo, best of luck with your project.

JohanDanforth wrote Nov 21, 2008 at 8:30 AM

Robert, thanks for the help digging into this. You really get an understanding of the difficulties involved with product development and all the testing that must be involved to get them, and especially add-ins, working on different computers :D

wrote Nov 21, 2008 at 8:37 AM

wrote Feb 7, 2010 at 12:29 PM

wrote Feb 7, 2010 at 12:29 PM

wrote Feb 7, 2010 at 12:31 PM

wrote Feb 7, 2010 at 12:31 PM

wrote May 7, 2010 at 3:28 PM

wrote Feb 14, 2013 at 1:35 AM

wrote May 16, 2013 at 8:09 AM