I have been putting up with the debugger for some time, but now it seems that the Xamarin Studio debugger, especially when dealing with the iOS simulator, though the device has its issues too, has been getting worse. It seems that 70% - 90% of the time when launching my application the debugger loses its connection and then I have to retry. Often it starts on the second go but may still need a couple tries to get it to "stick" so I can actually run my application.
More recently I have been running into issues, on occassion but more frequently than before, where variables stay evaluating when I try to inspect them. In some cases when I am trying to step through the code a dialog pops up asking me to either wait or stop. It seems that often it is getting stuck on .ToString() calls which is what the debugger is saying even though the code isn't executing a .ToString() at the time. I assume this is to get details about object.
I have a a couple apps and they both do this. They are both map heavy and I have always had the "feeling" that perhaps it has something to do with the map initializing though I don't have an evidence of this.
Anyone else noticing issues like this?