NuGetizer 1.2.4
dotnet add package NuGetizer --version 1.2.4
NuGet\Install-Package NuGetizer -Version 1.2.4
<PackageReference Include="NuGetizer" Version="1.2.4"> <PrivateAssets>all</PrivateAssets> <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference>
paket add NuGetizer --version 1.2.4
#r "nuget: NuGetizer, 1.2.4"
// Install NuGetizer as a Cake Addin #addin nuget:?package=NuGetizer&version=1.2.4 // Install NuGetizer as a Cake Tool #tool nuget:?package=NuGetizer&version=1.2.4
NuGetizer is a drop-in replacement for the .NET SDK built-in Pack (a.k.a. "SDK Pack") which instantly supercharges your ability to customize and extend the packing process in a consistent and easy to understand process designed and centered around best practices in MSBuild design and extensibility.
Yes, this means you'll never need to write a .nuspec
by hand ever again, no matter how complicated or advanced your packing scenarios are.
Comprehensive and intuitive heuristics built from experience building nuget packages for over a decade make getting started with NuGetizer seamless and easy, while still accomodating the most advanced scenarios through plain MSBuild extensibility. Out of the box, NuGetizer supports:
- Drop-in replacement for the built-in .NET SDK Pack
- Packing project references (including transitive references)
- Straightforward support for smart libraries packing needs
- Packing multi-targeted projects, including framework-specific resources and dependencies
- Fast iterative development with complementary dotnet-nugetize command line tool
- Comprehensive diagnostic analyzers to provide guidance on packing best practices
- Consistent and predictable naming for package content inference behaviors:
Pack=[true|false]
⇒ Include/exclude from package (on any item, such asPackageReference
,ProjectReference
,None
,Content
, etc.)PackFolder=[folder]
⇒ Name of known folders with special behavior, such asLib
,Build
,Content
,Tools
, etc. (as a project property or item metadata)PackagePath=[path]
⇒ Package-relative path (on any item, such asNone
,Content
, etc.)Pack[Item Type]=[true|false]
⇒ Set default pack behavior for all items of a given type via simple properties (such asPackNone
,PackContent
,PackBuildOutput
,PackDependencies
,PackFrameworkReferences
,PackEmbeddedResource
,PackResource
etc.)
- Packaging projects using
.msbuildproj
and Microsoft.Build.NoTargets SDK - SourceLink support to populate repository information in the package
- Automatic
readme.md
inclusion in the package - Support for content includes in readme
- Package validation enabled by default for release multi-targeting packages.
It's strongly recommended that you install the dotnet-nugetize tool to get the best experience with NuGetizer:
dotnet tool install -g dotnet-nugetize
Given the following project:
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>netstandard2.0</TargetFramework>
<GenerateDocumentationFile>true</GenerateDocumentationFile>
<PackageId>Quickstart</PackageId>
<Authors>NuGetizer</Authors>
<Description>NuGetized quickstart</Description>
<PublishRepositoryUrl>true</PublishRepositoryUrl>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="NuGetizer" />
<PackageReference Include="Microsoft.SourceLink.GitHub" Version="1.1.1"
PrivateAssets="all" />
<PackageReference Include="Newtonsoft.Json" Version="13.0.1" />
</ItemGroup>
<ItemGroup>
<None Include="none.txt" Pack="true" />
<Content Include="content.txt" Pack="true" />
<Compile Update="@(Compile)" Pack="true" />
</ItemGroup>
</Project>
Running nugetize
on the project directory will produce:
A typical packaging .msbuildproj
project for a smart multi-targeted library might look like the following:
<Project Sdk="Microsoft.Build.NoTargets/3.7.0">
<PropertyGroup>
<PackageId>Quickstart</PackageId>
<TargetFramework>netstandard2.0</TargetFramework>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="NuGetizer" />
<PackageReference Include="Microsoft.SourceLink.GitHub" Version="1.1.1"
PrivateAssets="all" />
</ItemGroup>
<ItemGroup>
<ProjectReference Include="..\Analyzer\Quickstart.CodeAnalysis.csproj" />
<ProjectReference Include="..\Build\Quickstart.Tasks.csproj" />
<ProjectReference Include="..\Lib\Quickstart.csproj" />
<ProjectReference Include="..\Tools\Quickstart.csproj" />
</ItemGroup>
</Project>
And produce the following nugetize
tool output:
You can open this sample and run it directly in your browser in a
Learn more about NuGetizer and its capabilities from the project documentation site.
Sponsors
Learn more about Target Frameworks and .NET Standard.
This package has no dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories (16)
Showing the top 5 popular GitHub repositories that depend on NuGetizer:
Repository | Stars |
---|---|
devlooped/moq
The most popular and friendly mocking framework for .NET
|
|
nissl-lab/npoi
a .NET library that can read/write Office formats without Microsoft Office installed. No COM+, no interop.
|
|
LitJSON/litjson
JSON library for the .Net framework
|
|
MonoMod/MonoMod
C# modding swiss army knife, powered by cecil.
|
|
moq/labs
The most popular and friendly mocking framework for .NET
|
Version | Downloads | Last updated |
---|---|---|
1.2.4 | 2,486 | 11/25/2024 |
1.2.3 | 25,146 | 8/9/2024 |
1.2.2 | 16,842 | 5/17/2024 |
1.2.1 | 61,748 | 11/30/2023 |
1.2.0 | 23,561 | 10/11/2023 |
1.1.1 | 9,923 | 8/28/2023 |
1.1.0 | 21,556 | 8/11/2023 |
0.9.2 | 11,211 | 2/11/2023 |
0.9.1 | 66,507 | 11/16/2022 |
0.9.0 | 38,576 | 9/3/2022 |
0.8.0 | 34,627 | 6/9/2022 |
0.7.5 | 45,356 | 10/13/2021 |
0.7.4 | 10,538 | 7/20/2021 |
0.7.3 | 431 | 7/19/2021 |
0.7.2 | 462 | 7/16/2021 |
0.7.1 | 5,313 | 6/17/2021 |
0.7.0 | 2,977 | 5/10/2021 |
0.6.2 | 25,574 | 3/30/2021 |
0.6.0 | 22,598 | 12/10/2020 |
0.5.0 | 1,815 | 11/25/2020 |
0.4.12 | 534 | 11/20/2020 |
0.4.11 | 824 | 11/4/2020 |
0.4.10 | 619 | 10/29/2020 |
0.4.9 | 2,301 | 10/26/2020 |
0.4.8 | 497 | 10/25/2020 |
0.4.7 | 890 | 10/21/2020 |
0.4.6 | 612 | 10/21/2020 |
0.4.5 | 1,097 | 10/8/2020 |
0.4.4 | 586 | 10/8/2020 |
0.4.3 | 538 | 10/4/2020 |