Kanject.Cli 2.0.2

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.2
                    
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.2
                    
This package contains a .NET tool you can call from the shell/command line.
#tool dotnet:?package=Kanject.Cli&version=2.0.2
                    
nuke :add-package Kanject.Cli --version 2.0.2
                    

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

- `distribute` checks the version inside the app it just built (`KANCLI790`, `KANCLI792`).
 2.0.1 made `--version` match the project's `<Version>`, but that compares two inputs: a `Version` or `VersionSuffix` from the environment, `publishProperties`, build inputs or a `Directory.Build.targets` still compiled a version the installer and release feed did not carry. After `dotnet publish` and before anything is signed or packaged, every desktop cell now reads the version the app reports at run time, its `AssemblyInformationalVersion` up to any `+`. It comes from the Native AOT executable's reflection metadata (the reader build-input verification uses, now also reading this attribute) or from the managed entry assembly named by the project's `<AssemblyName>`. A different version fails `KANCLI790` before an installer exists; a candidate is checked against its base, since `-rc.N` labels the package, not the binary. When the version cannot be read, a publishing run stops with `KANCLI792` and `--no-publish` only warns, so a local build still produces an artifact to inspect. Library cells and run-stamp versions are not checked. Checked on DynoStudio's .NET 11 Native AOT binary: it reads `1.3.0+c8d51348…`, accepts 1.3.0 and refuses 1.3.1 (proposal 0058 P1b).