Confusing windows
-
Due to various reasons I've ended up working on multiple VS projects all with the same name. I've got 2 on the go and am just about to get started on the 3rd. Please don't argue about how I ended up in this position, as that's not something I can fix right now. The problem is that if I've got these projects opened at the same time, I get confused as to which one I'm looking at. They are of course saved under different paths so if I spend the time to interrogate the file paths of .cpps and what have you I should be OK. But isn't there any easier way of telling apart the two VS instances I've got running both with MyProject.sln opened, both the seemingly identical code in them (unless you look at them under a microscope)?
Almost, but not quite, entirely unlike... me...
-
Due to various reasons I've ended up working on multiple VS projects all with the same name. I've got 2 on the go and am just about to get started on the 3rd. Please don't argue about how I ended up in this position, as that's not something I can fix right now. The problem is that if I've got these projects opened at the same time, I get confused as to which one I'm looking at. They are of course saved under different paths so if I spend the time to interrogate the file paths of .cpps and what have you I should be OK. But isn't there any easier way of telling apart the two VS instances I've got running both with MyProject.sln opened, both the seemingly identical code in them (unless you look at them under a microscope)?
Almost, but not quite, entirely unlike... me...
-
Due to various reasons I've ended up working on multiple VS projects all with the same name. I've got 2 on the go and am just about to get started on the 3rd. Please don't argue about how I ended up in this position, as that's not something I can fix right now. The problem is that if I've got these projects opened at the same time, I get confused as to which one I'm looking at. They are of course saved under different paths so if I spend the time to interrogate the file paths of .cpps and what have you I should be OK. But isn't there any easier way of telling apart the two VS instances I've got running both with MyProject.sln opened, both the seemingly identical code in them (unless you look at them under a microscope)?
Almost, but not quite, entirely unlike... me...
Our main form gets in your face with some horrible colours, not wishy washy pastels, in each different environment but this only relevant when you compile and run so it can be irritating having coded into the wrong instance. Multiple monitors, one for each instance, if the business are going to drive you nuts like this then make the buggers pay - 3 new HUGE monitors please. If you are the one making this decision then please remove your finger and rename the solutions!
Never underestimate the power of human stupidity RAH
-
I have a question on StackOverflow on How to change the title bar text of Visual Studio[^]. Maybe some of the feedback there can help you do that, and hopefully that may help you. I haven't tried any of the answers on VS 2012, or even on 2010 though.
Cool. I got it to work for VS 2010. :cool: But it doesn't seem to work for VS 2005... :suss:
Almost, but not quite, entirely unlike... me...
-
Due to various reasons I've ended up working on multiple VS projects all with the same name. I've got 2 on the go and am just about to get started on the 3rd. Please don't argue about how I ended up in this position, as that's not something I can fix right now. The problem is that if I've got these projects opened at the same time, I get confused as to which one I'm looking at. They are of course saved under different paths so if I spend the time to interrogate the file paths of .cpps and what have you I should be OK. But isn't there any easier way of telling apart the two VS instances I've got running both with MyProject.sln opened, both the seemingly identical code in them (unless you look at them under a microscope)?
Almost, but not quite, entirely unlike... me...
Been there. Updating the same module in three different code lines. Mistakes? What mistakes?
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
-
Due to various reasons I've ended up working on multiple VS projects all with the same name. I've got 2 on the go and am just about to get started on the 3rd. Please don't argue about how I ended up in this position, as that's not something I can fix right now. The problem is that if I've got these projects opened at the same time, I get confused as to which one I'm looking at. They are of course saved under different paths so if I spend the time to interrogate the file paths of .cpps and what have you I should be OK. But isn't there any easier way of telling apart the two VS instances I've got running both with MyProject.sln opened, both the seemingly identical code in them (unless you look at them under a microscope)?
Almost, but not quite, entirely unlike... me...
-
I've been there and this is what works for me: I hold the mouse pointer over the tab for the file and it gives the full path to the location of the file. From this you should be able to differentiate which one you are looking at.
that doesn't work if you don't use tabbed windows, unfortunately.
-
Due to various reasons I've ended up working on multiple VS projects all with the same name. I've got 2 on the go and am just about to get started on the 3rd. Please don't argue about how I ended up in this position, as that's not something I can fix right now. The problem is that if I've got these projects opened at the same time, I get confused as to which one I'm looking at. They are of course saved under different paths so if I spend the time to interrogate the file paths of .cpps and what have you I should be OK. But isn't there any easier way of telling apart the two VS instances I've got running both with MyProject.sln opened, both the seemingly identical code in them (unless you look at them under a microscope)?
Almost, but not quite, entirely unlike... me...
-
Due to various reasons I've ended up working on multiple VS projects all with the same name. I've got 2 on the go and am just about to get started on the 3rd. Please don't argue about how I ended up in this position, as that's not something I can fix right now. The problem is that if I've got these projects opened at the same time, I get confused as to which one I'm looking at. They are of course saved under different paths so if I spend the time to interrogate the file paths of .cpps and what have you I should be OK. But isn't there any easier way of telling apart the two VS instances I've got running both with MyProject.sln opened, both the seemingly identical code in them (unless you look at them under a microscope)?
Almost, but not quite, entirely unlike... me...
Just only open one at a time - VS is so fast at opening projects, it will hardly take any time to close one and open the next...
.\\axxx
-
Due to various reasons I've ended up working on multiple VS projects all with the same name. I've got 2 on the go and am just about to get started on the 3rd. Please don't argue about how I ended up in this position, as that's not something I can fix right now. The problem is that if I've got these projects opened at the same time, I get confused as to which one I'm looking at. They are of course saved under different paths so if I spend the time to interrogate the file paths of .cpps and what have you I should be OK. But isn't there any easier way of telling apart the two VS instances I've got running both with MyProject.sln opened, both the seemingly identical code in them (unless you look at them under a microscope)?
Almost, but not quite, entirely unlike... me...