frustrating profiler error when you aren't actually using a profiler
The other day I was troubleshooting an Azure problem, and I had turned on my profiler:
Once I figured out the problem, I then turned off profiling, then re-published. Now my application would not work at all and I kept getting the error:
.NET Runtime version 4.0.30319.18033 - Loading profiler failed during CoCreateInstance.
Despite the fact that I wasn't using a profiler anymore. I rebooted and tried all sorts of other things, nothing seemed to work.
Not to say there is not a better fix (I tried all I could find elsewhere, nothing seemed to relate to my specific problem) but here is what I ended up doing.
Simply delete your deployment, and re-publish. This must re-set whatever turning on your profiler sets.
Remember that if this is a non domain dns instance, your address will be changed. Hope this can save someone a few hours.