-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[RAR] As a customer, I want implicitly cached references so that MSBUILD builds faster #3139
Comments
Any further work on this should be based on #3914. |
I have just started working on this issue. |
The work is tracked as a project: https://github.com/dotnet/msbuild/projects/35 |
The spec document suggests that Bond has been discontinued (therefore PR #3914 was not completed):
Is it correct? I could not find any reference to Bond being discontinued. The latest release was made just 19 days ago: https://github.com/microsoft/bond/releases ( brew install bond gave me the latest v9.0.1 of Bond on macOS).
|
I was also confused by that. But it was pointed out to me, that this is some unusual activity in that repo (https://github.com/microsoft/bond/graphs/code-frequency). |
Note: I have converted issue to epic, for tracking purposes |
This issue is marked as stale because feedback has been requested for 30 days with no response. Please respond within 14 days or this issue will be closed due to inactivity. |
. |
The early performance numbers did not merit continuing on this delivery thread. Thus, we are parking this user story. |
RAR (Resolve Assembly References) as a service.
We have many issues related to the fact that ResolveAssemblyReferences a) must run for every build, including no-op incremental builds and b) is slow.
Creating a long-lived process as a cache for assembly information and so on could have a big impact on build perf, including design-time builds.
Note: This is a draft/proposed user story and not committed for .NET 6.0 yet.
Issues:
Outdated issues:
The text was updated successfully, but these errors were encountered: