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.
Any further work on this should be based on #3914.
Are there any future plans to revive the following PRs https://github.com/microsoft/msbuild/pull/3914 and https://github.com/microsoft/msbuild/pull/3868?
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):
https://github.com/dotnet/msbuild/blob/15307131458845313df37549b1e25c5076519809/documentation/specs/rar-as-service.md#L19
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
Most helpful comment
I have just started working on this issue.