Tutorials ASP.NET Core Tutorial
Launch Settings and Configuration — Complete Guide
Launch Settings and Configuration — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of ASP.NET Core Tutorial on Toolliyo Academy.
On this page
ASP.NET Core Tutorial (ShopNest) · Lesson 10 of 100
Launch Settings and Configuration
Beginner → Intermediate → Advanced → Professional
Beginner · 1 — Foundations · ~12 min read · Module 1: Introduction & Setup
Introduction
This lesson is part of the beginner section. We explain Launch Settings and Configuration slowly, with examples you can copy and run. If something is unclear, read it twice — that is how everyone learns. launchSettings.json sets local URLs (https://localhost:7xxx) and environment name (Development). appsettings.json holds connection strings and logging levels. Wrong port or environment causes “works on my machine” bugs — especially when Development shows detailed errors Production hides.
Launch Settings and Configuration is setup knowledge. Without it, nothing else in ASP.NET Core will run. Spend time here until dotnet run works without errors.
When will you use this?
You need this before writing any ASP.NET Core code — same as installing Visual Studio before opening a project.
- Every .NET backend job expects you to run dotnet new and dotnet run on day one.
- Interviewers often ask you to explain Program.cs and what Kestrel does.
Real-world: Power BI-style analytics API
The Analytics team building Power BI-style analytics API uses Launch Settings and Configuration to open the right localhost port and Development environment locally. business analysts never see the C# code — they just get a fast, reliable KPI reports and filtered data export.
Production-style code
// Properties/launchSettings.json — applicationUrl
// appsettings.json
{
"ConnectionStrings": {
"Default": "Server=.;Database=ShopNest;Trusted_Connection=True;"
},
"Logging": { "LogLevel": { "Default": "Information" } }
}
What happens in production: In Power BI-style analytics API, a solid Launch Settings and Configuration foundation lets the team ship KPI reports and filtered data export on schedule without environment surprises.
Lesson example (start here)
Copy this smaller example first. Once it works, compare it with the real-world code above.
// Properties/launchSettings.json — applicationUrl
// appsettings.json
{
"ConnectionStrings": {
"Default": "Server=.;Database=ShopNest;Trusted_Connection=True;"
},
"Logging": { "LogLevel": { "Default": "Information" } }
}
Line-by-line walkthrough
| Code | What it means |
|---|---|
// Properties/launchSettings.json — applicationUrl | Comment — notes for humans; the compiler ignores it. |
// appsettings.json | Comment — notes for humans; the compiler ignores it. |
{ | Part of the Launch Settings and Configuration example — read it together with the lines before and after. |
"ConnectionStrings": { | Part of the Launch Settings and Configuration example — read it together with the lines before and after. |
"Default": "Server=.;Database=ShopNest;Trusted_Connection=True;" | Part of the Launch Settings and Configuration example — read it together with the lines before and after. |
}, | Closes a block started by { above. |
"Logging": { "LogLevel": { "Default": "Information" } } | Part of the Launch Settings and Configuration example — read it together with the lines before and after. |
} | Closes a block started by { above. |
How it works (big picture)
- launchSettings applies only locally.
- appsettings.Development.json overrides settings when ASPNETCORE_ENVIRONMENT=Development.
Do this on your computer
- Open launchSettings.json and note the https URL.
- Run the app and match the browser URL.
- Add a custom key in appsettings.json and read it in Program.cs with builder.Configuration.
- Read the real-world section and name which part of the app uses this topic.
- Run the example locally with dotnet run and confirm the same behavior.
- Change one value in the example (route, text, or connection string) and predict what will happen before you save.
Experiments — try changing this
- Change a string or route in the example and save — watch the browser or Swagger response update.
- Break the code on purpose (remove a semicolon), read the error message, then fix it.
Remember
launchSettings = local URLs and profiles. appsettings = configuration per environment. Never commit real passwords.
Common questions
What is ASPNETCORE_ENVIRONMENT?
A variable that picks which appsettings.{Environment}.json file merges in.
How long should I spend on Launch Settings and Configuration?
Until you can explain it in your own words and run the example without looking at the answer. Beginners often need 30–60 minutes per new concept; setup lessons may take one afternoon.
What if I get stuck on Launch Settings and Configuration?
Re-read the line-by-line walkthrough, check the terminal for red errors, and compare your code character-by-character with the example. Search the exact error text — someone else had it too.
Where is Launch Settings and Configuration used in real jobs?
See the real-world section above — the same pattern appears in LMS, banking, e-commerce, and SaaS backends. Interviewers ask you to explain it using one concrete example.