18312, time stamp: 0x4e5d8cf3įaulting module name: mscorwks.dll, version: 7.5446, time stamp: 0x4d8cdb54Īfter doing more testing (i.e., running several builds), I've discovered that WAStorageEmulator.exe's status API is actually broken in a couple of significant ways (which may or may not have impact on how you use it). NET Runtime version 7.5446 - Fatal Execution Engine Error (000007FEF46B40D2) (80131506)įaulting application name: DSService.exe, version.
I've checked the Application Event Log and found the following two entries: I've tried fiddling with a number of ProcessStartInfo settings, but nothing seems to work. ProcessStartInfo processToStart = new ProcessStartInfo()įileName = Path.Combine(SDKDirectory, 'csrun'), When I try to start it using this C# code, it crashes: using System.IO To start the emulator from the command line, I can use this: 'C:\Program Files\Windows Azure SDK\v1.5\bin\csrun' /devstore If the emulator isn't running, I want it to be started.
When running these locally, I want them to use the Azure Storage emulator which is part of the Azure SDK v1.5. I have some unit tests that use Azure Storage.