Web Deploy
9 posts tagged with this.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Deploy .NET 10 to IIS with Web Deploy and CI
Ship ASP.NET Core apps to Windows IIS with Web Deploy, CI publish, config transforms, and post-deploy smoke checks. Practical patterns for shared and VPS hosts.
-
Stop Web Deploy from Editing Website ACL Permissions
Prevent Microsoft Web Deploy from automatically editing your website's ACL permissions during publish. Set IncludeSetAclProviderOnDestination to False using MSBuild commands or by editing your project and targets files to avoid permission errors.
-
Is Microsoft Web Deploy Publishing Supported on Windows Shared Hosting?
Yes, all Windows shared hosting packages support Microsoft Web Deploy Publishing for Web Matrix and Visual Studio 2010+. Enable it via the Web Publishing tab in each website's settings to generate credentials and profiles for direct IDE deployments.