LevT
Platinum Member | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору
- [Voiceover] I'll start the exploration of NuGet by looking at two roles: consumers and publishers. Most of this course is about the consumer side of NuGet. We are the consumer. Us. The developer. We want to use some library or .NET tool in our application. So we'll use NuGet to install that tool. Without publishers, there wouldn't be anything to consume, so I'll explore this concept in more detail. The publisher has something useful for the Microsoft developer. Since Visual Studio supports a huge set of application types, the kind of tools can vary a lot. For the .NET developer, it could be a .NET Library contained in a set of DLLs.
For the ASP.NET developer, it might be a single JavaScript file, or it could be a popular JavaScript framework like jQuery. Perhaps it is a set of style sheets, some CSS files and their affiliated image assets. It might even be a part of Microsoft's .NET system. An important part like Entity Framework or ASP.net MVC. The key idea is that there are a wide variety of the tools and libraries. From tiny one file helpers to massive frameworks. And they can all be published via NuGet. So the publisher takes all the items that are a part of their tool.
The DLL's, the JavaScript, whatever is necessary for it it to work correctly on your developer computer. And they create a package file. The package format is a special compressed format with a .nupkg extension. When the publisher creates the package they also indicate any dependencies on other NuGet packages. All of this information, the dependency data, the file data and more is put inside the package file. Each publisher does this. Here are some examples of some popular NuGet packages. JQuery is a popular javascript framework. xUnit is a unit testing framework.
And WebGrease is a suite of tools for optimizing JavaScript, CSS files and images. When the package is ready it is published to a feed. In this example each company publishes the the public Microsoft Gallery. Once the packages are in the gallery the packages are available to any developer with NuGet installed on their developer computer. It's possible for anyone to set up an alternate package feed. For example, a third party could host a set of packages. A more likely scenario is for a company or software group to set up a private feed. This makes it possible to share the proprietary code, libraries and assemblies amongst the team without sharing with the world.
To access the NuGet packages you install NuGet on the local developer computer. The installer modifies Visual Studio. Adding tools like the NuGet package manager extension and package console. Now you can access the package feeds and install, update and configure packages from within the Visual Studio IDE. You can also install NuGet into Windows PowerShell. Which adds a set of the NuGet commands. This provides a way to perform NuGet tasks from the command line. Once NuGet is on the developer computer there are a number of tasks that it can perform. Obviously there has to be a way to list the packages available in the feed.
There is. You can list all the packages. But consider this: There are over 50,000 packages on the Microsoft gallery. So there are ways to filter the list by package name. You can also look up a package by version number. Which means you can see the older versions of a package. This is critical if you need to install a previous version, not the latest. Once you know what package you want then you can perform the other common actions. You can install the package, update to a newer version when it's available or remove all traces of the package if necessary. And remember that NuGet packages are smart about dependencies.
When updating a package NuGet will fetch the new dependency files if needed. Same with removal. When the package is removed the dependencies are removed as well.
|
Всего записей: 17149 | Зарегистр. 14-10-2001 | Отправлено: 13:06 30-12-2017 | Исправлено: LevT, 14:31 30-12-2017 |
|
