The document provides an overview of the NuGet Package Manager, essential for .NET developers to manage, share, and collaborate on code packages. It covers the manager's introduction, features, ecosystem, tools, benefits, and concludes with the significance of using NuGet for efficient code integration and dependency management. Additionally, it emphasizes etiquette in sessions related to NuGet, including punctuality and constructive feedback.

1. NuGet Package
Manager for Dot Net
Libraries
Aishwarya Dubey
Mudassir Qureshi

2. Lack of etiquette and manners is a huge turn off.
KnolX Etiquettes
 Punctuality
Join the session 5 minutes prior to the session start time. We start on
time and conclude on time!
 Feedback
Make sure to submit a constructive feedback for all sessions as it is very
helpful for the presenter.
 Silent Mode
Keep your mobile devices in silent mode, feel free to move out of session
in case you need to attend an urgent call.
 Avoid Disturbance
Avoid unwanted chit chat during the session.

3. 1. Introduction to NuGet Package Manager
2. NuGet Package Manager Example
3. Key Features
4. NuGet Ecosystem
5. NuGet Package Tools
6. Benefits of NuGet Package Manager
7. NuGet Package Workflow
8. Demo
9. Conclusion

4. NuGet
Package Manager

5. Introduction to NuGet Package Manager
 To understand the NuGet package manager, first, let’s learn about the NuGet package. It will help
to capture the package manager’s details effortlessly.
 Let’s put it in the simplest form.
 The NuGet package is a zip file that contains the codebase required to integrate an additional
feature or functionality in the .NET application. Mainly, NuGet packages come with a “.nupkg”
extension. When you open any of the .nupkg files, it contains the following three components:
 DLLs (Compiled Code)
 The code’s descriptive manifest
 Files associated with DLLs

6. NuGet Package Manager Example
 The example is divided into steps, defining how the NuGet package manager works and
leveraging .NET developers to collaborate efficiently. Also, the example uses two hypothetical
developer characters, Max and Alex.
 A developer named Max creates a NuGet package holding code for enabling SignalR in the .NET
application
 Max uploads the created package on the NuGet package manager.
 another developer (Alex) opens the NuGet package manager in the Visual Studio IDE and
searches for the package uploaded by Max.
 Alex finds the package, downloads, and installs it. Further, Alex can embed the code in the
package in its .NET application and enable SignalR functionality.
 As a result, the process of sharing code gets streamlined with the NuGet package manager.

7. Key Features
 NuGet adds private hosting support to the central nuget.org repository.
 NuGet provides the tools that developers need to create, publish, and install packages.
 NuGet keeps track of the packages used in a project and allows you to restore and update those
packages from that list.
 NuGet keeps track of all the specifications pertaining to how packages are structured, such as
localization and how they are referenced.
 NuGet provides numerous APIs for programmatically interacting with all of its services, as well as
support for developers who publish Visual Studio extensions.
 NuGet includes a package cache and a global folder for packages to make installation and
reinstallation easier. If a package is already present on the local machine, the cache will not
download it from the central repository, and will instead serve the package from the cache.

8. NuGet Ecosystem
 NuGet Package Manager: Central tool for managing .NET packages.
 NuGet Gallery: Centralized repository for publishing and discovering packages.
 Package Authors: Developers who create and publish NuGet packages.
 Consuming Projects: Applications or libraries that use NuGet packages.
 Package Consumers: Developers who utilize NuGet packages in their projects.
 NuGet CLI: Command-line interface for package management tasks.
 Visual Studio Integration: Seamless integration for managing packages within Visual Studio.
 Community Collaboration: Platform for sharing, contributing, and supporting packages within
the .NET community.

9. NuGet Package Tools
The NuGet package manager offers numerous tools to support package hosting, download, and
installation. Both package users and the creators/developers can use the tools. The list of tools
includes:
 dotnet CLI : The .NET CLI is a command line-based interface used for installing NuGet packages
for .NET Standard and .NET Core. Most of its capabilities are by default present in .NET Core,
but you can also use it for SDK-style .NET framework projects.
 nuget.exe CLI : The nuget.exe CLI is for both NuGet creators and consumers. It provides the
commands used for hosting and installing the packages for .NET framework libraries. Also, you
can use it with non-SDK-style projects.
 Package Manager Console : To utilize the package manager console, you need Visual Studio
IDE on the Windows operating system and knowledge about PowerShell commands. And this
tool is only for NuGet package consumers.

10.  Package Manager UI : It’s a GUI-based (Graphical User Interface) interface used for consuming
NuGet packages for a .NET application project. It comes installed by default in the latest Visual
Studio versions. You will see its usage in the upcoming section, providing a practical hands-on on
NuGet package manager usage.
 Manage NuGet UI : manage NuGet UI is for macOS users. It runs on Visual Studio and is
available for Apple users. A GUI-based interface, similar to the Package Manager UI tool, is
provided for consuming NuGet packages.
 MSBuild : A NuGet package creator and a consumer can use the MSBuild tool. It’s available for
the Windows operating system with additional functionality to restore packages through the
toolchain.

11. Benefits of NuGet Package Manager
 Efficient Dependency Management: Simplifies dependency resolution and installation, saving
time.
 Time Savings: Offers pre-built components for quick integration, reducing development time.
 Version Control Integration: Seamlessly integrates with Git, facilitating package management
alongside source code.
 Visual Studio Integration: Provides a user-friendly interface within Visual Studio for easy
package management.
 Cross-Platform Compatibility: Supports .NET Framework, .NET Core, and .NET 5/6 for
versatile development.
 Community Collaboration: Facilitates sharing and contribution within the .NET community
through the NuGet Gallery.
 Flexible Installation Options: Offers multiple installation methods to accommodate different
workflows.
 Package Restoration: Automatically downloads missing packages, keeping project files
lightweight.

12. NuGet Packages Workflow

14. Conclusion
 NuGet package manager is a centralized repository for sharing code and associated files for
.NET development projects. It helps the development teams to collaborate and utilize the code
base per requirements efficiently. In addition, it comes in two versions – private and public. In the
private version, only authorized people are allowed to use a package. But, in the public version,
anyone can use the package.
 Furthermore, numerous NuGet package manager tools are available, helping the consumers and
creators to perform their tasks. Among all the tools, the package manager console and UI are
demonstrated above. You can undergo the procedure to understand how the package manager
for .NET works thoroughly.