VSTS Web Deploy执行成功但网站显示IIS默认页面的问题咨询

Hey there! Let's break down what's happening here and how to fix it.

First: Do you need an extra unzip step? #

Short answer: Probably not. The VSTS Web Deploy task (whether you're using the classic IIS Web Deploy task or the Azure App Service Deploy task) is designed to automatically handle unpacking and deploying your web package (either .zip or .msdeploy.zip format) to the target IIS server. Adding an extra unzip step is usually unnecessary unless you're working with a custom package the task doesn't recognize.

Why you're seeing the IIS default page #

If the deployment says it succeeded but you're still seeing the default IIS welcome page, here are the most common culprits to check:

1. Verify the target path in your Web Deploy task #

Double-check the IIS Site Name and Physical Path configured in your release pipeline's Web Deploy step. It's easy to accidentally deploy to a different site, a sub-application, or a directory your IIS site isn't pointing to. For example:

• If your IIS site maps to C:\inetpub\wwwroot\MyApp, make sure the Web Deploy task is deploying to that exact path, not just C:\inetpub\wwwroot.

2. Check if your deployment package has the right content #

Open the .zip package generated by your build pipeline and confirm it includes all your app's necessary files:

• Entry points like index.html, default.aspx, or web.config
• Binaries, static assets, and any other files your app needs to run
  If the package is missing these, the deployment will "succeed" but leave the target directory empty (or with only default IIS files).

3. Confirm IIS default document settings #

Head to your IIS server, open the site's settings, and check the Default Documents list. Make sure your app's entry file (e.g., index.html) is listed and prioritized above the default IIS welcome page files. If your entry file isn't in the list, IIS will fall back to showing the default page.

4. Dig into the deployment logs (not just build logs) #

Your build log might say the package was created successfully, but you need to look at the release pipeline's deployment logs to see exactly what the Web Deploy task did. Look for lines like:

Updating file (C:\inetpub\wwwroot\MyApp\index.html)

If you don't see entries for your app's files, the task might not be syncing the package content to the target directory correctly.

5. Check your Web Deploy task configuration #

Make sure you've selected the right deployment method and package type:

• Ensure the task's Deployment Method is set to Web Deploy (not FTP or another option)
• If you're using a custom .zip package, confirm it's structured correctly for Web Deploy (it should include necessary deployment manifest files if it's a proper Web Deploy package)

Next steps #

Start with verifying the target path and package content—those are the most common fixes. If you still can't figure it out, share a snippet of your deployment logs (focus on the Web Deploy task section) and we can dig deeper!

内容的提问来源于stack exchange，提问作者Hos