Knowledgebase

Deploying .NET Applications Print

  • microsofttechnology, microsoft, errors, migration, woocommerce, downtime, guide, howto
  • 0

Getting applications running.

WHAT HOSTING OPTIONS EXIST

A managed application platform Containers A virtual machine running a web server Serverless functions

WHAT TO PREFER

The most managed option meeting your requirements.

WHAT TO CONFIGURE PER ENVIRONMENT

Connection strings and endpoints Logging levels Feature settings

WHERE TO PUT THEM

Environment variables or a secret store, never in committed files.

WHAT TO PUBLISH

A build produced by the pipeline, not from a developer machine.

WHY

Reproducibility, and no dependence on one person's setup.

WHAT TO ENABLE IN PRODUCTION

Detailed error pages disabled Logging to a collected destination Health check endpoints

WHAT HEALTH CHECKS PROVIDE

A way for the platform to know whether an instance is usable.

WHAT TO VERIFY AFTER DEPLOYING

The application starts Migrations applied Key paths work Logs are clean

WHAT TO PLAN

Zero-downtime deployment, where the platform supports it.

WHAT TO KEEP

The previous version, for reversal.

WHAT TO MONITOR

Error rates and response times, immediately after release.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot