Needless to say this was quite the resource hog and we’d every now and then see unexpected issues with Visual Studio or the emulators. So in order to develop it locally we had to run 2 instances of Visual Studio 2013 and each of them would fire up an emulator. One project I worked on had a Web API running in an Azure cloud service and an ASP.NET MVC website running in another cloud service. You make a code change and the write – compile – debug process is slowed down big time because you have to wait for the Azure emulator to start up every time. A big bugbear when developing Azure cloud services is the Azure emulator.