Docs menu
Getting started with .NET
Deploy a minimal ASP.NET Core app to Primcloud end-to-end using a sample repo, in about five minutes.
On this page
Deploy a small ASP.NET Core app to Primcloud: fork a sample repo, import it, watch the build, and open the app at its *.primcloud.app URL. It takes about five minutes.
Before you start#
You'll need:
- A Primcloud account. Standard accounts have no monthly fee; compute is metered by the minute once you deploy, from around $5/mo for the smallest app.
- A git provider connected to your Primcloud account; see Source Control.
- Optional: the .NET SDK 8.0 or newer installed locally, if you want to run the sample or make changes before deploying.
The sample app#
For this guide, use Heroku's heroku/dotnet-getting-started repo. It's a minimal ASP.NET Core web app that builds on Primcloud with no changes. Fork it into an account you've connected to Primcloud.
1. Create the application#
Hit Import Git Repository on the applications list, then:
- Select your fork of
dotnet-getting-started. - Configure the branch (
main) and a region. - Verify the commit and hit Import.
2. Deploy#
The first deployment starts as soon as the app is created, and its build log streams live:
- Detection. Primcloud sees the
.csprojat the repo root and picks the .NET toolchain. - Build. The .NET SDK for the project's
TargetFrameworkrunsdotnet publish. - Start. Primcloud starts the
webprocess. NoProcfileis required: Primcloud infers thewebprocess type from theMicrosoft.NET.Sdk.WebSDK.
When the deployment's Rollout phase shows Complete, the app is live.
3. Reach the app#
Click the *.primcloud.app URL in the dashboard header to open the app.
If it doesn't come up:
- Deployments: the build log has the raw output from the .NET SDK.
- Logs: runtime output from your app streams there, including any startup errors.
- Confirm the app binds to
$PORT. Primcloud setsPORT(a fixed5000) on thewebformation, and because the sample is anMicrosoft.NET.Sdk.Webproject, the build wires it to that port automatically.
Where to go next#
- Deploying a different .NET app: .NET on Primcloud for detection, build target selection, and process type inference.
- Pinning to a specific SDK version: Runtime versions.
- Using a private NuGet feed: Package managers.
- Customizing the
dotnet publishcommand or adding a build hook: Customizing the build. - Something breaking: Troubleshooting .NET.