Kanject.Cli 2.0.1

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet tool install --global Kanject.Cli --version 2.0.1
                    
This package contains a .NET tool you can call from the shell/command line.
dotnet new tool-manifest
                    
if you are setting up this repo
dotnet tool install --local Kanject.Cli --version 2.0.1
                    
This package contains a .NET tool you can call from the shell/command line.
#tool dotnet:?package=Kanject.Cli&version=2.0.1
                    
nuke :add-package Kanject.Cli --version 2.0.1
                    

Kanject.Cli

A single .NET global tool that drives C# AWS services from dotnet new to kanject aws deploy --env prod — wrapping the existing dotnet/AWS toolchain so your inner loop stays vanilla and the Lambda, ECS Fargate, static-site, and coupled full-stack deploy plumbing disappears behind one committed manifest.

Install

dotnet tool install --global Kanject.Cli

Requires the .NET 10 SDK or later (the .NET 11 SDK installs its .NET 11 build). The aws, msbuild, and github providers ship in the box — no extra installs.

Choose a workflow

  • Deploy applications: Lambda, ECS Fargate, or a coupled SPA/backend. Choose independent service roots, a shared multi-Lambda stack, or a coordinated frontend/backend pair.
  • Publish libraries: kanject packages init, then kanject packages plan and kanject packages verify from the package repository root.
  • Distribute desktop apps: initialize the product manifest, register with kanject add distributable, and configure delivery destinations.

Start at Getting started for workflow selection. Service commands run from the directory containing that service's manifest, which can differ from the repository or solution root. The current static-site shape requires a coupled backend.

Discover commands with kanject --help and kanject aws --help.

What it does

  • Bootstrap — kanject new scaffolds a project from a bundled template and initializes it; kanject init adds the manifest, stage files and lock file to an existing project.
  • Deploy — kanject aws deploy --env <stage> resolves cross-repo dependencies and env, builds the provider artifacts, and ships the manifest's target (Lambda, ECS Fargate, static site, or a coupled backend + site), recording every release in an S3 deployment ledger.
  • Rollback — kanject aws rollback --env prod shows the last 10 deployments with dates, statuses, targets, and commit summaries; pick one and Kanject does the target-native promotion with the prior artifact still immutable in S3/ECR.
  • And more — cross-repo dependency sync, a local test runner, env/param/secret management, static-site previews and ephemeral backend previews (kanject aws deploy --preview <NAME>), DynamoDB change feeds, a managed streaming Function URL and CloudFront edge, VPC & custom-domain wiring, multi-function services, AWS-native pipeline scaffolding, NuGet package publishing, desktop distribution, and sign-in for paid Kanject packages (kanject login, kanject add package).

It invokes — never replaces — dotnet new, dotnet build, and dotnet lambda, and drives AWS services through their SDK APIs (including CloudFormation change sets). The dotnet-native experience stays; kanject only owns the AWS plumbing that doesn't have a great answer in the box.

Learn more

License

Commercial — governed by the Kanject Code Libraries License Agreement (KCLLA); see the bundled LICENSE.md. © Kanject Business Solutions.

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed.  net11.0 is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

Version Downloads Last Updated
2.5.0 103 11/16/2026
2.4.0 93 11/16/2026
2.3.0 113 11/15/2026
2.2.0 128 11/14/2026
2.1.0 96 11/13/2026
2.0.2 102 11/13/2026
2.0.1 94 11/13/2026
2.0.0 100 11/12/2026
1.5.1 123 11/11/2026
1.5.0 121 11/10/2026
1.4.0 106 11/4/2026
1.3.0 119 11/2/2026
1.2.0 157 11/1/2026
1.1.0 115 11/1/2026
1.0.79 111 10/30/2026
1.0.78 101 10/30/2026
1.0.77 108 10/29/2026
1.0.76 102 10/29/2026
1.0.75 100 10/29/2026
1.0.74 101 10/28/2026
Loading failed

- `kanject access` and `kanject add package` treat the `Kanject.Core.Events` packages as public.
 The embedded Kanject feed manifest is re-vendored from the licence service (`59bb931`): `Kanject.Core.Events`, `Kanject.Core.Events.Abstractions`, `Kanject.Core.Events.Annotations` and `Kanject.Core.Events.TestKit` have been on nuget.org since 2026-10-23, after Core made them public, but the manifest still classed them as paid Core packages. `kanject access` therefore mapped them to the Kanject feed, so they restored only for an organisation with a paid Core tier, and `kanject add package` asked for a sign-in. They now map to nuget.org with the other public Kanject packages (42 in all), and `kanject add package` adds them with plain `dotnet add package`. The same manifest lets a Wallet licence pull the change-feed outbox packages `Kanject.Wallet` 4.0.0 depends on; nothing in the CLI reads that differently.

- `distribute --version` must name the version the project compiles (`KANCLI783`).
 `dotnet publish` never received the run's version: the binary carries the project's own `<Version>`, while `--version` reached only the installer names, the release kit's `{version}` token, the release feed and the ledger. A `--version` that named the next release therefore built a split artifact. DynoStudio's `--version 1.3.1` run with `1.3.0` committed produced `dynostudio-Business-1.3.1-osx-arm64.dmg`, whose `Info.plist` said 1.3.1 around a binary whose `AssemblyInformationalVersion`, which the app's About screen and updater read, said 1.3.0. `aws distribute` and `github distribute` now refuse a `--version` that differs from the `<Version>` (or `<VersionPrefix>`, which also accepts `<prefix>-<suffix>`) in the csproj or nearest `Directory.Build.props`, in every mode and for the `--candidate` base. The refusal comes before anything is built or read from a destination, and names the file and both versions. Passing the committed version still works; a project with no version, or whose `<Version>` is an MSBuild expression, is not checked. Commit the version change first (proposal 0058 P1).