erikdarlingdata / build
Build and locate the PerformanceMonitor executables
0
SKILL.md2.1 KB
Build PerformanceMonitor
Build a component of PerformanceMonitor and report the result. All paths are relative to the repository root.
Arguments
$ARGUMENTS specifies which component to build:
| Argument | Project | Output TFM |
|---|---|---|
lite | Lite/PerformanceMonitorLite.csproj | net10.0-windows |
darling or service | Darling/PerformanceMonitor.Darling.Service/PerformanceMonitor.Darling.Service.csproj | net10.0 |
viewer | Darling/PerformanceMonitor.Darling.Viewer/PerformanceMonitor.Darling.Viewer.csproj | net10.0-windows |
dashboard or full | deprecated/Dashboard/Dashboard.csproj | DEPRECATED since v3.3.0 |
installer | deprecated/Installer/PerformanceMonitorInstaller.csproj | DEPRECATED since v3.3.0 |
| (empty) | build whatever is in the current working directory, or ask |
Lite, the Darling service, and the Darling Viewer are the shipping artifacts. The full Dashboard and the CLI Installer moved to deprecated/ in v3.3.0. They still build and their tests still run in CI, but they ship no release artifacts and get bug-fix support only.
Steps
- Map
$ARGUMENTSto the project path above. - Run
dotnet build <path>, Debug configuration by default. Report the result:
- success: show the output path (e.g.
Lite/bin/Debug/net10.0-windows/) and the executable name - failure: show the error messages clearly and suggest fixes
- success: show the output path (e.g.
- Do NOT automatically launch the executable. Just say where it is.
Notes
- Use
dotnet buildwith paths relative to the repository root. Do NOTcdinto directories. - If the build fails because the exe is locked by a running instance, kill it (
taskkill /F /PID <pid>) and rebuild. - If a project path cannot be determined, run
git ls-files "*.csproj"to list the real projects. Stalebin/andobj/folders are left behind at the old top-levelDashboard/andInstaller/paths and are not projects.