question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support WhereRefBind log entries

See original GitHub issue

I’ve been using Fusion++ today, it’s a great tool!

I noticed that it looks like it may not support all entries. Specifically if I run fuslogvw.exe and specify log all binds to disk, I may get files with this format: WhereRefBind!Host=(LocalMachine)!FileName=(Microsoft.Build.NuGetSdkResolver.dll).htm

These don’t seem available in Fusion++.

To get a repro:

  1. git clone https://github.com/dotnet/msbuild (assuming you cloned into C:\MSBuild), checkout main as of 2021-03-24 (e.g. https://github.com/dotnet/msbuild/commit/bf0b0c52351d2034daec62b74c49f67def7fe739)
  2. build -bl /p:CreateBootstrap=true
  3. C:\msbuild\artifacts\bin\bootstrap\net472\MSBuild\Current\Bin\MSBuild.exe /r C:\temp\net472\net472.csproj where net472.csproj is any dotnet C# project. Note /r is important as the codepaths involve NuGet

Run step 3 under fuslogvw and Fusion++ and compare the results.

https://github.com/dotnet/msbuild/issues/6289 is the issue we’re investigating. Looks like we first load an assembly using Assembly.LoadFrom(), which loads it into the LoadFrom context, then we load the same .dll into the default load context, so we have two copies of the assembly loaded from two different codepaths, then we get the exception.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:2
  • Comments:10 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
davkeancommented, Jun 29, 2021

WhereRef binds are situations where the assembly name hasn’t been set; think Assembly.LoadFrom(“foo.dll”).

1reaction
awaeschercommented, Apr 15, 2021

Version 1.4 was just released 🎉

Thank you for the feedback, Kirill.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Fuslogvw.exe (Assembly Binding Log Viewer)
Use Fuslogvw.exe, the Assembly Binding Log Viewer. ... By default, log entries are stored in per-user directories on disk in the wininet ...
Read more >
Fusion Log Viewer (fuslogvw.exe)
Enable Fusion Logs so that you can see where the binding is failing. There are two ways to enable it: Registry Editor; Fusion...
Read more >
Assembly Binding Issue in asp.net web application ...
*** Assembly Binder Log Entry (6/28/2018 @ 4:18:03 AM) *** The operation failed. Bind result: hr = 0x80070002. The system cannot find the...
Read more >
Back to Basics: Using Fusion Log Viewer to Debug ...
You probably have a tool to help on your development system already. Type "Fusion" in the Start Menu. The Assembly Binding Log Viewer, ......
Read more >
Fusion Log Viewer - Lycangeek
The first thing is to get the logger to record all log attempts – not ... If you see either WhereRefBind or something...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found