Rearrange tfms for intellisense in vscode and visual studio

[Anipik]

Fixes #36799

The intellisense always picks up the first tfm in tfms to resolve the references, so the first one needs to be netcoreapp-*

[ghost]

Tagging subscribers to this area: @ViktorHofer
Notify danmosemsft if you want to be subscribed.

[ViktorHofer]

so the first one needs to be netcoreapp-*

What about netstandard-only projects?

[safern]

Is this something we will have to live with? Like we use to do with, /t:UpdateVSConfigurations? If so, is there a way we can improve/fix this in a better way?

[Anipik]

What about netstandard-only projects?

The intellisense will work if the ref folder is populated with the correct reference assemblies.

Is this something we will have to live with? Like we use to do with, /t:UpdateVSConfigurations? If so, is there a way we can improve/fix this in a better way?

We can have designTimeBuild protection on ci which can help us catch these errors before they are introduced. I have an issue tracking that.
We can write a msbuild task to check that none of our quirks are violated.
We have a couple of them (Having all the tfm derived properties in the second property group).

[ViktorHofer]

Got it thanks. Then I don't think we need any protection for this as I'm currently working on getting rid of the upfront restore necessity hence the order of tfms shouldn't matter going forward.