Skip to main content

Azure: Create an Azure package file without using a Cloud Service project

A customer asked me if there was a way to keep their existing solutions intact and still be able to create an Azure package. Normally you have to add a Cloud Service project to your solution. This Cloud Service project contains all the information and required configuration to correctly build your Azure package.

But if you don’t want to do this, there is way around it by using the cspack command line tool for this(available as part of the Windows Azure SDK: http://msdn.microsoft.com/en-us/library/windowsazure/gg432988.aspx )

This tool allows you to create a deployment package from scratch.

Here are the required steps:

  • Create a servicedefinition file(.csdef). Probably the easiest way is to copy it from an existing cloud service project and adapt it to your needs
  • Build the (web) applications that you want to deploy
  • Execute the cspack command line tool using the following parameters:

cspack “c:\<path to the csdeffile>\servicedefinition.csdef” /role:<Name of the role as defined in the csdef file>;<location of the binaries> /sites:<Name of the role>;<name of the site path>;<location of the website files>

If you have multiple roles and sites, you have to add multiple /role & /sites arguments.

An example if you have the following servicedefinition file:

cspack “c:\testazurecloud\sampledefinition.csdef” /role:WebApplicationRole;c:\testazurecloud\MyWebApplication\bin /sites:WebApplicationRole;Web;c:\testazurecloud

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