The .NET Developer's Guide to Package Managers
NuGet burst onto the .NET developer scene in 2010 and took Visual Studio development by storm. We .NET developers were able to easily add key Microsoft dependencies like Entity Framework, ASP.NET Web API, or client-side libraries like jQuery and bootstrap. But now new package management is front and center in Visual Studio 2015. And there’s nothing stopping you from using them in your development toolbelt today. Where does this leave NuGet? And what will you need to get up to speed on now? Chris, Todd, and Jess talk about what NuGet meant to developers until now, and introduce NPM and Bower and their integration into the ASP.NET 5 beta templates. By no means is it the whole list of package managers you can use, but they will be front and center for web developers who live in Visual Studio. Mentioned in the show:
- Introduction to TypeScript: Jess’s free TypeScript training video
- Bower - Home page for this web development package manager
- npm - The nodejs package manager, which has also become a go to for more than just nodejs development.
- Visual Studio - Bower: Modern Tools for Web Development: Adam Tuliper dives into Bower usage in Visual Studio web projects.
- Manage client-side packages with Bower - Direct from the ASP.NET 5 documentation.
- Introducing Gulp, Grunt, Bower, and npm support for Visual Studio: Scott Hanselman makes the case for using more than just NuGet and introduces the Visual Studio integration for these tools (we didn’t discuss task runners in this episode).
- Why use Bower when there is NPM? - Mattias Petter Johansson makes the case that Browserify and NPM are the way to go (we didn’t discuss browserify but we did discuss whether Bower is really necessary).
- Mattias also has a fun YouTube channel discussing how to become a better programmer.
- Migrating to Automatic Package Restore - Stop using “Enable Package Restore” in your Visual Studio solutions. The naming is subtle, but NuGet has a simpler package restore methodology, and you have to edit your project files to get rid of the “old” way.
After you've listened to the episode, we'd love to hear what you think. Please leave a comment below!