TimeWarp.State.DevTools.Hosting
12.0.0-beta.13
Prefix Reserved
dotnet add package TimeWarp.State.DevTools.Hosting --version 12.0.0-beta.13
NuGet\Install-Package TimeWarp.State.DevTools.Hosting -Version 12.0.0-beta.13
<PackageReference Include="TimeWarp.State.DevTools.Hosting" Version="12.0.0-beta.13" />
<PackageVersion Include="TimeWarp.State.DevTools.Hosting" Version="12.0.0-beta.13" />
<PackageReference Include="TimeWarp.State.DevTools.Hosting" />
paket add TimeWarp.State.DevTools.Hosting --version 12.0.0-beta.13
#r "nuget: TimeWarp.State.DevTools.Hosting, 12.0.0-beta.13"
#:package TimeWarp.State.DevTools.Hosting@12.0.0-beta.13
#addin nuget:?package=TimeWarp.State.DevTools.Hosting&version=12.0.0-beta.13&prerelease
#tool nuget:?package=TimeWarp.State.DevTools.Hosting&version=12.0.0-beta.13&prerelease
TimeWarp.State.DevTools.Hosting
Aspire integration that starts the TimeWarp.State DevTools Blazor app and links it from the dashboard.
Dev-only. Production app packages do not reference it. There is no time-travel channel.
AppHost
IResourceBuilder<ProjectResource> devtools = builder.AddTimeWarpStateDevTools();
builder.AddProject<Projects.MyApp>("my-app")
.WithTimeWarpStateDevTools(devtools);
AddTimeWarpStateDevTools finds source/timewarp-state-devtools/timewarp-state-devtools.csproj by walking up from the AppHost directory. Set TIMEWARP_STATE_DEVTOOLS_PROJECT to that csproj when the AppHost is outside this repository.
The DevTools app is not packed into this package. Outside this repository, set TIMEWARP_STATE_DEVTOOLS_PROJECT to the full path of a checkout's source/timewarp-state-devtools/timewarp-state-devtools.csproj; without it AddTimeWarpStateDevTools throws.
The dashboard shows the resource endpoint as TimeWarp.State DevTools.
AddTimeWarpStateDevTools declares an HTTP endpoint named http. Aspire updates an existing endpoint of that name, so a launch profile that already defines http is not added twice. When Aspire does not find a launch profile, that declaration is what gives the resource an endpoint and lets Aspire set ASPNETCORE_URLS.
Aspire reads launch settings only from Properties/launchSettings.json (capital P). The DevTools project keeps its profile there. An external AppHost that points TIMEWARP_STATE_DEVTOOLS_PROJECT at a checkout still needs that Properties/ folder when the app should start as Development with the profile URL. Without the profile the endpoint still exists, the host runs as Production, and static web assets stay attached.
WithTimeWarpStateDevTools sets TIMEWARP_STATE_DEVTOOLS_ENDPOINT on the inspected resource. The app calls AddTimeWarpStateDevToolsExporter() from package TimeWarp.State.DevTools.Export. Aspire's own OTLP endpoint is unchanged, so the dashboard still receives traces.
When Aspire ships a dashboard plugin model, this companion app is the page to port.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net11.0 is compatible. |
-
net11.0
- Aspire.Hosting (>= 13.6.1)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 12.0.0-beta.13 | 36 | 10/13/2026 |
| 12.0.0-beta.12 | 43 | 10/12/2026 |
| 12.0.0-beta.11 | 45 | 10/12/2026 |