![]() ![]() For example, if you have a Utilities.dll that depends on Parser.dll, and Parser.dll is useful on its own, then create one package for each. In general, it's best to have one assembly per NuGet package, provided that each assembly is independently useful. Most general-purpose packages contain one or more assemblies that other developers can use in their own projects. NET Standard projects using Visual Studio 2017 and higher versions and NuGet 4.0+. This topic applies to non-SDK-style projects, typically projects other than. This process is independent from compiling or otherwise generating the files that go into the package, although you can draw from information in a project file to keep the compiled assemblies and packages in sync. Packaging begins with the compiled code (assemblies), symbols, and/or other files that you want to deliver as a package (see Overview and workflow). This topic describes the detailed process of creating a package that meets those conventions. nupkg extension and whose contents match certain conventions. Technically speaking, a NuGet package is just a ZIP file that's been renamed with the. NET Standard projects that use the SDK-style format, and any other SDK-style projects, see Create a NuGet package using the dotnet CLI.įor projects migrated from nfig to PackageReference, use msbuild -t:pack. For step-by-step instructions using Visual Studio and the nuget.exe CLI, see Create and publish a. ![]() ![]() NET Framework projects, follow the steps described in this article to create a package. Note that Visual Studio does not automatically include a CLI tool.įor non-SDK-style projects, typically. To install NuGet CLI tools, see Install NuGet client tools. No matter what your package does or what code it contains, you use one of the CLI tools, either nuget.exe or dotnet.exe, to package that functionality into a component that can be shared with and used by any number of other developers. ![]()
0 Comments
Leave a Reply. |