.NET 10
88 posts tagged with this.
-
Web Deploy Parameters and Post-Publish Smoke Tests
Most IIS outages after a .NET ship are bad config, not bad code. Parameterize Web Deploy, keep secrets off disk, and gate traffic on a short smoke script.
-
Put Forwarded Headers First in the ASP.NET Pipeline
IIS already terminated TLS, yet apps still log http and 127.0.0.1. Run UseForwardedHeaders before HTTPS redirects and auth or scheme and client IP stay wrong.
-
SqlClient Encrypt Defaults Break Quietly After NuGet Bumps
A Microsoft.Data.SqlClient bump can flip Encrypt on and drop SQL connections from IIS overnight. Here is the failure mode we see and how to set Encrypt on purpose.
-
Ship .NET 10 With Staging Slots, Not Blind Overwrites
Stop overwriting production first. Use a publish-once pipeline, environment slots, and post-deploy smoke checks that fit shared IIS and Windows VPS reality.
-
Stop Regenerating Data Protection Keys on Every Recycle
App pool recycles that wipe in-memory Data Protection keys log everyone out. Persist the key ring outside the publish folder so cookies and antiforgery survive IIS restarts.
-
Folder Swap Cutover for .NET 10 on IIS
Shared and VPS IIS hosts rarely offer Azure-style slots. Publish to a sibling folder, smoke-test it, then flip the site physical path for a clean cutover.
-
Parameter Sniffing Fixes for ASP.NET SQL Workloads
One cached plan can make the same ASP.NET query fly or crawl. Spot parameter sniffing on SQL Server and fix it without blanket recompiles.
-
Output Cache for ASP.NET Core 10 APIs on IIS
Cut repeat SQL and CPU on IIS-hosted APIs with ASP.NET Core output cache. Wire policies, vary-by rules, and tag eviction so responses stay fast and correct after recycles.
-
Harden ASP.NET Core Auth Cookies on IIS
Lock down cookie authentication for ASP.NET Core 10 on IIS: Secure, HttpOnly, SameSite, names, and lifetimes. Concrete CookieOptions and hosting notes you can ship.
-
ANCM In-Process vs Out-of-Process on IIS
Choose the right AspNetCoreModuleV2 hosting model for .NET 10 on IIS. In-process wins on latency; out-of-process wins on isolation—here is how to set both.
-
PathBase for ASP.NET Core Under IIS Virtual Apps
ASP.NET Core under an IIS virtual app misbuilds links and cookies unless PathBase is set. Wire middleware and web.config so /api and sub-apps stay correct.
-
IIS App Pool Recycling Without Dropping ASP.NET Requests
Default IIS recycles hit at awkward hours and can cut in-flight work. Schedule quiet-hour recycles, enable overlap, and set shutdown limits so ASP.NET finishes cleanly.
-
GitHub Actions Web Deploy for .NET 10 on IIS
Wire publish and Web Deploy into GitHub Actions so ASP.NET Core 10 hits IIS the same way every push. Covers profiles, safe excludes, and a post-deploy smoke check.
-
SQL Connection Pools and Timeouts on IIS Hosts
Pool exhaustion often surfaces as random SQL timeouts under load. Tune Max Pool Size, Connect Timeout, and CommandTimeout for ASP.NET apps on IIS before traffic spikes.
-
Tune .NET GC for ASP.NET Core App Pools on IIS
Default GC settings can thrash IIS app pools under load. Align heap limits with recycle thresholds so ASP.NET Core 10 stays stable on Windows hosts.