So my Surface pro 3 running the anniversary update and latest updates got hot. So hot that I got the white thermometer of death.

I borrowed this picture from this topic on Microsoft Community. I could not take my own picture, because I was too upset.

So I contacted the store where I bought the device and there has been a change with the return policy in the Netherlands. So I could not send it in for repair at the store. I had to contact Microsoft myself. After logging in with my Microsoft account I could register the issue without any issues. Microsoft mailed me an UPS label for the box and within a few days I got a mail with a trackingcode that a similar device was heading my way.

My SP3 was over 1,5 year old and like a lot of overheating sp3’s equiped with an i7 cpu.

Windows Store

Having a lot of applications in the store, made it easy for me to get back to work fast. Open live writer is now a store app too so that is nice! The only applications I had to download outside the store were:

  • Visual Studio
  • FileZilla
  • Skype (I know there is a preview uwp app in the anniversary update…)
  • Sql Server Management Studio
  • Office 365
  • Notepad++
  • Adobe cloud (and Photoshop)
  • Chrome
  • Firefox (and mozbackup)
  • Github for Windows
  • TeamViewer
  • Snip (office mix)


It would save me even more time if those were in the store. And if Visual Studio had some kind of installed extension restore option.

So I was supprised how fast and good the service for the surface is and how fast people can get back to work with all the latest software on Windows 10. Could be even faster if I would do a system restore. But I wanted a clean install with all the legacy sql, mvc, azure installers etc. Maybe it will be even faster in the future with using chocolatey or oneget and restore settings stored in the cloud (onedrive)


I hope this will cheer up people who have Surface heating issues. I was only a week without the surface.

Good luck!

Pin on pinterest Plus on Googleplus Post on LinkedIn

The first step is of course install the remote debugging tools on the debug host 

When I fire up the Visual Studio Remote Debugging Monitor (latest version 12.0.30501.0), it says that it is already running on port 4018 so I have selected a different port. I selected 4019 and went to the “Tools” menu and then “Options (Ctrl + o) I have selected 'No authentication' and check 'allow any user to debug'. 

All there is left to do, is press play on the Visual studio side and make sure that you have the same port and no-auth set.

The other option is not to go to options but go to permissions (Ctrl + p) and add my Live ID/ Microsoft account from my developing machine, but that takes more clicks and my debugging device also forgets these settings. So you have to set it at every launch. Since I am also the admin of this tiny LAN, there is no security risk here and I can go with option 1.

screenshot taken from the interwebz

I am able to remotely debug, it's just that I have to setup the debugging every time on the client side (Lenovo Miix 2 8" tablet running win8.1) The development side does not need to be reconfigured every time.

After spending some time on google/bing/duckduckgo I have found which gives me details about launching the remote debugging monitor from the command line and give it some parameters.

I ended up with a small .bat file having these command line options:

`msvcmon -anyuser -noauth -port=4019`

Here is a good read with more info about remote debugger settings:

Good luck debugging!

Pin on pinterest Plus on Googleplus Post on LinkedIn

I had this error “A reference to a higher version or incompatible assembly cannot be added to the project” during my Windows Phone development. I wanted to add some dll’s because there are no nuget packages for smaato, mobfox etc.

At first I thought that it was because the dll’s were not build as portable class library. But then I found this other source online which gave me the correct and simple answer: Windows blocks the downloaded dll’s by default. You have to unblock it by going to the properties of the dll.

You can also unblock with powershell by using Unblock-File

So perhaps the dialog of visual studio should tell me that it is impossible to add a reference to a blocked dll.

Good luck!

Pin on pinterest Plus on Googleplus Post on LinkedIn

If you are still working with WebForms and the FormsAuthentication in visual studio 2013, you are probably missing the option `Asp.Net Configuration` which fires a tool to configure users and groups for your webapplication.

Sorry for the dutch screenshot by the way. But this is the tool that I am referring to.


I have found this post about manually starting IIS Express to manage it and I had some problems with it, so that is the reason that I am blogging about it. To help others, but also as a reference for myself if I have this issue again.

    1. Open Command Prompt (Windows key + X, or Windows key + R, cmd <enter>)
    2. Navigate to the IIS Express folder (cd C:\Program Files\IIS Express <enter>)
    3. Copy paste this:
      iisexpress.exe /path:C:\Windows\Microsoft.NET\Framework\v4.0.30319\ASP.NETWebAdminFiles /vpath:"/webadmin" /port:12345 /clr:4.0 /ntlm
    4. Open your browser and navigate to: http://localhost:12345/webadmin/default.aspx?applicationPhysicalPath=C:\Path\to\your\webformcode\&applicationUrl=/ (I had to login with my windows account) Do not forget to change the path to your code!


You can close IIS Express in the console with `Q` if you are done. I hope that this option will be put back in Visual Studio 2013 update 1 or something for all those webform developers.

Good luck!

    Pin on pinterest Plus on Googleplus Post on LinkedIn