3 ms·
What exactly is wrong with NuGet? It's very simple, I think you just didn't give it a chance For example a month ago Facebook broke .net's built in social logi
by mattmanser 10y ago
What exactly is wrong with NuGet? It's very simple, I think you just didn't give it a chance
For example a month ago Facebook broke .net's built in social login, all installed with NuGet, so I ran a single command and it was fixed.
If you're talking about front end, NuGet can handle it, or the recent versions of VS have a built in task runner that you can easily setup to run Gulp, Grunt, Yarn, Bower, whatever, if you so desire on build/debug/etc.
There are things to hate about the .Net ecosystem (TFS, I'm looking at you), but NuGet ain't one of them.
- partycoder 10y agoSo far what I have seen with .NET project files is that: people modify them, VS generates code into those files, and they contain a lot of stuff. As a result, they're very painful to manage when trying to troubleshoot issues. Then, because the project files get modified all the time it's a constant source of conflicts in version control.
- ygra 10y agoIf project files get modified all the time then either you're constantly moving, adding, or removing files from the project, or constantly changing configurations and build settings. Neither should really happen constantly.
- Sacho 10y agoThis is an issue addressed in the new .NET Core project templates, which are organized to limit the times VS would touch them.