Davis Goodin

Core-Setup uses `use_installed_dotnet_cli=false` to prevent roll-forward behavior because the SDK has breaking changes between versions, yet I ran into this problem when it used the installed SDK anyway. So in...

It sounds like Arcade is inconsistently blocking roll-forward: (I guess because of the "is .NET Core installed?" capability test) > If the roll-forward is desired, I'd expect it to be...

TIL `msbuild.ps1/sh` isn't a standard Arcade script--I thought it was meant to be a way to handle automatic bootstrap and some Arcadey params when you need to call a specific...

> 1. Could you confirm whether your custom build script (`eng/run.ps1 build`) performs a fresh build of the sources that you want to analyse every time it is run? This...

For now, to get unblocked, we are stopping trying to analyze the Go source using CodeQL in GitHub Actions, instead focusing on the util code in the repo which doesn't...

We don't run the multiple-toolset bootstrap process in our own scripts, we just set up the environment and let the standard upstream process (https://go.dev/doc/install/source) do the rest. Letting it do...

Also prevents issues like https://github.com/dotnet/standard/issues/948 if Darc somehow manages to make an unfetchable branch again.

> Separately, I don't really like controlling the stages using those variables/conditions because it seems fragile to me - esp. because variables are mutable and can be set by any...

Why in this repo, rather than the repos where these installers are built? (There's also some tooling in dotnet/runtime and dotnet/windowsdesktop for readme tables.)

@gdams is planning to take a look at this and figure out if it makes sense for us to try to contribute to the .NET code or go with the...