Now it’s all cool, but If I debug something and I have finished debugging it will throw all the tabs together into one group and mess up all my good individual tab groups.
Anyone knows any Things that will prevent Visual Studio from doing this and remember which tabs go into which groups?
In fact, I believe there are many window layouts available (except your own customization). This is what Visual Studio requires when you first start and set up the environment One of your questions.
I know that the only way to solve this problem is to rearrange your windows when “debugging”. It should remember these settings and switch to them when debugging.
p>
I have set up Visual Studio 2008, as I want, one screen (with dual monitors) is only used for coding, and the other is set with multiple tab groups, Each contains different tabs, such as one set containing output, error list and todo list tabs, and another set of tabs with toolbox and properties window.
Now it’s all cool , But if I debug something and I have finished debugging it will throw all the tabs together into one group and mess up all my good individual tab groups.
Anyone Know of anything that will prevent Visual Studio from doing this and remember which tabs go into which groups?
This is because VS has separate layout settings for coding and debugging. The idea is that you don’t need things like output windows when coding , You need a solution explorer and a nice big code window. While debugging, you still want to see the code, but there may be many other windows that can help you (threads, breakpoints, etc.).
In fact, I believe there are many window layouts available (except for your own customization). This is one of the questions that Visual Studio asks you to ask when you first start and set up the environment.
< p>I know the only way to solve this problem is to rearrange your windows while “debugging”. It should remember these settings and switch to them while debugging.