I Wish Visual Studio Had a Read-Only Lock
-
Sometimes I have multiple instances of Visual Studio open, looking at code in one while writing and running code in the other. Only, I sometimes confuse the two of them and run the one I am supposed to only be looking at, causing who knows what kind of havoc. :doh: Wouldn't it be nice if VS had a read-only mode so you couldn't accidentally modify/run that solution (a bit like the Forms designer that has a lock so you don't accidentally move elements around)? I suspect it would add years to my life in heart attacks avoided.
-
Sometimes I have multiple instances of Visual Studio open, looking at code in one while writing and running code in the other. Only, I sometimes confuse the two of them and run the one I am supposed to only be looking at, causing who knows what kind of havoc. :doh: Wouldn't it be nice if VS had a read-only mode so you couldn't accidentally modify/run that solution (a bit like the Forms designer that has a lock so you don't accidentally move elements around)? I suspect it would add years to my life in heart attacks avoided.
AspDotNetDev wrote:
looking at code in one while writing and running code in the other
Bullshit, copy paste from the last project just like any VB programmer. I have trouble with SSMS query window, opening dev and UAT databases in the same instance of SSMS is fatal, I always start another instance. The number of times I have made a change to a stored proc, fired up the app and seen no difference is distressing.
Never underestimate the power of human stupidity RAH
-
AspDotNetDev wrote:
looking at code in one while writing and running code in the other
Bullshit, copy paste from the last project just like any VB programmer. I have trouble with SSMS query window, opening dev and UAT databases in the same instance of SSMS is fatal, I always start another instance. The number of times I have made a change to a stored proc, fired up the app and seen no difference is distressing.
Never underestimate the power of human stupidity RAH
Mycroft Holmes wrote:
opening dev and UAT databases in the same instance of SSMS is fatal
Amen to that, brother!
MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
-
Sometimes I have multiple instances of Visual Studio open, looking at code in one while writing and running code in the other. Only, I sometimes confuse the two of them and run the one I am supposed to only be looking at, causing who knows what kind of havoc. :doh: Wouldn't it be nice if VS had a read-only mode so you couldn't accidentally modify/run that solution (a bit like the Forms designer that has a lock so you don't accidentally move elements around)? I suspect it would add years to my life in heart attacks avoided.
I have, under similar circumstances, resorted to putting an uncommented line of code in the source I don't want to run, something like int c = "Don't run this because I just have it open for reference"; so i can't accidentally run it.
MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
-
Sometimes I have multiple instances of Visual Studio open, looking at code in one while writing and running code in the other. Only, I sometimes confuse the two of them and run the one I am supposed to only be looking at, causing who knows what kind of havoc. :doh: Wouldn't it be nice if VS had a read-only mode so you couldn't accidentally modify/run that solution (a bit like the Forms designer that has a lock so you don't accidentally move elements around)? I suspect it would add years to my life in heart attacks avoided.
Yes a RO option would be nice. The next best thing might be a different background color, and that is easy to achieve (menu Tools/Options/Environment/Fonts and Colors: DisplayItem=Plain Text, Background Color=Yellow). It will be persisted and applies to all instances, so you have to apply the change every time you launch and close down; I guess someone will figure out either a Project Configuration thingy, an add-on, a macro, whatever it takes. :)
Luc Pattyn [My Articles] Nil Volentibus Arduum
-
Yes a RO option would be nice. The next best thing might be a different background color, and that is easy to achieve (menu Tools/Options/Environment/Fonts and Colors: DisplayItem=Plain Text, Background Color=Yellow). It will be persisted and applies to all instances, so you have to apply the change every time you launch and close down; I guess someone will figure out either a Project Configuration thingy, an add-on, a macro, whatever it takes. :)
Luc Pattyn [My Articles] Nil Volentibus Arduum
Luc Pattyn wrote:
The next best thing might be a different background color
Oh you mean like the pretty tab colouring in IE when you open a related tab. Cute!
Never underestimate the power of human stupidity RAH
-
Sometimes I have multiple instances of Visual Studio open, looking at code in one while writing and running code in the other. Only, I sometimes confuse the two of them and run the one I am supposed to only be looking at, causing who knows what kind of havoc. :doh: Wouldn't it be nice if VS had a read-only mode so you couldn't accidentally modify/run that solution (a bit like the Forms designer that has a lock so you don't accidentally move elements around)? I suspect it would add years to my life in heart attacks avoided.
Perhaps the VS Tools/Options/Environment under Documents you can uncheck the Allow editing of read-only files... Then change the files in your model project to read-only (or have them in source control). HTH
Karl - WK5M PP-ASEL-IA (N43CS) PGP Key: 0xDB02E193 PGP Key Fingerprint: 8F06 5A2E 2735 892B 821C 871A 0411 94EA DB02 E193
-
Sometimes I have multiple instances of Visual Studio open, looking at code in one while writing and running code in the other. Only, I sometimes confuse the two of them and run the one I am supposed to only be looking at, causing who knows what kind of havoc. :doh: Wouldn't it be nice if VS had a read-only mode so you couldn't accidentally modify/run that solution (a bit like the Forms designer that has a lock so you don't accidentally move elements around)? I suspect it would add years to my life in heart attacks avoided.
just type "banana" at the head of the file, and remember not to check it in.
I wanna be a eunuchs developer! Pass me a bread knife!