Eric StJohn

@sharwell pointed me to how Razor does this https://github.com/dotnet/sdk/blob/2fea637fd7dcc56a8d29329dd0c28de4309bd5f4/src/RazorSdk/SourceGenerators/RazorSourceGenerator.RazorProviders.cs#L17 cc @captainsafia That's pretty cool that we could use .editorconfig to make generator-specific settings. Perhaps one thing we could do here...

One thought is that we could have a property or item like "DisabledSourceGenerators" and pass that in via https://github.com/dotnet/roslyn/blob/2946c619d91c7279d69d71bbb521ea4647e29fc1/docs/features/source-generators.cookbook.md#consume-msbuild-properties-and-metadata then have all generators honor that in their Initialize methods. Seems...

@maryamariyan and @sharwell were discussing this. We'd like to see something land for 6.0 if possible.

The premise of my original request was that asking folks to muck with `Analyzers` via a target might not be something we want to do if we have to do...

@jaredpar / @chsienki -- will this be part of the .net 6.0 / roslyn 4.0 release? I think that's what the milestone 17.0 means but I wanted to confirm. Thanks!

First off the aka.ms link doesn't exist for datasets/cifar10.zip. I took a look at the blob storage under `datasets` and didn't see the cifar10.zip there. @michaelgsharp do we have this...

/azp run

@alexperovich why are we manually changing things under eng/common -- shouldn't we instead just flow arcade?

/azp run MachineLearning-CI

cc @mmitche @ViktorHofer @markwilkie This refers to the conventions described in https://github.com/dotnet/arcade/blob/e7ede87875f41a9b3df898ae08da5ebc96e24f56/Documentation/ArcadeConventions.md#dependent-packages-version. Changes could potentially impact darc as well.