Skip to main content

Web Deploy Improvements in ASP.NET and Web Tools 2012.2 Update

Last week Scott Guthrie announced the release of the ASP.NET and Web Tools 2012.2 Update. This release not only offers some really nice new features for ASP.NET WebForms, ASP.NET MVC, ASP.NET Web API, SignalR and the web tooling in Visual Studio, but also adds some nice improvements to Web Deploy. (For the full list of new features, have a look at the release notes). 

What’s new?
  • First of all, Web site projects now have the same publishing experience as Web Application projects including publishing to Windows Azure Web Sites. 
  • Selective publish – for one or more files you can perform the following actions (after publishing to a Web Deploy endpoint):
    • Publish selected files.
    • See the difference between a local file and a remote file. (this even works for images!)
    • Update the local file with the remote file or update the remote file with the local file.
  • Apply config transformations on the publish profile next to the build profile.
    • This will combine the transformations you’ve specified at the build profile level with the transformations you’ve specified at the publish profile level.
    • An example:
      • “You have a QA environment and want to apply the same transformation to both a release and debug build. Before you had to configure a build configuration for every combination. In this case it was QA-Release and QA-Debug and copy the same transformation over between the 2 configs. Now you can create a config transform for QA, and keep the Release and Debug build configuration intact.”
  • One that isn’t new, but I want to mention again is the web.config transform preview. This allows you to preview the result of a transformation.It was added when releasing VS 2012 but a lot of people don’t know it exists.

PreviewTransform

For more information, have a look at the videos from Sayed Ibrahim Hashimi.

Labels:

Popular posts from this blog

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.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

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         ...
Read more