Skip to main content

NuGet: prevent developers from upgrading to a newer version

I’m working on an Angular.js Single Page Application right now. One of the requirements is that we still have to support IE8. Therefore it’s important that we stay on the 1.* version number for jQuery because the 2.* release dropped support for IE8.

We are using NuGet and the jQuery Nuget package to keep our dependencies under control. The problem is that when we open up NuGet, jQuery was in the list of packages to update. As developers we all want to work with the latest and greatest, so I had to make sure that no one in my team accidently updated jQuery to 2.*.

You can fix this by executing following steps:

  • Open the packages.config file inside your project
  • Add an allowed versions attribute to the jQuery package
    • <package id="jQuery" version="1.9.1" allowedVersions="[1.9.1,2)" />
  • This tells NuGet that we allow all versions starting from 1.9.1 until 2(version 2 NOT included).

That’s it!

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

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