updated readmes

Author: codebytes

01-basic-console/README.md

@@ -1,15 +1,10 @@
-# 02 - Basic Console
+## Overview
 
-Minimal .NET console template baseline. Used as a control sample before adding configuration providers.
+- Baseline .NET console sample with top-level statements.
+- Use as the control before layering configuration providers.
 
 ## Run
 
 ```powershell
-dotnet run --project 02-basic-console
+dotnet run --project 01-basic-console/BasicConsole.csproj
 ```
-
-## Key Points
-
-- Single `Program.cs` using top-level statements.
-- Prints "Hello, World!".
-- No configuration providers yet (contrast with later samples).

02-generic-host/README.md

@@ -1,14 +1,10 @@
-# 01 - Generic Host
+## Overview
 
-Introduces generic host template using `Host.CreateApplicationBuilder`.
+- Shows Host.CreateApplicationBuilder scaffolding for configuration, logging, and DI.
+- Demonstrates long-running host lifetime versus a simple console exit.
 
 ## Run
 
 ```powershell
-dotnet run --project 01-generic-host
+dotnet run --project 02-generic-host/GenericHost.csproj
 ```
-
-## Key Points
-
-- Foundation for adding services, logging, configuration in a structured way.
-- Execution continues after initial code until host shutdown.

03-json-config/README.md

@@ -1,19 +1,10 @@
-# 03 - JSON Configuration
+## Overview
 
-Introduces the JSON configuration provider via `AddJsonFile("config.json")`.
+- Loads config.json via AddJsonFile.
+- Reads values with the IConfiguration indexer.
 
 ## Run
 
 ```powershell
-dotnet run --project 03-json-config
+dotnet run --project 03-json-config/JsonConfig.csproj
 ```
-
-## Key Points
-
-- Builds an `IConfigurationRoot` with a single JSON file.
-- Accesses values using indexer: `configuration["greeting"]`.
-- Establishes baseline for precedence demos (env vars, command line) in later samples.
-
-## Try
-
-Edit `config.json` and re-run to see value changes (no reload-on-change here).

04-environment-variables/README.md

@@ -1,25 +1,14 @@
-# 04 - Environment Variables
+## Overview
 
-Adds `AddEnvironmentVariables()` showing how environment variables override JSON values.
+- Adds environment variables provider on top of JSON.
+- Illustrates overriding keys such as environment or greeting.
 
 ## Run
 
 ```powershell
-$env:environment = "qa"
-dotnet run --project 04-environment-variables
+dotnet run --project 04-environment-variables/EnvironmentVariables.csproj
 ```
 
-### Bash
+## Notes
 
-```bash
-environment=qa dotnet run --project 04-environment-variables
-```
-
-## Key Points
-
-- Provider order: JSON then Environment -> env vars win when keys collide.
-- Cross-platform examples (PowerShell / bash) moved from code comments to README.
-
-## Try
-
-Set `greeting` or `environment` via environment variable and verify override.
+- Set environment variables in your shell before running (PowerShell: $env:environment='qa').

05-command-line-args/README.md

@@ -1,23 +1,14 @@
-# 05 - Command Line Arguments
+## Overview
 
-Adds `AddCommandLine(args)` to show highest-precedence overrides.
+- Adds command-line configuration for highest-precedence overrides.
+- Mixes environment variables and switches to highlight precedence order.
 
 ## Run
 
 ```powershell
-dotnet run --project 05-command-line-args -- --environment=prod --greeting=Hey
+dotnet run --project 05-command-line-args/CommandLineArgs.csproj -- --environment=prod --greeting=Hey
 ```
 
-## Precedence (Highest → Lowest)
-
-1. Command line
-2. Environment variables
-3. JSON file
-
-## Try
-
-Combine env vars + command line to observe override order.
-
 ### Examples
 
 ```bash
@@ -26,3 +17,7 @@ environment=qa dotnet run --project 05-command-line-args
 environment=qa dotnet run --project 05-command-line-args -- --environment=prod
 greeting=hey dotnet run --project 05-command-line-args -- --environment=prod
 ```
+
+## Notes
+
+- Remember the -- separator so dotnet passes switches through to the app.

06-in-memory-config/README.md

@@ -1,15 +1,10 @@
-# 06 - In-Memory Configuration
+## Overview
 
-Uses `AddInMemoryCollection` to seed configuration dynamically at runtime.
+- Seeds configuration with AddInMemoryCollection.
+- Useful for tests or runtime-only defaults.
 
 ## Run
 
 ```powershell
-dotnet run --project 06-in-memory-config
+dotnet run --project 06-in-memory-config/InMemoryConfig.csproj
 ```
-
-## Key Points
-
-- Great for tests or programmatic seeding.
-- Shows accessing a key not present (`SomeKey`) returning null.
-- Prepares for binding + sections in later demos.

07-user-secrets/README.md

@@ -1,21 +1,14 @@
-# 07 - User Secrets
+## Overview
 
-Demonstrates `AddUserSecrets<Program>()` for local secret storage (development only).
-
-## Setup
-
-```powershell
-dotnet user-secrets init --project 07-user-secrets
-dotnet user-secrets set "greeting" "SecretHello" --project 07-user-secrets
-```
+- Loads secrets from the user secrets store during Development.
+- Keeps API keys out of source control.
 
 ## Run
 
 ```powershell
-dotnet run --project 07-user-secrets
+dotnet run --project 07-user-secrets/UserSecrets.csproj
 ```
 
-## Key Points
+## Notes
 
-- User secrets override JSON but are not checked into source.
-- Suitable for API keys during local dev; not for production.
+- Initialize secrets via 'dotnet user-secrets init --project 07-user-secrets' and set the expected keys before running.

08-configuration-sections/README.md

@@ -1,21 +1,17 @@
-# 09 - Configuration Sections
+## Overview
 
-Demonstrates hierarchical keys (e.g. `greeting:message`) and retrieving nested values.
+- Explores hierarchical sections such as Greeting:Message.
+- Shows how nested keys flow from JSON, environment variables, and command-line arguments.
 
 ## Run
 
 ```powershell
-dotnet run --project 09-configuration-sections -- --greeting:color=blue
+dotnet run --project 08-configuration-sections -- --greeting:color=blue
 ```
 
 ### Additional Examples
 
 ```bash
-dotnet run --project 09-configuration-sections -- --greeting:color=green
+dotnet run --project 08-configuration-sections -- --greeting:color=green
+dotnet run --project 08-configuration-sections/ConfigurationSections.csproj
 ```
-
-## Key Points
-
-- Shows colon-delimited keys for hierarchy.
-- Mixes JSON + environment + (optional) user secrets + command line.
-- Basis for section binding in later samples.

09-command-line-mappings/README.md

@@ -1,22 +1,17 @@
-# 08 - Command Line Mappings
+## Overview
 
-Adds a custom switch mapping dictionary to map friendly switches to config keys.
+- Maps friendly switches to configuration keys with AddCommandLine(args, mappings).
+- Still supports raw colon-delimited arguments when needed.
 
 ## Run
 
 ```powershell
-dotnet run --project 08-command-line-mappings -- --color=green --greeting="Hi"
+dotnet run --project 09-command-line-mappings/CommandLineMappings.csproj -- --color=green
 ```
 
 ### Additional Examples
 
 ```bash
-dotnet run --project 08-command-line-mappings -- --greeting:color=blue
-dotnet run --project 08-command-line-mappings -- --color=blue
+dotnet run --project 09-command-line-mappings -- --greeting:color=blue
+dotnet run --project 09-command-line-mappings -- --color=blue
 ```
-
-## Key Points
-
-- Demonstrates `AddCommandLine(args, mappings)`.
-- Enables shorter / domain-friendly switches.
-- Both mapped and raw hierarchical syntax work.

10-key-per-file/README.md

@@ -1,27 +1,10 @@
-# 14 - Key Per File Provider
+## Overview
 
-Reads individual config values from files in a directory using `AddKeyPerFile`.
-
-## Directory
-
-`keyPerFile/` contains one file per key. File name = key; file content = value.
+- Uses AddKeyPerFile to read secrets from the keyPerFile/ directory.
+- Great for Docker or Kubernetes mounted secrets.
 
 ## Run
 
 ```powershell
-dotnet run --project 14-key-per-file
-```
-
-### Environment Override Examples (PowerShell)
-
-```powershell
-$Env:ENVIRONMENT="qa"; dotnet run --project 14-key-per-file
-$Env:ENVIRONMENT="production"; dotnet run --project 14-key-per-file
-$Env:ENVIRONMENT=$NULL; dotnet run --project 14-key-per-file
+dotnet run --project 10-key-per-file/KeyPerFile.csproj
 ```
-
-## Key Points
-
-- Useful for Kubernetes secrets (mounted files).
-- `optional: true` allows directory absence without failure.
-- `GetDebugView()` demonstrates provider/value origins.