.NET
61 posts tagged with this.
-
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.
-
HttpClient DNS Refresh for IIS-Hosted .NET Apps
Long-lived IIS worker processes keep outbound sockets past DNS TTLs. Set connection lifetimes so .NET 10 apps pick up endpoint changes without a recycle.
-
Preload ASP.NET Core on IIS to Cut Cold Starts
App pool recycles leave the next visitor paying startup cost. IIS Application Initialization can warm ASP.NET Core before real traffic hits—when the host allows it.
-
app_offline.htm for Clean ASP.NET Core IIS Cutover
Drop app_offline.htm before you overwrite bins on IIS. It stops new requests, reduces file locks, and makes .NET 10 cutovers predictable on Windows hosts.
-
Rate-Limit ASP.NET Core APIs Before SQL Pools Fill
One noisy client can exhaust SQL connection pools on IIS. Use ASP.NET Core’s built-in rate limiter to reject excess traffic early—before controllers and EF Core run.
-
Set .NET Roll-Forward Safely for IIS Hosted Apps
Framework-dependent .NET apps on IIS inherit the host’s shared runtimes. Set rollForward explicitly so patch updates apply without surprise major jumps.
-
Keep IIS Disk Free: Logs, Temp Files, Uploads
ASP.NET apps fill Windows volumes with logs, temp compile output, and uploads. Control paths, retention, and app pool behavior before the host runs out of space.
-
FDD vs Self-Contained for .NET 10 on IIS Hosts
Framework-dependent .NET 10 publishes stay lean on Windows IIS when the host runtime is present. Self-contained bundles the runtime—use it only when you must pin a patch band the server lacks.
-
Health Checks for ASP.NET Core on IIS
Ship liveness and readiness checks that work with IIS in-process hosting. Avoid false downs from cold pools and noisy SQL probes.
-
Debug Slow IIS Pages with Failed Request Tracing
Turn on IIS Failed Request Tracing for ASP.NET apps without drowning in logs. Capture slow pages and 500s with tight rules you can leave on shared hosts.
-
Web Deploy Parameters for Multi-Env IIS Hosts
Stop baking secrets into publish output. Use Web Deploy parameters and .pubxml profiles so one .NET 10 package targets staging and production IIS cleanly.
-
Set ASP.NET Core Environment on IIS via web.config
Stop baking Staging vs Production into publish profiles. Set ASPNETCORE_ENVIRONMENT at the IIS layer so one package runs cleanly on Windows hosts.
-
Persist Data Protection Keys for ASP.NET Core on IIS
App pool recycles reset in-memory Data Protection keys and break cookies. Persist the key ring outside the site folder so auth and antiforgery survive restarts.
-
32-bit vs 64-bit IIS App Pools for .NET Apps
Pick the right IIS app pool bitness for .NET Framework and .NET 10 apps. Avoid native DLL load failures, address-space traps, and surprise memory pressure.
-
Folder Swaps and Smoke Tests for IIS .NET Deploys
Ship ASP.NET Core 10 to IIS with a staging folder, brief app_offline window, and a post-swap smoke check. Safer cutovers on shared and Windows VPS hosts without cloud slots.