Skip to main content

Web Deploy 3

Between all the announcements about the release of Visual Studio 2012, Windows 8, Windows Server 2012 and so on, I noticed one small announcement: the release of Web Deploy 3.

Web Deploy 3.0 can be installed using these links x86/x64. More details on installation can be found in Installing & Configuring Web Deploy tutorial.

Let’s have a look at some of the new features available in Web Deploy 3:

  • Deployment & Migration to IIS8: migrate to IIS8 from IIS 6, IIS7 and IIS7.5.
  • Publishing to Microsoft Azure Websites: deploy websites to Microsoft’s new Azure Websites offering.
  • Incremental Database Publishing using Data Tier Application (DAC) framework: incremental data sync and SQL Azure download using SQL DACPAC framework.
  • Automatic Backup:  allows server administrators to configure servers in such a way that each publish will automatically generate a backup and store it on server. If you need to roll back or go to a previous version, you will be able to do it without involving server administrator.
  • PowerShell Cmdlets: PowerShell Cmdlets for common Web Deploy tasks.
  • Improved Parameterization
  • Enabling Application Offline: automatically drops a blank App_Offline.htm file into the root of the application folder.
  • Changing authentication mode for a given website
  • Automatically disabling proxy settings
  • Support for IPv6-style bindings in certificate sync logic

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...