Menu
Maybe I'm doing something wrong or expressing pure ignorance here, but I can't really see how Nuget packages are beneficial? I recently decided to install a number of Nuget packages to replace the static DLLs in my application. When I inspect the folders that are created by the packages they seem to include many different versions of the DLL all nested under an array of sub directories.
Don't all these files, many of which appear to be redundant increase the overall size of the application and slow down the publish and deploy routine? Also which items should be placed into source control?
Like I said I may be missing something here but can anybody enlighten me on the virtues of Nuget packages? I'm starting to think that a simple dll in the bin folder worked perfectly fine?
537
For example, package creators use the nuget pack command to create a package from various assemblies and related files, package consumers use nuget install to include packages in a project folder, and everyone uses nuget config to set NuGet configuration variables.
A NuGet package contains reusable code that other developers have made available to you for use in your projects. You can install a NuGet package in a Microsoft Visual Studio project by using the NuGet Package Manager, the Package Manager Console, or the . NET CLI.
NuGet creates a subfolder for each package identifier, then creates subfolders for each installed version of the package. NuGet installs package dependencies as required. This process might update package versions in the process, as described in Dependency Resolution.
The NuGet Package Manager can be used to search and install NuGet packages in the Visual Studio solution or project. Right-click the project or solution in the Solution Explorer tab, and choose Manage NuGet Packages…
187
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
