Below are the ten most recent posts from my blog, mirrored from the original at

Creating Service Bus authorization rules with ARM errors out

Intro In my current project we use Azure Resource Manager (ARM) templates to help with deployments across multiple subscriptions and environments. One of the elements of the ARM template is adding a couple of Shared Access Policies to enable Read and Write on the queues we have in place. The policies have been defined on Service Bus level because they span multiple queues. Our ARM template functioned just fine, (automated) deployment was up & running and life was beautiful. Until our automated deployment to our development environment triggered in the night of January 24th. Our ARM template, not having been changed for a while, suddenly errored out with a Bad Request. The message read: Request payload is not in the expected format. Searching for the issue We checked everything: API versions (still version 2015-08-01, so no changes there), variables we introduced (no changes there) and parameters. We even stripped out all dynamic behavior just to be sure that wasn’t the cause. And it wasn’t. The offending part of the ARM template (the one that had functioned before) looked like this: {     "apiVersion": "2015-08-01",     "name": "[concat(variables('servicebus_namespace_name'), '/', 'RoleName')]",     "type": "Microsoft.ServiceBus/namespaces/authorizationRules",     "dependsOn": [ "[concat('Microsoft.ServiceBus/namespaces/', variables('servicebus_namespace_name'))]"      ],     "location": "[variables('location')]",     "properties": {         "Rights": [             //"Send",             "Listen"             //"Manage" ] } } I found an article Create a Service Bus authorization rule for namespace and queue using an Azure Resource Manager template. One of the things in that article is an exmple, that also holds a piece of template to create an Authorization Rule on Service […]
posted on Wednesday February 01 2017
tags: ARM, automation, azure, Error,

Unable to attach remote debugger after Visual Studio 2015 Update 2

As the title states: I was unable to attach the remote debugger (for instance to an Azure Web App) after installing Visual Studio 2015 Update 2. I got an error with something about invalid memory access or something like that. The solution is simple: install Remote Tools for Visual Studio 2015 Update 2. Go to the webite, pick your machine’s architecture (the x86 install won’t run on a x64 machine) and click download. After installing, you’re good to go! Hope this helps. PS: There’s a list of Related releases on the Visual Studio 2015 Update 2 page. Have a look, it’s helpful ;)
posted on Wednesday April 06 2016
tags: debug, Development, Error, Link, Visual Studio, VS2015,

Unable to find specific NuGet packages after update

After updating Visual Studio 2015 (there was an update for GitHub Extensions, one for the NuGet Package Manager and, of course, there was Visual Studio 2015 Update 2) I tried to add the WindowsAzure.Storage NuGet package to a project I started about a month ago. I opened NuGet Package Manager, went to the Browse tab and typed WindowsAzure.Storage. The result: No Packages Found. OK, so then I’ll just…. Wait… WHAT? No Packages Found After doing all sorts of things, including looking for other NuGet packages with the same result, I found what the issue seemed to be: the Package Sources weren’t up to par, since the Official feed had vannished. I fixed them to look like this: And then set the’Package source’ to be ‘All’ in the upper right corner of the NuGet Package Manager. Fixed it for me! Hope this helps.  
posted on Tuesday April 05 2016
tags: Visual Studio, VS2015,

Exception with EF code first migrations

Just ran into an exception when running both update-database and add-migration in the Package Manager Console for an EF Code First project. The Exception read: The type initializer for ‘System.Data.Entity.Migrations.DbMigrationsConfiguration`1’ threw an exception. The cause? An invalid config file for the project I was trying to run the tools for. So: if you run into this exception, check your configs ;)
posted on Friday March 18 2016
tags: Development, Error,

Running Visual Studio as an administrator causes ‘Save changes to devenv.sln’ when double clicking solutions

After making sure my Visual Studio always ran as an administrator by following my own post HowTo: Have Visual Studio always run as administrator on Windows 8, I got a message if I wanted to save changes to devenv.sln each and every time I double clicked a Solution. Since the problem kept occuring after installing Visual Studio 2015 CTP6, I wanted to solve it. So here we go! Double clicking a Solution file doesn’t start devenv.exe (which is set to be run as an administrator) but will cause the Microsoft Visual Studio Version Selector (VSLauncher.exe) to be run. This tool selects the right version of Visual Studio to open the Solution. Because VSLauncher.exe is not being run as an administrator, the error occurs. The Solution Find VSLauncher.exe, which is typically located at ‘C:\Program Files (x86)\Common Files\Microsoft Shared\MSEnv’ and make sure it runs as an administrator too. This will cause the Version Selector to be started with the correct privileges, helping it start devenv.exe with the right privileges. Problem solved ;) Hope this helps
posted on Thursday April 16 2015
tags: .Net, Tip, Visual Studio, VS2013, VS2015,

Scheduled build launches an hour early on TFS 2013 (after installing Update 3 or 4)

There’s new information in this issue. Please read the updates at the bottom of the article. We use our own TFS server and were using TFS 2013 Update 2 up until last Tuesday. We have several build definitions for my current project, and most of them are scheduled at a specific time, because we have specific times for automatic deployment. Up until Tuesday, everything seemed to work well and the Builds ran at the specified time (both before and after Daylight Saving Time applied). And then I installed Update 4… :) The issue After installing Update 4, our scheduled builds ran an hour early. Of course I checked both the time on the server and the time the build was scheduled for: these were fine. I looked at the Update 4 documentation, but couldn’t find anything related. I did see however the build server report its time setting as UTC +01:00, and the build definition stating UTC +02:00.Next up was searching the web, which pointed me to an article on Scheduled build launched 1 hour earlier. As a comment on this article, which is from July last year, Microsoft employee Mario mentions the issue is fixed in the (at that time) RC of the Summer Update. He also mentions: Once you install that Update on the server please recreate/re add the build definition and the database will now respect the right times. Visual Studio 2013 Update 3 & 4 Since we were using Update 2, I looked at the documentation of both Update 3 and Update 4. And if you go to the New technology improvements in Visual Studio 2013 Update 3 chapter and look at the Fixed issues paragraph you find this for […]
posted on Thursday April 09 2015
tags: TFS,

Error saving Galileo Wiring App in Visual Studio

Last week I received my Intel Galileo board (from and I started playing with developing for it yesterday. I created a first test project, but it didn’t run. Visual Studio couldn’t find the Arduino header file, which was probably due to a missing NuGet package (the Galileo C++ SDK). I tried to save the project, because you need to before you can manage NuGet packages, but to no avail. Visual Studio served me a ‘The operation could not be completed’ error without any additional information. A while ago I posted about some handy settings in Visual Studio like Zero-impact projects & Cutting/copying empty lines. Turns out that the Windows for IoT project template does some extra things upon creation. And with the ‘Save new projects when created’ checkbox unchecked, it’s not able to do that. Rendering the project unsaveable…   The solution It’s as easy as it is ugly to have to do this: simply check the checkbox in ‘Save new projects when created’ before creating your Windows for IoT project. Then you’re good to go…! Hope this helps
posted on Tuesday September 16 2014
tags: Development, Error, Gadgets, IoT, Visual Studio,

Fixing the Remote Desktop Connection to a Virtual Machine in Microsoft Azure

A few minutes before my second session at the Dutch Techdays started I tried connecting to my Virtual Machine in Microsoft Azure through remote desktop. It didn’t connect… The RDP client tried to connect to the Virtual Machine, but nothing happened. So I rebooted the VM and tried connecting again, confident that this would solve the problem. It didn’t connect…. again. As I started stressing out a bit (the VM was the main character of my session) I thought of one last thing I could try. Fixing the issue The next steps helped me save my Virtual Machine without too much loss of time (I was able to connect again just before the start of my session!): Go to the Azure Management Portal Open up the details of the VM you’re having trouble with Go to the ENDPOINTS tab (see image below) Select the ‘Remote Desktop’ endpoint and click EDIT at the bottom of the screen Change the public port to a different (random) number Wait for the changes to be propagated Success! Hope this helps.
posted on Wednesday May 07 2014
tags: azure, Congresses, Error, Tip,

Techdays 2014 The Netherlands

As I wrote earlier I presented at the 2014 Dutch Techdays. The session content is now available online. Find it here (Dutch): Session information + PDF of my presentation My presentation on SlideShare My session on Channel 9
posted on Wednesday May 07 2014
tags: azure, Congresses, HPC, Link, Personal,

Error comparing historic versions of a TFS source controlled file

When working with Visual Studio 2012 on our current project, the error ‘These files are not text files and cannot be opened in the comparison window.’ shows up every now and again. I’ve tried several things to solve this problem. Here’s the one that works: Close Visual Studio Navigate to your version of the ‘c:\users\{username}\AppData\Local\Temp\’ folder Delete the TFSTemp folder Restart Visual Studio and try again. You should be good to go! Hope this helps.
posted on Wednesday March 12 2014
tags: Error, TFS, VS2012,

latest tweets