Skip to main content

Building Azure solutions on your build server

Out-of-the-box building your Azure projects on the build server will fail. You probably get an error like below:

c:\builds\AzureProject\AzureProject1.ccproj(57,11): error MSB4019: The imported project "C:\Program Files\MSBuild\Microsoft\Cloud Service\v1.0\Microsoft.CloudService.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.

Probably the easiest solution is to install the Windows Azure SDK on your build server. However the SDK installer checks if some components like Visual Studio, IIS, … are available on the server. You can start to install all these components, but then you are polluting your clean build environment.

So what is a (better) alternative?

The solution we used was to just copy the necessary files and components. This means:

  • Copying the files under  C:\Program Files\MSBuild\Microsoft\Cloud Service\v1.0\ to the same location on your build server.( Program Files(x86) if you are on a 64bit system)
  • Copying the files under “C:\Program Files\Windows Azure SDK\v1.0\bin" to your build server.
  • As a last step, you’ll have to update the registry because the Microsoft.CloudService.targets file searches for the following keys:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\ServiceHosting\v1.0@InstallPath
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\ServiceHosting\v1.0@ToolsVersionSupportLevel
  • Export these registry keys and import them on your build server.

That did the trick for us. Anyone with a better solution?

Labels:

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

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