Description
The new moniker for .NET 6.0 (net6.0) is soon coming to the SDK.
I was told by @ViktorHofer that once dotnet/runtime#42709 gets merged it should be a matter of +- 2 weeks until it's recognized by .NET SDK.
Currently, when I am using benchmarks_ci.py -f netcoreapp5.0 it downloads .NET 6.0 bits from the master channel. It's fine as long as I don't want the actual .NET 5.0 (my current use case). I know that it's possible to specify the channel in an explicit way like the CI does.
@billwert @ooooolivia would it be OK if I send a PR that adds support of net6.0 to the python scripts? It would internally map to the master channel installers and existing net5.0 moniker. I would change the net5.0 mapping to use the .NET 5 channel. And when the SDK starts to recognize net6.0, I would send a new PR with the removal of artificial mapping to older tfm for 6.0
I am not sure if my description explains it correctly, but basically what I would like to do is:
channel_map = {
'master': {
- 'tfm': 'netcoreapp5.0',
'branch': 'master'
},
channel_map = {
'master': {
+ 'tfm': 'net6.0',
'branch': 'master'
},