C
Join ServerC#
help
❔ Managing `global.json` with JebBrains Rider?
CWM3cat whisperer mk. 31/25/2023
I'm trying to get it to follow/manage a
When I right click my solution in rider and hit the manage .NET SDK option, I only get these options:
global.json
file at the root of my solution but I can't get it to work and something seems broken. I have the following SDKs installed on my computer:❯ dotnet --list-sdks
6.0.100-preview.7.21379.14 [/usr/local/share/dotnet/sdk]
6.0.100-rc.1.21458.32 [/usr/local/share/dotnet/sdk]
6.0.100-rc.2.21505.57 [/usr/local/share/dotnet/sdk]
6.0.100 [/usr/local/share/dotnet/sdk]
6.0.200 [/usr/local/share/dotnet/sdk]
6.0.300 [/usr/local/share/dotnet/sdk]
6.0.302 [/usr/local/share/dotnet/sdk]
6.0.400 [/usr/local/share/dotnet/sdk]
6.0.401 [/usr/local/share/dotnet/sdk]
6.0.405 [/usr/local/share/dotnet/sdk]
7.0.100 [/usr/local/share/dotnet/sdk]
7.0.102 [/usr/local/share/dotnet/sdk]
When I right click my solution in rider and hit the manage .NET SDK option, I only get these options:

CWM3cat whisperer mk. 31/25/2023
The dropdown only has "6.0" and "7.0" and selecting either of them and any roll-forward policy doesn't create a
global.json
or modify an existing one.Ttebeco1/25/2023
my first advice here is to uninstall all your installed SDK but 2
Ttebeco1/25/2023
keep tje lastest 6.0.x and 7.0.x
Ttebeco1/25/2023
so only
6.0.405 [/usr/local/share/dotnet/sdk]
7.0.102 [/usr/local/share/dotnet/sdk]
Ttebeco1/25/2023
if you had "actual preview/rc" I would tell you to keep them too but you don't have any
Ttebeco1/25/2023
the only alpha/preiew/rc that exists today are from the 8.0.x
Ttebeco1/25/2023
you'll save about 2 GByte doing that cleanup
Ttebeco1/25/2023
When I right click my solution in rider and hit the manage .NET SDK option, I only get these options:
Ttebeco1/25/2023
well your screen is not showing much
Ttebeco1/25/2023
it's showing 2 combo and a checkbox
Ttebeco1/25/2023
which are the thing
global.json
CAN haveTtebeco1/25/2023
but it's not clear what are the list of values inso the combo box
AAccord1/26/2023
Was this issue resolved? If so, run
/close
- otherwise I will mark this as stale and this post will be archived until there is new activity.