Mihai Codoban

This would be so useful. I constantly open new tabs on some focused work, start splitting panes within the tab, and then at some point decide to move the whole...

Why not do it in a static constructor from a type that does not reference any other type? Excluding the usual caveats with exceptions from type constructors. ```c# class LoadMSBuild...

Only option I know is to change the machine's language.

+1 for replacing the .sln file with native msbuild files. This probably implies implementing lineup files in one form or another (see lineup files in #1493). And then, probably, also...

This would probably also be the solution to making the notorious `nuget pack` work with static graph builds: https://github.com/dotnet/msbuild/issues/6197

@wjk this section describes how to let static graph know what targets projects call each other with: https://github.com/Microsoft/msbuild/blob/master/documentation/specs/static-graph.md#inferring-which-targets-to-run-for-a-project-within-the-graph As you've noticed, we've added the managed sdk specification in Microsoft.Managed.targets, because...

> @cdmihai, if this is not implemented as part of the official SDK yet, maybe specifying the target protocol at the repo level is an option? I'm not super familiar...

Depending on time, I might look into fixing this. If anyone gives me a head start, please say something in this issue.

We could also require people to re-compile their tasks against .net core assemblies, which would make them work on full framework as well. But this would not be a transparent...

On Full Framework MSBuild populates a list of all valid culture names [via `CultureInfo.GetCultures`](https://github.com/Microsoft/msbuild/blob/xplat/src/XMakeTasks/CultureInfoCache.cs#L26). That method does not exist on .Net Core, so we just use the [hardcoded list FF...