FCS solution requires install of globals.json .NET SDK version to open

[auduchinok]

I can workaround it by either allowing more SDK versions (#10130) or by installing the particular SDK version from global.json. Since the latter is not required in readme/devguide, other people, especially newcomers, will likely also get hit by it. I think we should allow any suitable SDK version to be used locally to reduce developer pain.

[abelbraaksma]

This appears to be true now for all solutions in the F# repo, see #10193. This is quite the blocker for working with the F# solutions. How are others dealing with this, nobody using VS anymore?

This behavior is only so since a few days/weeks afaik, what change caused this? Seeing that #10130 was canceled, I wonder how others are dealing with this.

[auduchinok]

This is quite the blocker for working with the F# solutions. How are others dealing with this, nobody using VS anymore?

We've been using an older branch from August for the recent PRs and rebased the changes on main. The inability to use dotnet build is a much bigger blocker for us, since it's what Rider uses to build a solution (to have reproducible builds in console/CI), so we're just waiting when we'll be able to contribute to FCS normally again.

[abelbraaksma]

I can workaround it by either allowing more SDK versions (#10130) or by installing the particular SDK version from global.json.

@auduchinok, at least for VS I found a manageable workaround with an undocumented environment variable: #10193 (comment) that doesn't require installing the SDK separately.

Though as of yet, I don't seem to have dotnet build working, nor .dotnet\dotnet build (using the one installed on build), at least not on my machine, but I don't know if it ever worked for me, tbh: I just use VS and/or build.cmd.

[cartermp]

This should now be resolved since, finally, the build machines we rely on were updated.