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.
Stamp Microsoft.DotNet.MSBuildSdkResolver.dll with Git SHA
See original GitHub issueI’m looking at Microsoft.DotNet.MSBuildSdkResolver.dll this version:
[assembly: AssemblyCompany ("Microsoft.DotNet.MSBuildSdkResolver")]
[assembly: AssemblyConfiguration ("Release")]
[assembly: AssemblyFileVersion ("2.2.100.0")]
[assembly: AssemblyInformationalVersion ("2.2.100-preview1-008633")]
[assembly: AssemblyProduct ("Sdk")]
[assembly: AssemblyTitle ("Microsoft.DotNet.MSBuildSdkResolver")]
[assembly: AssemblyVersion ("2.2.100.0")]
I’d like to find the source code to debug this .dll. I’m not sure if it’s SourceLinked and/or if the .pdb is embedded.
It would be nice to stamp the Git SHA into the .dll as an assembly-level attribute so it’s easy to pull the source code and check out the matching version.
Bonus: SourceLink the .pdb, make sure the .dll is deterministic and the .pdbs are portable and either published everywhere or embedded into the .dll.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
https://github.com/dotnet/cli/releases/tag/v2.2.202
https://github.com/dotnet/cli/commit/8a7ff6789d66a487bffc35aebb136621f5a1b3ee
No, I was investigating https://github.com/mono/monodevelop/issues/6335, we’ve found the problem in VSMac (no support for SDK resolver manifest .xml files).