Skip to main content

Visual Studio 2010 Web Deploy improvements

Microsoft announced some important improvements in the Visual Studio 2012 Web Deploy.

I noticed that when you install the new Windows Azure SDK for Visual Studio 2010, you will also get the same updates for the Visual Studio 2010 Web Publishing Experience.

These updates include some of the following  features:

  • Updated Web Publish dialog
  • Support to import publish profiles (.publishSettings files)
  • Support to configure EF Code First migrations during publish
  • Support to create web packages in the publish dialog
  • Publish profiles now a part of the project and stored in version control by default
  • Publish profiles are now MSBuild files
  • Profile specific web.config transforms

After installing the SDK, you get a new Publish dialog:

PublishDialogProfile

You can now import a .publishsettings file(provided by many web host sites and by Windows Azure) and you can also manage your publish profiles.

One of the things I like the most is that these publish profiles are now stored as a part of your project under the folder Properties\PublishProfiles as .pubxml files:

image

These .pubxml files are  just normal MSBuild files so you can modify these files in order to customize the publish process. You can also leverage these publish profiles to simply publishing from the command line:

msbuild.exe SOFAServicesHost.csproj /p:DeployOnBuild=true;PublishProfile="SOFA – Release";Password={INSERT-PASSWORD}

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