LazyCrud.Cli 1.1.0

Lazy CRUD command line

Lazy CRUD for Visual Studio, unattended.

This is the same engine the Visual Studio extension runs, with a different face. A build server and a developer generate the same files, protect the same edits, and read the same diagnostic codes — because there is one implementation, not two that agree by inspection.

dotnet tool install --global LazyCrud.Cli
lazycrud status

What it does

Your model is the source. The Lazy CRUD platform packages publish a descriptor — which layers exist, which templates write into them, who owns each output — and this tool reads it and does what it says. It resolves the templates from the packages, runs them through the Visual Studio templating host, records what it wrote, and refuses to overwrite anything you have changed.

lazycrud init-sln --path . --name Shop
lazycrud create-aggregate --agg Orders --entity Order
lazycrud status

lazycrud --help lists every verb. The ones you will use most:

Requirements

• Windows, with an installed Visual Studio carrying the Text Template Transformation component. Generation runs the real templating host; nothing here reimplements it. Without it, every generating verb stops with the prerequisite exit code before writing anything.
• .NET 8 or later for the tool itself.

What it will not do

• It never falls back to a template folder on your disk. Local template mode exists for developing templates, is selected explicitly, is reported when used, and is refused under --strict.
• It never overwrites a generated file you have edited. It stops, names the file, and offers --force (overwrite, reporting each one) or --skip-modified (keep yours, generate the rest).
• It never writes anything after a refusal. A run that stops, stops before the first write.

Exit codes

From the platform's shared table, so a script can branch on them:

--json writes exactly one machine-readable document on stdout, with every log line on stderr.

Documentation

• Quick start
• Generated-code policy — ownership, markers, hashing
• Troubleshooting — indexed by diagnostic code
• Release notes

The command line and the extension share a version number, because they share an engine.