NuGet is great - but yes, when compared to tooling like npm or composer etc. it's not as robust as you would think.
The new "dotnet" tools are much easier to work with, and .NET Core is making features that used to be difficult much easier (although that's nothing to do with NuGet).
One of the coolest things (I find) is the ability to create a .NET Core Razor library that lets you build a UI (a whole app - if you really wanted!) and pack it as a NuGet package.
Apps that use this package would "automatically" get the proper routes working out-of-the-box. It's pretty easy to include client-side files (images, js, CSS, etc.) as part of the NuGet project's build too.
All that to say that the tooling around .NET Core is awesome. But NuGet, on its own... ya, it's missing some well-needed features.
I haven't looked into .NET Core Razor yet. Posts about it keep popping up so I should get around to it one of these days.
And I definitely agree about dotnet. I get the feeling we're still in a transitionary period with respect to tooling in the .net ecosystem. dotnet commoditizes some of the "black box" that was Visual Studio, but they haven't really closed the loop on packaging. There's a fair amount of confusion surrounding dotnet vs nuget.exe, using a nuspec file vs newer PackageReference format, etc.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nuget leaves a lot to be desired. The more time I spend with it the more bafflement I excavate.
NuGet is great - but yes, when compared to tooling like npm or composer etc. it's not as robust as you would think.
The new "dotnet" tools are much easier to work with, and .NET Core is making features that used to be difficult much easier (although that's nothing to do with NuGet).
One of the coolest things (I find) is the ability to create a .NET Core Razor library that lets you build a UI (a whole app - if you really wanted!) and pack it as a NuGet package.
Apps that use this package would "automatically" get the proper routes working out-of-the-box. It's pretty easy to include client-side files (images, js, CSS, etc.) as part of the NuGet project's build too.
All that to say that the tooling around .NET Core is awesome. But NuGet, on its own... ya, it's missing some well-needed features.
I haven't looked into .NET Core Razor yet. Posts about it keep popping up so I should get around to it one of these days.
And I definitely agree about dotnet. I get the feeling we're still in a transitionary period with respect to tooling in the .net ecosystem. dotnet commoditizes some of the "black box" that was Visual Studio, but they haven't really closed the loop on packaging. There's a fair amount of confusion surrounding dotnet vs nuget.exe, using a nuspec file vs newer PackageReference format, etc.