CI/CD
7 posts tagged with this.
-
Keep Host Config Intact When Publishing .NET 10
Blind Web Deploy overwrites connection strings and rewrite rules on shared IIS. Separate code from host config with skip rules and layered settings.
-
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.
-
Ship .NET 10 With Staging Slots, Not Blind Overwrites
Stop overwriting production first. Use a publish-once pipeline, staging slots, and post-deploy smoke checks that fit shared IIS and Windows VPS.
-
GitHub Actions Web Deploy for .NET 10 on IIS
Wire publish and Web Deploy into GitHub Actions so ASP.NET Core 10 reaches IIS the same way every push, with safe excludes and a smoke check.
-
Deploy .NET 10 to IIS with Web Deploy and CI
Ship ASP.NET Core apps to IIS with Web Deploy, CI publish, config transforms, and post-deploy smoke checks. Patterns for shared and VPS hosts.
-
Reliable CI/CD Pipelines for .NET 10 Deployments
CI/CD patterns that reduce deployment failures for .NET workloads: pipeline structure, automation steps, and monitoring for Windows Server hosts.
-
CI/CD Patterns for Reliable .NET 10 Deployments
Modern CI/CD pipelines make ASP.NET Core releases faster and more reliable. Proven patterns for automation, testing, and deployment on Windows Server.