Forgind

Bug reports that get moved to MSBuild via mover software don't automatically receive MSBuild labels like untriaged, which means they can easily fall through the cracks. Example: https://github.com/dotnet/sdk/issues/26711

- [x] When VS main snaps to `17.4`, create `vs17.3` branch - [ ] When VS main snaps, set change 17.3 loc branch from `main` to `vs17.3` and file a...

Waiting for arm machines to be cheaper.

Avoid building dwproj

10

Mitigates #2064 ### Context This is an alternate way to fix the same problem. This is incomplete: it would still need to replace "dwproj" with the !projectsKnownToBeMSBuild and add a...

This adds to event sources to let loggers access them independently.

Look into merging MSBuild's RAR caching and the SDK's assembly (?) caching

7

Look into what they have in common. Merge the caching to some extent. Possibly merge the code paths? Possibly only run it once and share the results? Specifically ProcessFrameworkReferences and...

I considered making a "documentation" folder for this, but I'd slightly prefer to wait on that until we have several things to put there. If you disagree, I can make...

 vs.     Still to do: drop into vsix. Fixes #67

Indicates whether Roslyn is included

1

Fixes #22 I didn't see an obvious way to determine whether the C# compiler was installed for the dotnet sdk, and I didn't want to replicate all the logic from...

Fixes #7920 ### Context When a task ships MSBuild assemblies, we try to load both those assemblies and the assemblies next to MSBuild. This confuses the MetadataLoadContext. We should just...