dotnet / dotnet/vscode-csharp

Microsoft.VisualStudio.VIL.DebuggerHost.BinaryResolutionFailureException during expression evaluation

Open
#780 0 comments 0 reactions 1 assignee Claimed by @wesrupert View on GitHub
Bug Debugger OmniSharp
Dominant language
TypeScript
Stars
3.1k
Forks
737
Avg merge
17h 56m
Merged PRs (30d)
21

Description

The following error stack is the 2nd most non fatal error we are encountering in the debugger. While we know there are cases where we won't be able to resolve the assembly, we didn't think those would be hit frequently:

at Microsoft.VisualStudio.VIL.DebuggerHost.FusionHelper.LoadAssemblyByName(AssemblyResolver resolver, AssemblyName assemblyName, Boolean fThrowOnError, IList`1 specialCasedAssemblies)#N# at Microsoft.VisualStudio.VIL.DebuggerHost.AssemblyResolver.ResolveAssembly(AssemblyName name, Boolean fThrowOnError)#N# at Ilrun.CachedTypeUniverse.AssemblyResolutionCache.LookupAndAddCachedResolution(String typeName)#N# at Ilrun.CachedTypeUniverse.ResolveAssembly(Module scope, Token tokenAssemblyRef, String typeName)#N# at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)#N# at Ilrun.ModuleEntry.ResolveTypeRef(CachedTypeRef typeRef)#N# at Microsoft.MetadataReader.TypeProxy.Equals(Type t)#N# at Microsoft.VisualStudio.VIL.VisualStudioHost.VilEvaluationServices.Find_ToStringMethod(Type type, ITypeUniverse universe)#N# at Microsoft.VisualStudio.VIL.VisualStudioHost.VilEvaluationServices.EvaluateToString(DkmInspectionContext inspectionContext, VilEvaluationResult evalResult)#N# at VSDeb

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.