Table of Contents

Local development

Prerequisites

Tool Version Notes
.NET SDK 8.0.424 / 10.0.400 Each repository's global.json selects its SDK: the website pins 8.0.424; the docs repo pins 10.0.400.
Node.js 20.x Website build tooling and Playwright tests.
SQL Server A reachable instance The API and Teams bot need a connection string.
Azure access Development/integration credentials Needed for Blob Storage, Service Bus or Speech paths you exercise.
PowerShell 7+ recommended Build and deploy scripts.

Website

dotnet run --project SPE.Public

The local endpoints are https://localhost:7089 and http://localhost:5089 unless ASPNETCORE_URLS or TEST_BASE_URL is set (the functional-test harness sets those). The development configuration points at a local API by default.

Do not build the website with the .NET 10 SDK. The global.json pin exists because the Razor source generator in .NET 10 can drop asp-append-version links on several pages, which ships unresolved ~/css/... hrefs.

API

dotnet run --project SPE.Api

Configure the SQL Server connection string through user secrets or environment variables, not in a committed file. The development API listens on the endpoint the website's Performance:Client:EnvironmentUrls:Development points at (https://localhost:44332/api/v1/ in the generated configuration).

Profiler (.NET)

dotnet build Reignite.Profiler.sln
dotnet test Reignite.Profiler.sln

To exercise the agent locally, point a test application at a development profiler configuration and lower a threshold so a small workload triggers a capture.

Bots

The diagnostic bot and Teams bot need their own app registrations and settings:

  • TeamsBot:BotAppId and TeamsBot:BotAppPassword for the diagnostic bot.
  • ConnectionStrings__SqlServerConnection for the Teams bot.
  • DiagnosticsControlPlane:BaseUrl and ApiToken for the diagnostic bot's control-plane calls. Leave BaseUrl blank to use the in-memory stub.

Docs

dotnet tool restore
./scripts/build.ps1       # generator + DocFX + host publish
./scripts/serve.ps1       # generator + docfx --serve

The docs repo targets .NET 10 LTS. global.json selects SDK 10.0.400; DocFX ships a .NET 10 build, so the docs build needs only the .NET 10 SDK.

The docs site is a DocFX modern-template site. The architecture diagrams are generated from architecture/model.yaml by tools/Reignite.Docs.Generator.

Secrets

  • Use user secrets for local .NET projects: dotnet user-secrets set "Key" "value".
  • Use App Service application settings for deployed services.
  • Never commit a connection string, API key, bot secret or storage key.
  • Treat downloaded traces and dumps as production data.

Troubleshooting

Symptom Check
dotnet resolves to the wrong SDK Run dotnet --version in the repository; the global.json should select 8.0.424 for the website or 10.0.400 for the docs repo.
Website pages lose stylesheets You built with the .NET 10 SDK; use the pinned SDK.
API cannot connect The connection string is missing or points at an unreachable SQL Server.
Bot starts but health is unconfigured The Teams bot has no connection string; that is deliberate and keeps it diagnosable.
Docs generator fails The model is invalid; the error names the duplicate id, unknown endpoint or broken flow.