codingadventures / LINQBridgeVs

Dumps the content of variables during debugging in Visual Studio to LINQPad
MIT License
127 stars 21 forks source link

AssemblyResolutionException: Failed to resolve assembly: 'netstandard' #52

Closed sentry-io[bot] closed 5 years ago

sentry-io[bot] commented 5 years ago

This is one of many assembly resolution exception errors. A warning message should be showed in case LINQBridgeVs is used with netstandard, asp.net core, .net core and other unsupported projects

Sentry Issue: LINQBRIDGEVS-J

AssemblyResolutionException: Failed to resolve assembly: 'netstandard'
  Module "Mono.Cecil.BaseAssemblyResolver", line 116, in Resolve
    Mono.Cecil.AssemblyDefinition Resolve(Mono.Cecil.AssemblyNameReference, Mono.Cecil.ReaderParameters)
  Module "Mono.Cecil.DefaultAssemblyResolver", line 29, in Resolve
    Mono.Cecil.AssemblyDefinition Resolve(Mono.Cecil.AssemblyNameReference)
  Module "Mono.Cecil.MetadataResolver", line 56, in Resolve
    Mono.Cecil.TypeDefinition Resolve(Mono.Cecil.TypeReference)
  Module "Mono.Cecil.TypeReference", line 0, in Resolve
    Mono.Cecil.TypeDefinition Resolve()
  Module "Mono.Cecil.Mixin", line 0, in CheckedResolve
    Mono.Cecil.TypeDefinition CheckedResolve(Mono.Cecil.TypeReference)
...
(22 additional frame(s) were not displayed)

Error Executing MSBuild Task SInjectionBuildTask
sentry-io[bot] commented 5 years ago

Sentry issue: LINQBRIDGEVS-M

sentry-io[bot] commented 5 years ago

Sentry issue: LINQBRIDGEVS-K

sentry-io[bot] commented 5 years ago

Sentry issue: LINQBRIDGEVS-N

codingadventures commented 5 years ago

fixed in the next release