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.
GenerateReferenceSource should follow type forwards so we can update based on changes to S.P.Corelib
See original GitHub issueIt appears as though running /t:GenerateReferenceSource does not currently pick up that the actual sources live in S.P.Corelib (or another assembly) but are exposed as part of a given projects ref assembly.
We should likely follow the TypeForward and use System.Private.Corelib to validate the exposed surface is up to date.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Commits to .NET Core 2.1
It will roll-forward to the CLI runtime (2.1.0) through minor version ... We can manually update release/2.0 if necessary, but LTS is always...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That’s already defined by the typeforwards in the src assembly that GenerateReferenceSource operates on.
GenAPI supports exclusions. https://github.com/dotnet/arcade/blob/5c40ffc8d160681c1ff39f69ec8fd893795bd520/src/Microsoft.DotNet.GenAPI/Program.cs#L42
No, I think this can be closed.