111 reputation
4
bio website going-round.nl
location United Kingdom
age 32
visits member for 2 years, 10 months
seen Jun 26 at 8:24

Web-developer (in the broadest sense) for a financial institution, with a love for GIS applications.


Feb
4
awarded  Supporter
Jan
3
comment Visual Studio 2012 cursor behaviour in locked files
Yes, that is the message I'm getting. But I don't mind that it prevents me from editing. What I mind is that it will move my cursor. So when I stop the solution from running after closing the message and continue with what I wanted to do, my cursor will not be where I was when I first tried to change something.
Jan
3
comment Visual Studio 2012 cursor behaviour in locked files
I'm compiling/running in debug mode.
Jan
3
awarded  Editor
Jan
3
revised Visual Studio 2012 cursor behaviour in locked files
added 1 characters in body
Dec
24
comment Visual Studio 2012 cursor behaviour in locked files
Yup, you just want to make the change when you know what to do, forgetting yo're still in debug mode. However, it will already make the cursor jump before you stop debugging, it will already jump after you close the info-popup that you can't make changes while debugging.
Dec
24
awarded  Student
Dec
24
comment Visual Studio 2012 cursor behaviour in locked files
When looking through the code, I sometimes forget that I am still in debug mode when I decide I need to make a change somewhere. That's when it happens. I'm not trying to purposefully change code while debugging (which is why I said it was fine that files get locked). I've never noticed this behaviour in older versions of Visual Studio. Trying to edit a locked file should not result in the cursor changing it's location.
Dec
24
asked Visual Studio 2012 cursor behaviour in locked files
Sep
15
awarded  Autobiographer