Sometimes when I try to debug in the normal way (F5), the solution builds, but doesn't start executing. This normally happens if I try to debug twice in a row without changing the code. It eventually does run if I wait a while and try again. The strange thing is that NCrunch is idle at the time, so it shouldn't be able to interfere.
I'm not entirely sure that this is caused by NCrunch, but it has only been happening since I installed it. Has anyone else had this problem?
I'm using NCrunch version 1.39.015b with Visual Studio Premium 2010.
Remco NCrunch Developer
#2001
25 May 2012 11:13 UTC
Hi Patrick,
NCrunch doesn't really have any connection with the normal build operation within Visual Studio, so if this issue is NCrunch related than it's likely to be indirectly so (which makes it very hard to track down). So far I haven't heard any reports of similar behaviour - though this isn't to say that others haven't also experienced it. All I can really suggest is to keep an eye on the logs within the output window around VS builds/debug sessions - as this may yield some clue as to why the application isn't being started. It may be worth trying to work for a few hours without NCrunch installed to confirm/deny whether it's related.
Cheers,
Remco
NCrunch doesn't really have any connection with the normal build operation within Visual Studio, so if this issue is NCrunch related than it's likely to be indirectly so (which makes it very hard to track down). So far I haven't heard any reports of similar behaviour - though this isn't to say that others haven't also experienced it. All I can really suggest is to keep an eye on the logs within the output window around VS builds/debug sessions - as this may yield some clue as to why the application isn't being started. It may be worth trying to work for a few hours without NCrunch installed to confirm/deny whether it's related.
Cheers,
Remco
Sorry to bother you with this. turns out the problem has nothing to do with NCrunch.
Post a reply
Log in to reply.