Oct 13, 2012 at 9:38 AM
Edited Oct 13, 2012 at 9:39 AM
Many nuget packages do not install with version numbers.
filename-1.2.3.min.css (and similarly for js),
we actually get:
This does not work (nicely or easily) with MVC4 bundling and minification, and makes it hard overall to use. Typically we just have to include manually, and update manually every time there is an update (and thus cannot use nuget for these sort of libraries).
Is there any sense in forcing authors to use version numbers, or if that is draconian then at least allowing the user the ability to modify/configure the installed files through the package manager or Visual Studio or something?
There are so many such packages, it's truly saddening, we would love to use nuget for all of them!