Michael Yanni

We would not use a roslyn-tools for this action. There is likely a way to do this via the automated VS insertion process, to be done in: https://github.com/dotnet/project-system/issues/7911

The original solution in https://github.com/dotnet/project-system/pull/8517 did not work. The multi-repo triggering mechanism requires that the repo containing the YAML file **also** be within the same AzDO org. This was not...

I finally hit this in CI, even with the `/m` flag. So, it is definitely possible to hit randomly while the build runs on multiple processes.  https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=6549829&view=results

Another failure here: https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=6966047&view=results

@jonathanchapmanmoore Our repo currently can be built using only the VS Build Tools, but you need to specify that the VS extension should not be deployed. Also, the tests will...

@jonathanchapmanmoore We decided to not support Visual Studio Build Tools as an option for building this repo. If you need a free way to build it, you can use the...

Looks like there is a way to configure Apex tests publicly, but they run through DartLab. The configuration script is produced as part of a build artifact, so it doesn't...

Putting this back for review since it seems the work on this was being complicated by roslyn-tools. Since we don't use roslyn-tools anymore, this is likely easier to do. Personally,...

I've ended up figuring it out after running into an issue that Andrew actually created. https://github.com/dotnet/sourcelink/issues/492 PR will be created shortly.

This issue will be for discussing/deciding if publishing our packages to NuGet.org on a regular basis actually provides any benefit to anyone. At this point in time, I don't know...