Shipped.NET hosting
on Shipped.
Bring your .NET application and the runtime it needs. Run a web service, a worker, or a scheduled task from the same product platform.
Publish for the environment you will run
Package your .NET publish output with the runtime and operating-system dependencies it needs. A framework-dependent or self-contained deployment still needs the correct target environment. Shipped runs suitable containerized services, so keep platform-specific requirements explicit when preparing an existing application to move from your development machine.
Give web and worker processes separate jobs
Use a web service for HTTP requests and a worker for continuous background processing. They can share application libraries and connect to the same data services while using different start commands and capacity. Scheduled jobs provide a place for commands that need to run at defined intervals.
Configure the same code for each environment
Supply connection strings and private integration settings through secrets rather than committing them into configuration files. Connect PostgreSQL using an appropriate .NET provider and keep staging resources separate from production. Logs let you inspect startup and application behavior after a new release is deployed.
A little more detail
Questions about .NET?
Does this mean any Windows desktop .NET app can be hosted?
No. Website hosting runs service workloads, not a desktop interface. Your application and its dependencies must support the deployment environment; Windows-specific or legacy framework dependencies may need adaptation.
Do I have to publish a self-contained application?
No. Both framework-dependent and self-contained approaches can be packaged appropriately. Include or provide the matching runtime and test the output for your selected environment.
ASP.NET Core
Run ASP.NET Core on Shipped with your published app, database connections, environment settings, domains, HTTPS, and deployment logs.
Explore ASP.NET CoreBackground workers
Run background workers on Shipped for queues, imports, notifications, and long-running application tasks, with separate resources and deployment history.
Explore Background workersScheduled jobs
Schedule application jobs on Shipped for recurring reports, synchronization, and maintenance, with explicit runtime settings and execution logs.
Explore Scheduled jobs
Docker
Deploy containerized applications on Shipped with your runtime and system dependencies, connected services, domains, secrets, and rollbacks.
Explore DockerFrom your workspace to the web