5 ms·
I'm using all of them in my project, as this seems to be the direction Microsoft is taking as well: - Nuget for serverside .net (.cs, .dll) and msbuild (.targe
by Maarten88 11y ago
I'm using all of them in my project, as this seems to be the direction Microsoft is taking as well:
- Nuget for serverside .net (.cs, .dll) and msbuild (.target) dependencies
- npm for javascript development dependencies (grunt/gulp)
- bower for clientside dependencies (.less/.scss, .js)
I'm using the new VS online build stuff as well. In git, none of the dependencies are checked in. So the build starts with npm install, bower install and nuget / restore, then it runs gulp and finally msbuild.
I'm pretty happy with it.
- wintersFright 11y agothis is exactly right. It isn't confused as parent says. They are no longer forcing js packages to be bundled into nuget where they tend to grow stale. The nuget angular package was actually maintained by scott hanselman. Why duplicate the effort when angular is published by the angular team on bower? Instead of reinventing the wheel, they are leaning heavily on existing OSS that already does the job very well. eg: No more bundling in MVC, that is what gulp/grunt tasks do for the non MS world, so use that too. No more MSTest which is a poor clone of Nunit, XUnit is the default tool and is used for all ASP.NET internal framework tests.