Skip to main content

Asp.NET MVC BundleConfig: {version} string

One of the neat features inside the ASP.NET Optimization library is the support for a {version} string. Before you had to update your BundleConfig.cs each time that you upgraded one of your included JavaScript/CSS libraries.  The{version} placeholder tells the bundler to look for a string in the form of N[.N[.N]] and pick the file with the highest numbers.

You can see this feature in action by looking at the BundleConfig you get out-of-the-box when creating a new ASP.NET MVC application:

This will load the latest JQuery file that can be found inside my Scripts folder:

image

You can do the same thing for Modernizr or any other library that uses the same versioning pattern.

There is only one thing missing in this feature; it only works when the version is part of the filename not of a folder. For example, when you use the Kendo UI libraries you’ll see that they don’t have a version number in every file but instead have the version number on the folder level.  Unfortunately this doesn’t work with the {version} number feature and you still have to update the references yourself:

image

image

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.

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

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