Unhandled exception error for Valuedump.
Closed this issue · 1 comments
When I attempt to run Valuedump after using Questor for several hours, I get the following error in the console:
Unhandled exception in application.
Outer Exception: System.BadImageFormatException: Invalid assembly file format. (Exception from HRESULT: 0x8013141D)
at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.Load(String assemblyString, Evidence assemblySecurity)
at System.AppDomain.ExecuteAssemblyByName(String assemblyName, Evidence assemblySecurity, String[] args)
at System.AppDomain.ExecuteAssemblyByName(String assemblyName)
at System.AppDomain.ExecuteAssemblyByName(String assemblyName)
at LavishVMRuntime.LVMDomainManager.AsEx.NewExecuteAssembly2()
at LavishVMRuntime.LVMDomainManager.AsEx.NewExecuteAssembly()
at LavishVMRuntime.LVMDomainManager.AssemblyExecuter(Object Obj)
However, If I run it just after logging in, it'll load up fine.
This happens with compiles from the master, experimental and several of the branch's code.
Figured out a way to still use VD from a script.