Comment by delaconcha
3 months ago
Just install the .NET SDK, and you’re ready to go.
> Nuget is complete and utter garbage. You still have to resort to all forms of unreliable hacks in order to redirect it to a locally clone
How so, you can use a nuget.config in your project and use your local packages fairly easy, seems in part with npm and the likes.
"Just" is an incredibly obnoxious word when used in the way that you have.
> Just install
Not on Debian? Have fun with that. You'll also need the Azure SDK. And what about openssl-dev? Oh no, you installed dotnet on Windows instead of within WSL? Start again.
No, you don't "just install" the SDK. There is a lot that the IDEs set up for you.
> Local nuget.config
I don't see how adding a nuget config improves anything. You have completely omitted what you place inside of it to make it build and use a local clone of the package source.
Look at all this nonsense that people have resorted to: https://stackoverflow.com/questions/32482746/how-to-temporar...
In my experience installing the .NET SDK is fairly simple in any platform, well documented and supported.
Nuget.config allows to configure your local feeds, this implies you have a local feed with the required packages.
Another option is to push the local build packages to you local NuGet cache.