At the moment when debugging static graph-based restores, an MSBuild binary log is created automatically. However, when repositories are quite big, I've noticed that the MSBuild portion of the restore takes a long time. This is because the MSBuild binary logger is including all of the project evaluations, imports, and misc files.
Desired Behavior
I had static graph-based restore automatically generate a binary log when debugging as a convivence when developing the feature. However, now its probably not necessary.
NuGet Product(s) Affected
MSBuild.exe, dotnet.exe
Current Behavior
At the moment when debugging static graph-based restores, an MSBuild binary log is created automatically. However, when repositories are quite big, I've noticed that the MSBuild portion of the restore takes a long time. This is because the MSBuild binary logger is including all of the project evaluations, imports, and misc files.
Desired Behavior
I had static graph-based restore automatically generate a binary log when debugging as a convivence when developing the feature. However, now its probably not necessary.
Additional Context
No response