Primcloud
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

This guide walks through deploying a small ASP.NET Core app to Primcloud. You'll fork a sample repo, import it, watch the build, and reach the deployed app at a *.primcloud.app URL. Takes about five minutes.

Before you start#

You'll need:

  • A Primcloud account. Standard accounts are free to create; compute is metered by the minute once you deploy, from around $5/mo for the smallest app.
  • A git provider connected to your account with access to at least one repo.
  • 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 cleanly on the Primcloud Runtime with no changes. Fork it into an account your connected provider can see, so Primcloud can pull from it.

1. Create the application#

From the Primcloud dashboard, hit Import Git Repository on the applications list. The import wizard walks you through three quick steps:

  1. Pick a repository: select your fork of dotnet-getting-started.
  2. Configure the deployment:
    • Branch: main (the fork's default).
    • Region: US East (NYC).
  3. Review and create: Primcloud auto-provisions the app's primary *.primcloud.app subdomain on the production environment.

2. Deploy#

The first deployment kicks off automatically when the app is created. Watch it stream in the Deployments tab:

  • Detection. Primcloud sees the .csproj at the repo root and picks the .NET toolchain.
  • Build. The .NET SDK runs dotnet publish and packages the result into a runnable image. The SDK version is resolved from the project's TargetFramework.
  • Release. Primcloud starts the web process on the pod formation. No Procfile is required: Primcloud infers the web process type from the Microsoft.NET.Sdk.Web SDK.

When the deployment status flips to Release Succeeded, the app is live.

3. Reach the app#

The application dashboard shows the assigned *.primcloud.app URL in the header. Click it, and the sample app's homepage loads.

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 sets PORT (a fixed 5000) on the web formation, and because the sample is an Microsoft.NET.Sdk.Web project, the build wires it to that port automatically.

Where to go next#