Project Automation and Configuration Engine
A Python CLI tool for bulk management of C# .NET project ecosystems — from single class libraries to complex multi-project hierarchies with MAUI applications.
Overview
PACE eliminates the repetitive, error-prone manual work of managing .NET project ecosystems at scale. Rather than shelling into each project directory to run dotnet commands, manage git state, or manually update build configurations, PACE provides a unified interface to interact with all of them at once.
It understands your project topology — respecting dependency order, project hierarchy, and configuration context — so you can express intent once and apply it across your entire repository graph.
Target project types
| Type | Description |
|---|---|
| Class libraries | Standalone or NuGet-published reusable packages |
| MAUI applications | Cross-platform apps with platform image and build assets |
| Dependency trees | Multi-library hierarchies with topological dependency ordering |
| Sample applications | Reference and demo apps accompanying library suites |
Design principles
Composability — individual commands can be piped, scripted, and combined into workflows.
Topology-awareness — multi-project operations always respect inter-project dependencies.
Transparency — every operation emits clear, structured output suitable for both human review and CI log parsing.
Reproducibility — configuration is declared in a manifest file that describes the project graph.
Installation
pip install pace-dotnet
Configuration
PACE is driven by a pace.toml manifest at your workspace root:
repodir = "/path/to/repositories"
nuget_cache_path = "/path/to/nuget/cache"
[[projects]]
name = "common-lib"
csproj_path = "common-lib/src/CommonLib/CommonLib.csproj"
repo_url = "https://github.com/org/common-lib"
depends_on = []
[[projects]]
name = "feature-module"
csproj_path = "feature-module/src/FeatureModule/FeatureModule.csproj"
repo_url = "https://github.com/org/feature-module"
depends_on = ["common-lib"]
[[build-props]]
name = "DevSolution"
datatype = "boolean"
default = true
Usage Examples
# Build all projects in dependency order
pace dotnet build
# Build projects starting from a specific project
pace --from ProjectName dotnet build
# Check git status across every repo
pace git status
# Run all unit tests and show a summary
pace test
# Format and verify code style
pace format --check
License
Metadata
Release files for pace-dotnet 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pace_dotnet-0.2.2.tar.gz | 24.6 kB | Without provenance | Details for pace_dotnet-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pace_dotnet-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for pace_dotnet-0.2.2-py3-none-any.whl |
Total release size: 52.0 kB
Release files / pace_dotnet-0.2.2.tar.gz
| Download URL | pace_dotnet-0.2.2.tar.gz |
|---|---|
| Size | 24.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
821994c343baab0d803503b328caab04f3a436c88140faf7b74a2991db27fe08
|
|
BLAKE2b-256 checksum How to use checksums |
26a152dcc0af5ed33c0e61a45213471fd0cda3abcff463768da4079af0424240
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Release files / pace_dotnet-0.2.2-py3-none-any.whl
| Download URL | pace_dotnet-0.2.2-py3-none-any.whl |
|---|---|
| Size | 27.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1444bc290f4d53116513f36ce7cfc9d5a80d161d579aa08c5a75a4bb5a3df700
|
|
BLAKE2b-256 checksum How to use checksums |
94ad621f78452b5f974a6ef366538c539eb3a281ed568d06eb60fd59e871a696
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Security for pace-dotnet 0.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.