-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Consider logging assembly loads into the binlog #6303
Copy link
Copy link
Closed
Labels
Area: DebuggabilityIssues impacting the diagnosability of builds, including logging and clearer error messages.Issues impacting the diagnosability of builds, including logging and clearer error messages.Area: LoggingGood First IssueSelf-contained issues good for first-time contributors.Self-contained issues good for first-time contributors.needs-designRequires discussion with the dev team before attempting a fix.Requires discussion with the dev team before attempting a fix.triaged
Milestone
Description
We often have issues when MSBuild binaries are loaded from the GAC etc. Or NuGet/SDK binaries loaded from the wrong location. I think it would be beneficial to subscribe to AppDomain.CurrentDomain.AssemblyLoad and log all assembly loads, including full path to the .dll, assembly name, MVID, and maybe some attributes such as AssemblyFileVersion (which often contains the Git SHA).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Area: DebuggabilityIssues impacting the diagnosability of builds, including logging and clearer error messages.Issues impacting the diagnosability of builds, including logging and clearer error messages.Area: LoggingGood First IssueSelf-contained issues good for first-time contributors.Self-contained issues good for first-time contributors.needs-designRequires discussion with the dev team before attempting a fix.Requires discussion with the dev team before attempting a fix.triaged