devlooped/nugetizer

Issues

• Remove SourceLink packages which are now built-in the .NET SDK

  #484 opened 24 days ago by kzu
  0

• Make sure nugetize always sets EnablePackageValidation=false to avoid SDK attempting to validate a non-existent package

  #482 opened 24 days ago by kzu
  0

• Document usage of properties that affect packing, such as UseShortSourceRevisionId

  #481 opened 24 days ago by kzu
  0

• Packing reference assemblies generated at compile time is valid.

  #480 opened 24 days ago by kzu
  0

• Cannot imitate DevelopementDependency with PackageReference

  #448 opened 4 months ago by FuzesiAkos
  2

• Bring back nuget authoring analyzers

  #462 opened 6 months ago by kzu
  0

• Package file is always updated on a build even when there are no changes

  #434 opened 9 months ago by davidhunter22
  2

• Rename BuildOutputFrameworkSpecific > PackFrameworkSpecific for consistency

  #438 opened 8 months ago by kzu
  0

• Inference of package icon causes duplicate package readme files

  #436 opened 8 months ago by kzu
  0

• When publishing as a tool, readme inclusions are resolved from publish dir

  #435 opened 9 months ago by kzu
  0

• Empty TargetFramework breaks the build

  #416 opened 9 months ago by hankovich
  2

• Unhandled exception in nugetize output

  #417 opened 9 months ago by hankovich
  1

• error NETSDK1085: The 'NoBuild' property was set to true but the 'Build' target was invoked.

  #407 opened 10 months ago by voroninp
  4

• Add support for PackAsAnalyzer

  #414 opened 10 months ago by kzu
  0

• 'NuGetizer.SponsorLinker' exception happening randomly

  #370 opened a year ago by Aleksanderis
  4

• SponsorLink warnings in VS builds that can't be suppressed and "build paused for Xms"?

  #371 opened a year ago by Sergio0694
  1

• Cleanup happens on every build

  #369 opened a year ago by Aleksanderis
  2

• Error message "valid version string" after adding nugetizer package

  #271 opened a year ago by davidhunter22
  4

• PackNone should default to 'true' in authoring/packaging projects

  #346 opened a year ago by kzu
  0

• SponsorLink incorrectly configured

  #340 opened a year ago by fde-lmag
  3

• NuGetizer v0.9.1 packing reference assembly instead of real assembly

  #263 opened a year ago by RichardD2
  8

• F# projects are not supported

  #191 opened a year ago by tastyeggs
  3

• Nugetizer seems to change AssemblyName of projects to the project's file name in dependency graph

  #270 opened a year ago by karpis
  2

• Inconsistent behaviour when using PrivateAssets="All" between different frameworks when packing as tool

  #261 opened 2 years ago by quasarea
  2

• NuGetizer is incompatible with SDK Pack DevelopmentDependency property

  #253 opened 2 years ago by kzu
  0

• Allow nugetize (non-build) tool for dotnet-tool projects

  #247 opened 2 years ago by kzu
  0

• When include in readme fails, log a warning

  #232 opened 2 years ago by kzu
  0

• The target "GetPackageContents" does not exist in the project.

  #226 opened 2 years ago by CoenraadS
  1

• Allow including content in the package readme from a URL

  #216 opened 2 years ago by kzu
  0

• Support markdown includes in package readme files

  #210 opened 2 years ago by kzu
  0

• If readme isn't already a @(None) item, it's not automatically added to package

  #213 opened 2 years ago by kzu
  0

• Support transitive package dependency of referenced (non-packing) project

  #199 opened 2 years ago by khamza85
  1

• Packaging when using Nerdbank.Gitversioning fails

  #198 opened 2 years ago by hymccord
  2

• Yellow triangle on Nugetizer nuget package reference under project dependencies -> packages

  #196 opened 2 years ago by menaheme
  1

• running nugetize fails - unable to find framework

  #189 opened 2 years ago by menaheme
  1

• Improve compatibility with SDK Pack for tools

  #134 opened 2 years ago by kzu
  0

• Improve readme.md content inclusion inference

  #185 opened 2 years ago by kzu
  0

• Make it easier to create build packages by improving inference heuristics

  #184 opened 2 years ago by kzu
  0

• Allow packaging projects to be framework-specific

  #182 opened 2 years ago by kzu
  0

• SDK Pack always packs build as framework-specific

  #133 opened 2 years ago by kzu
  1

• Add support for PackFolder=buildTransitive

  #179 opened 2 years ago by kzu
  0

• Packaging project generates package improperly

  #139 opened 2 years ago by dansiegel
  1

• Packing with Microsoft.Build.NoTargets doesn't put dependency under proper target framework group when reference other Microsoft.Build.NoTargets project

  #155 opened 2 years ago by denjmpr
  4

• Do BuildAction and CopyToOutput work?

  #143 opened 2 years ago by davidhunter22
  0

• Files with absolute paths that do not specify a PackFolder are not included in the final nupkg

  #162 opened 2 years ago by breidikl
  1

• Re-enable build/tests on macOS/linux

  #174 opened 2 years ago by kzu
  0

• Cannot use PackageRequireLicenseAcceptance = true with Microsoft.Build.NoTargets sdk

  #149 opened 3 years ago by denjmpr
  4

• PackAsTool from SDK Pack should cause PackFolder=tool

  #131 opened 3 years ago by kzu
  0

• SDK Pack always packs tools as framework-specific

  #132 opened 3 years ago by kzu
  0

• Normalize all paths for consistency, use SDK Pack format

  #135 opened 3 years ago by kzu
  0