Marco van Kimmenade
Developer to the bone.
Blogging about Azure and anything else that comes to mind.
This is part 9 of the DevOps with VSTS series
As part of The Third Way, Feature Flags provide functionality for savely experimenting in a live environment without impacting all customers.
The Feature Flag pattern does this by enabling or disabling a specific feature without the need to red(...)
This is part 8 of the DevOps with VSTS series
The Third Way of DevOps is about The Principles of Continual Learning and Experimentation.
The First Way The Principles of Flow allow that any change can be delivered to the customer in a fast and reliable way.
The Second Way, The Principl(...)
This is part 7 of the DevOps with VSTS series
A big part of The Principles of Feedback is making sure that the system is providing enough telemetry data about the performance and usage of the system.
By having this data, analysis can be done on the whole system, but especially on newly rel(...)
This is part 6 of the DevOps with VSTS series
By leveraging the ability in VSTS to create custom WorkItem Types, feedback flows that don't already have a supporting WorkItem can be easily created.
VSTS already supports different flows of feedback, like feedback about a bug that can be trac(...)
This is part 5 of the DevOps with VSTS series
The Second Way of DevOps is about The Principles of Feedback.
The First Way, Principles of Flow, makes sure that any change can be delivered to the customer in a fast and reliable way.
Since delivering new value is done in such a fast mann(...)
This is part 4 of the DevOps with VSTS series
The First Way is all about improving work going from left to right, eg. from concept to customer.
As part of this it is important to make work visible, reduce batch size and limit work in progress.
In VSTS the Kanban board can help tremend(...)
This is part 3 of the DevOps with VSTS series
Continuous Delivery is the automation of creating and updating environments and deploying a release package into an environment.
Automating this step enables us to reduce handovers and eliminate bottlenecks and therefor is a major improvement o(...)
This is part 2 of the DevOps with VSTS series
Continuous Integration is the automation of building and testing code every time a developer integrates changes into a shared repository.
Automating this step enables us to commit changes to the repository very fast and, using unit tests, verif(...)
This is part 1 of the DevOps with VSTS series
The Principles of Flow describes how value can be delivered to the customer, both internal as external, in the fastest and safest way.
This can be done by making sure all work is visible, by reducing batch sizes, limiting work in progress and a(...)
This series of blog posts will showcase a potential setup in using DevOps principles and patterns with Visual Studio Team Services.
In DevOps the Three Ways are at the foundation for all DevOps principles.
Using these principles, DevOps enables companies to deliver software in a faster and(...)
In this blogpost we're going to look at how we can persists the connection state of an IoTHub device into a SQL Database.
The connection state is also available in the IoTHub device registry, but quering the device registry each time an application needs the connection state, isn't optimal.
For a recent project I needed to host a WCF service in an Azure Cloud Service Worker Role.
This WCF service was secured using Client Certficiate authentication.
During a typical SSL handshake, the server will send a list of all trusted Root Certificate Authorities in the ServerHello messag(...)
Recently I received the Microsoft IoT Pack for Raspberry Pi 2
Using this starter pack you can create the WeatherStation sample that can be found over here
With this sample and combining it with the Azure IoT Hub and Stream Analytics it is very easy to display the data from the WeatherStati(...)
When you create a new Azure Service Fabric cluster, you can download the Resource Manager Template in the summary section.
This template (and the fact that you can download it so easily) is great but in my opinion there are a lot of parameters to fill in.
Therefor I simplified this templat(...)
For a recent project I needed to recreate an Azure IoT Hub automatically.
An Azure Resource Manager Template is perfect for this but I couldn't find any online.
So after some trial and error I figured out how the template should look like. Below is the result of that effort.
In one of my projects I'm having multiple Cloud Services that use ETW logging and use Windows Azure Diagnostics (WAD) to upload the logs into Azure Table Storage.
After I upgraded the Cloud Services to a new version, the logging suddenly failed.
I enabled Remote Desktop on one of the Worke(...)
With the recent announcement of the Public Preview of Azure Service Fabric, I've been building some test applications for it.
Once you deploy your application to the Cluster there are multiple ways to delete individual services, actors or the entire application.
You can use the Service Fab(...)
Recently I was having some problems with using Add-AzureAccount in PowerShell.
I could sign in correctly but as soon as I tried any Azure cmdlet I would get the error "No default subscription has been designated".
This error kept showing up, also after Remove-AzureAccount, restarting Power(...)
Recently Microsoft announced the public preview of the Azure IoT Hub.
The IoT Hub is a great solution to establish bi-directional communication between devices and the cloud. Furthermore, it has an authentication model per device, allowing you to manage per device credentials.
In this post(...)
There have been some people already who have blogged about Azure automation of Virtual Machines.
For my use case I needed a slightly different set up, so here is my use of Azure Automation.
My development machine is a Windows 10 Azure D3 VM which is running in my MSDN subscription.
When I was building this website, I wanted it to automatically deploy from VSO to my Azure Web App.
Since this website has been build with ASP.NET 5 (currently using beta 5 8) i couldn't just simply use the default stuff in VSO.
I found this great article by the VS ALM guys that discribe h(...)
Recently every time I tried to connect to Azure in the Visual Studio Server Explorer I kept getting this Multiple Matching Tokens error.
Trying to reconnect always gave me the Already Signed In message.
Selecting either the Remain signed in or Sign out and sign in with a different account (...)