In my entire career I have never, not even once, seen any benefit from having a global.json file in the repo. However, I have seen countless times, over and over again that a repo fails to build because the right SDK is not installed, and deleting global.json makes it build just fine. - ThreadSky

About ThreadSky

kirillosenkov.com • 10 days ago

In my entire career I have never, not even once, seen any benefit from having a global.json file in the repo.

However, I have seen countless times, over and over again that a repo fails to build because the right SDK is not installed, and deleting global.json makes it build just fine.

Comments

gulbanana.au•10 days ago

i have used them temporarily to work around sdk bugs, but they are tech debt to be removed asap

cellivar.dev•10 days ago

We ship an SDK package for internal use that helps manage the versions of other packages. It itself is versioned via global.json and we don't put anything else in there. Keeping it simple has helped.

aaron-powell.com•10 days ago

I was just thinking about this week as I was, yet again, trying to work out why I couldn't build a project.

rocky.lhotka.net•10 days ago

I find them indispensable locally, as I almost always have beta versions of #dotnet installed and that frequently causes issues with existing apps.

I wish there was a good solution to this overall issue.

fransbouma.com•10 days ago

If the ASP.NET team doesn't run into it, it won't get a proper fix

ryzngard.dev•10 days ago

Seems likely it would be good for CI to enforce toolkit for testing / release, but local it's a pain

flensrocker.de•10 days ago

Should we have something like "dotnet tool restore", maybe "dotnet sdk restore"?
But I agree, I have deleted some global.json in the past...

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply