-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Document 'Resolve Assembly Reference core scenarios' #8506
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Forgind
reviewed
Mar 2, 2023
JanKrivanek
reviewed
Mar 2, 2023
Forgind
approved these changes
Mar 20, 2023
JanKrivanek
approved these changes
Mar 21, 2023
rainersigwald
approved these changes
Apr 3, 2023
Co-authored-by: Rainer Sigwald <[email protected]>
Co-authored-by: Rainer Sigwald <[email protected]>
signalling to RAR that it doesn't have to open the assembly files to read their AssemblyRef tables. | ||
|
||
1. Project references. When a project depends on another project, the output file of the dependency is passed to RAR. Alternatively, a project may directly | ||
reference a random file o disk, resulting in the same code path. Unlike SDK and NuGet, these references are not pre-resolved and RAR must open the assembly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"file on disk"
This was referenced Jul 29, 2025
Closed
Closed
This was referenced Oct 15, 2025
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area: Documentation
Issues about docs, including errors and areas we should extend (this repo and learn.microsoft.com)
merge-when-branch-open
PRs that are approved, except that there is a problem that means we are not merging stuff right now.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #8441
Context
This document aims to capture the core functionality provided by the ResolveAssemblyReference task when building .NET (Core - pun intended) projects. The goal is to rationalize and optimize the task, ultimately achieving substantially better performance and crossing out RAR from the list of notoriously slow build tasks.
Changes Made
Added the document (preview link).