# Configure build and start for ASP.NET Core

Build and start for a ASP.NET Core app on Ample. Verified on ASP.NET Core: the app built and started with the documented commands and answered on its public HTTPS URL. Build and start: `dotnet publish -c Release -o out` in the builder, then `dotnet <entry>.dll` on the dotnet-10 template with `ASPNETCORE_URLS` bound to `PORT`.

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

## You need

- An ASP.NET Core project (`dotnet publish -c Release -o out` in the builder, then `dotnet <entry>.dll` on the dotnet-10 template with `ASPNETCORE_URLS` bound to `PORT`)
- An Ample account token with `servers:write`

## Exact tested configuration

- `dotnet publish -c Release -o out`
- `dotnet`
- sizes-1vcpu-1gb
- `ASPNETCORE_URLS=http://0.0.0.0:$PORT dotnet out/$(basename $(ls out/*.runtimeconfig.json | head -n 1) .runtimeconfig.json).dll`
- dotnet-10

## Steps

1. **Build and start.** `dotnet publish -c Release -o out` in the builder, then `dotnet <entry>.dll` on the dotnet-10 template with `ASPNETCORE_URLS` bound to `PORT`; the server must bind 0.0.0.0 on PORT.
2. **Deploy.** Run the synchronous deploy once and read the result.
    
    ```
    $ ample deploy . --name <app-name> --public
    ```
3. **Verify.** Fetch the live URL on the example; on failure read the build and runtime logs.
    
    ```
    $ ample logs <deployment_id> --kind build
    ```

## How it was checked

✓ app responds on its public URL · `http get/` → “ample canary asp net core patterns”

## Evidence

1. November 6, 2026 · canary run  
ASP.NET Core pattern fixture deployed on Ample (`dotnet publish -c Release -o out` in the builder, then `dotnet <entry>.dll` on the dotnet-10 template with `ASPNETCORE_URLS` bound to `PORT`); for this guide: the app built and started with the documented commands and answered on its public HTTPS URL.

## Tested examples

- **ASP.NET Core pattern fixture.** Verified build and start on ASP.NET Core.

## What it doesn’t cover

- Verified on the dotnet-10 template at s-1vcpu-1gb.
