Skip to main content

Deploying extra files when using WebDeploy

On one of the teams I’m coaching they are using Angular (4) in combination with ASP.NET Web API. This combination took a little more time to setup than for ASP.NET Core but worked quiet nice in the end.

In the current setup the Angular code is stored inside the ASP.NET Web API project:

image

To deploy the application to our servers, we configured a build process that contains the following steps:

  • Step 1 - Restoring the NuGet packages from our private package repository.
  • Step 2 – Compiling the .NET solution using MSBuild
  • Step 3 – Restore the NPM packages required for the Angular code
  • Step 4 – Execute the ng build command specify the environment and other parameters
  • Step 5 – Running the tests
  • Step 6 – Deploying the application using WebDeploy

image

After configuring all steps above, we noticed that everything was compiled nicely but after WebDeploy was completed only the C# assemblies were published on the web server. The files generated by Angular CLI were missing…

This makes sense as by default WebDeploy is only aware of the files that are tracked by the Visual Studio project inside the csproj file. To let WebDeploy know that some extra files need to be copied, we have to open up the .pubxml files and add some extra xml voodoo:

image

First add an extra target:

In this sample, we specify that we want to include all files in the dist folder and its subfolders(dist\**\*). The root of the folder is the same as the web project folder.

Second step is that we invoke this target before the web deploy file copy is executed or before the web deploy package is created:

That’s it!

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