Add a new net6.0 TargetFramework

[Anipik]

• adding a new target framework net6.0
• making coreclr tool target net5.0
• make packages containing net5.0 exclude netcoreappcurrent

[ViktorHofer]

Can you please verify if vstest still works? I believe the xunit.visualstudio package and vstest were hardcoding on checking for "net5.0" of "netcoreapp". cc @nohwnd

[nohwnd]

@ViktorHofer yes, it should work. The change that caused that problem was rolled back somewhere between Preview8 and 5.0.100-rc.1.20451.10.

[Anipik]

@marek-safar @akoeplinger can you help with the browser errors here ? i m not aware how everything is put together.
From the error it seems an bin log it seems like that $(CORE_ROOT) property is not getting set.

[Anipik]

@ViktorHofer @ericstj @safern this one is complete, can you please take a look ?

[ViktorHofer]

Why are these properties needed? Don't we want to set a tfm here? cc @ericstj @trylek

[ViktorHofer]

Cool 👍👍

[ViktorHofer]

@Anipik before merging, please validate if building and testing inside Visual Studio still works. Also please validate that dotnet test on the CLI still works (we don't protect that yet in CI).

[Anipik]

@Anipik before merging, please validate if building and testing inside Visual Studio still works. Also please validate that dotnet test on the CLI still works (we don't protect that yet in CI).

1. Package sizes are same before and after the change
2. Dotnet test works from the CLI
3. Able to build projects form VS (we still get duplicate tfm error while restoring from the VS)
4. We are able to run tests using the VS

[Anipik]

Merging the change as failure is known and we have a tracking issue.

[ViktorHofer]

Note that this is a breaking change which ideally would go trough a monthly rollout. Please send out a mail to the team explaining why this was merged now and what the breaking change is about.