NugetUtil

NugetUtil is a small CLI that discovers packable .csproj files, builds them with dotnet build, regenerates .nuspec files, packs with dotnet pack, and optionally pushes packages with dotnet nuget push.

It also supports Dynamics 365 FO deployable package repacking mode via fopack.

fopack accepts either a deployable package ZIP or a prepared model directory.

What it does

Given a repo root, NugetUtil will:

1. Discover *.csproj recursively
2. Identify package projects (PackageId + Version + not IsPackable=false)
3. Build each package project with dotnet build -c <Configuration>
4. Regenerate <PackageId>.nuspec in each package project folder
5. Pack with dotnet pack (from nuspec)
6. Optionally push with dotnet nuget push

By default, NugetUtil computes filesystem fingerprints and only regenerates/packs packages that changed.

Nuspec mode is the default behavior and is required when a package project directly references non-packable projects.

Requirements

• .NET SDK installed (dotnet on PATH)

Installation (Windows)

Recommended install location:

• C:\nuget\

Suggested layout:

• C:\nuget\nugetutil.exe

Add install folder to PATH:

1. Open System Properties → Advanced → Environment Variables.
2. Under User variables (or System variables), edit Path.
3. Add: C:\nuget\
4. Open a new terminal and verify:

nugetutil --version

Config file path:

• %APPDATA%\NugetUtil\config.json
• Example expanded path: C:\Users\<you>\AppData\Roaming\NugetUtil\config.json

State file path:

• %APPDATA%\NugetUtil\state.json

Notes:

• NugetUtil creates a starter config.json on first run if missing.
• apiKey can be set in config or provided at runtime with -api-key.

Usage

nugetutil ["<rootPath>"] [options]

If <rootPath> is omitted, NugetUtil uses the current directory. Current directory must contain .sln/.csproj (or subfolders containing .sln/.csproj).

Examples:

nugetutil "C:\Dev\sample-repo" -push

nugetutil "C:\Dev\sample-repo" -push -source "PrivateFeed"

nugetutil "C:\Dev\sample-repo" -push -source "PrivateFeed" -api-key "YOUR_API_KEY"

nugetutil "C:\Dev\sample-repo" -autobump -bumplevel patch

nugetutil "C:\Dev\sample-repo" -force

nugetutil fopack "C:\Downloads\Contoso.Module.1.2.3.zip" -output "artifacts\\fo"

nugetutil fopack "C:\Downloads\Contoso.Module.1.2.3.zip" -output "artifacts\\fo" -save-nuspec

nugetutil fopack "C:\Temp\SampleModule" -output "artifacts\\fo" -save-nuspec

Parameters

• -push

  • Push generated .nupkg files after packing.
  • Default: false.
  • If no packages were rebuilt, NugetUtil can push matching existing .nupkg files from the output folder.

• fopack "<zip>"

  • Dynamics 365 FO mode: accepts either a deployable package ZIP or a prepared model directory.
  • For ZIP input, extracts payload from AOSService\Packages\files\*.zip inside the deployable package.
  • For directory input, expects a root *.xref file and package folders such as bin, AdditionalFiles, Reports, and Resources.
  • Package id is inferred from the root *.xref filename (for example Packagename.xref -> Packagename).
  • Package version is inferred from file version of bin\Dynamics.AX.<PackageId>.dll.
  • Output package preserves package root layout and includes root *.xref plus only the source folders that actually existed, from bin, AdditionalFiles, Reports, and Resources.
  • Empty included folders are materialized with _nugetutil.keep only when that folder existed in the original source.

• -save-nuspec

  • With fopack or -deployable-package, saves the generated nuspec to the output folder as <PackageId>.nuspec.
  • If the file exists, it is overwritten.

• -source "<name>"

  • NuGet source name configured on your machine (for dotnet nuget push --source).
  • Must also exist in config sources when -api-key is not provided.
  • Default: defaultSource from config.

• -api-key "<key>"

  • Overrides apiKey from config for push operations.
  • Useful for passing a temporary key from command line.
  • If omitted, key is loaded from config source entry.

• -configuration Release|Debug

  • Build configuration for dotnet build.
  • Default: Release.

• -output "<folder>"

  • Output folder for generated .nupkg files.
  • Relative paths are resolved under <rootPath>.
  • Default: artifacts\nuget (or config override).

• -skip-duplicate

  • Adds -SkipDuplicate when pushing.
  • Default behavior comes from config (behavior.skipDuplicate, default true).

• -verbose-build

  • Prints full dotnet build output for each package.
  • Default: concise build output (- Build: succeeded or build errors).

• -force

  • Processes all discovered packages, ignoring fingerprint change detection.
  • Useful when you want to regenerate/repack everything.

• -autobump

  • Uses filesystem fingerprints to detect which packages need a version bump.
  • Bumps changed packages and dependent packages, then packs only bumped packages.
  • Also updates matching internal PackageReference versions across discovered projects.

• -bumplevel patch|minor|major

  • Version bump level used with -autobump.
  • Default: patch.

• -dryrun

  • Dry-run mode. Commands are printed but not executed.

• -yes

  • Non-interactive push confirmation.

• -include "<glob>"

  • Repeatable include glob for project discovery.
  • If omitted, all discovered projects are considered (subject to excludes).

• -exclude "<glob>"

  • Repeatable exclude glob for project discovery.
  • Combined with config behavior.excludeGlobs.

• -v, --version

  • Prints NugetUtil version and exits.

Config file

Location:

• %APPDATA%\NugetUtil\config.json

Autobump state file:

• %APPDATA%\NugetUtil\state.json

State is used for both default changed-package detection and -autobump.

Behavior summary:

• default: fingerprint-based changed packages only
• -force: all discovered packages
• -autobump: bump changed packages and dependent packages, then pack bumped packages
• with -push and no rebuilds: push existing output packages that match discovered package IDs

On first run, if missing, NugetUtil creates a starter config automatically.

Example:

{
  "defaultSource": "PrivateFeed",
  "sources": {
    "PrivateFeed": {
      "apiKey": "REPLACE_WITH_YOUR_API_KEY"
    }
  },
  "behavior": {
    "skipDuplicate": true,
    "outputFolder": "artifacts\\nuget",
    "excludeGlobs": [
      "**\\bin\\**",
      "**\\obj\\**",
      "**\\**Tests**\\**"
    ]
  }
}

Notes:

• API keys are stored in plain text by design.
• -source / defaultSource uses the NuGet source name configured on your machine.
• NugetUtil masks API keys in command logs/output.

Nuspec generation notes

• Generates <projectFolder>\<PackageId>.nuspec from scratch every run.
• Uses package metadata from the package .csproj.
• Includes dependencies from package and referenced non-packable project package references.
• Resolves $(PropertyName) versions from project properties and Directory.Build.props up the directory tree.
• For internal package dependencies discovered in the same run, NugetUtil uses the latest discovered package version.
• Embeds non-packable referenced project outputs into lib\<packageTfm> via <files> entries.

Auto bump behavior

• Tracks package input fingerprints in %APPDATA%\NugetUtil\state.json.
• Detects changes from filesystem content (no git integration required).
• Marks changed packages for bump.
• Propagates bumps to dependent packages.
• Updates <Version> in .csproj, regenerates nuspec, and packs bumped packages.

Exit codes

• 0 success
• 2 invalid arguments/config
• 3 build failed
• 4 pack failed
• 5 push failed

The CLI prints:

• Job finished successfully. on success
• Job failed with exit code: <code> on failure

Help

• nugetutil -h
• nugetutil --help
• nugetutil -v
• nugetutil --version

Help/version invocations exit with code 0.