You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It maybe have. been discussed that global.json at the root is a bit problematic under several aspects.
I suggest the dotnet sdk supports a better default location for it, most likely under .config, in the most agreed upon fashion, possibly based on feedback from people using many stacks without dotnet necessarily being the most prominent, just to make sure we aren't clashing with the world.
it may also impact the default location for .config/dotnet-tools.json, which is right now, the right location; but maybe it would be under .config/dotnet/tools.json according to how this feature suggestion fares.
It maybe have. been discussed that
global.json
at the root is a bit problematic under several aspects.I suggest the dotnet sdk supports a better default location for it, most likely under
.config
, in the most agreed upon fashion, possibly based on feedback from people using many stacks without dotnet necessarily being the most prominent, just to make sure we aren't clashing with the world.it may also impact the default location for
.config/dotnet-tools.json
, which is right now, the right location; but maybe it would be under.config/dotnet/tools.json
according to how this feature suggestion fares.related:
.fsharp
folder to make all fsharp tooling more cohesive fsharp/fslang-suggestions#1339The text was updated successfully, but these errors were encountered: