Test view keeps dissapearing in visual studio - visual-studio

I have visual studio 2008 TS both on my laptop as on my desktops(work & home).
For some reason the one on my laptop keeps removing the test view window from my window lay-out.
I can put it back by going Test=>windows=>test view, but as soon as my test run ends, the window is gona again. Quite anoying since I can't see the test results that way.
any ideas on how to fix it?

Try doing "Reset" to your views (i.e. all the windows, placement and which are open), and re-arrange them all over again. It worked for me when my "Pending Changed" window kept re-duplicating and/or disappearing.

Related

Visual Studio always closes Output window when build starts

I have a weird problem with Visual Studio Premium 2013. VS has taken to closing the Output window after my build starts. If the window is unpinned, it briefly opens at the start of the build, and then auto-hides. If it's pinned, it briefly gets selected, and then moves to another pinned window (it usually opens the Error List window and switches to that). The one thing it always makes sure of is that it switches away from the Output window. This is a behaviour that has started recently and I have no idea why - it didn't used to, and I don't remember changing anything related to this behaviour. Here's my settings, which should cause the Output window to stay open:
I've even tried deleting the solution's .suo file, but this problem persists.
Can anyone tell me how to get the Output window to stay open during a build again?
Well, I think this has something to do with the fact that the solution I'm building does a bunch of automated stuff, including the building of some .tt files. It's not a configuration issue in my Visual Studio because the Output window doesn't disappear when I'm building a new simple project I create from scratch, so I guess there's probably nothing I can do to stop the Output window disappearing for this project.

How can I determine why Visual Studio 2008 is hanging?

Visual studio is just hanging. The GUI just sits there and the CPU is at or near 0%.
I've let it sit for close to hour to see if it would resume, to no avail.
What is weird, is that the GUI doesn't respond to clicks anywhere, however, it re-draws correctly. If I drag another window over it, after the window passes over a portion, it is re-drawn correctly.
At the bottom of the VS window, it sometimes says 'Analyzing database schema. Your database projects will be ready after 5030 operations are completed', however, the GUI has hanged without it there.
I'm not sure if this is the cause or not.
I've tried /safemode, but I need the DB functionality loaded and using /safemode disables them.
I'm at a loss really.
More info -- The window stays as an unselected window even when I click on it. It's as though the whole thing is suspended except for the fact that it is redrawn properly when something else passes over it.
It might be worthwhile to delete all of the temporary files (.ncb, etc.) that get created within your solution directory, and let VS re-create them. Sometimes they get corrupted.
The next thing I would do isto use ProcessExplorer to see if I can identify a thread that seems to be hanging, and whether it's in a particular module.

Visual Studio Dual Monitor Layout : Watch/Debug Window keeps Popping on Left Screen

Every Time I launch a Debug Session VS 2010 pops the Watch/Debug Windows on the left Screen. I then move it manually to the Right One. After ending the session, going back to code, and relaunching a debug session, that damned Watch window pops on the left again. It turns me crazy ! Why isn't VS memorizing where I have put that window ???
Do you stop debug session with Shift+F5 or by quitting application which is being debugged? VS seems to forget window positions if debugging process was stopped by Shift+F5.
I tried the solution I found on this post. Did not work.
Seems like it's the exact same problem as with the find dialog (see this post)
Ended-up docking the heck out of the Watch/debug window into a more "stable" panel (Class view in my case).
This still looks like an annoying known bug in VS 2010. This sucks.
Visual studio 2010 has at least 3 screen modes.
Normal
Full
Debug
You should export the window settings after entering into the desired screen mode(in your case, debug).
Steps
Start 'debug' your project
Move the desired windows(watch/debug) to the 2nd monitor on right
Goto Tools>Import and Export Settings>Export selected environment settings>General Settings>Window Layouts and export it into a file.
Load the settings by using the import settings in the same window
Visual studio would remember your settings and would move the window to the 2nd monitor on the right, whenever you enter 'debug' mode.
As a tip, it is a great idea to create macros to load window settings and to assign keystrokes to switch between window modes, depending on the kind of development you are on.
code to create a macro to import a vssetting file:
DTE.ExecuteCommand("Tools.ImportandExportSettings", "-import:Path to VSSetting File")

Object Test Bench flashes quickly whenever I run (F5) in VS2008

Maybe a silly question but one day I did something accidentally in VS2008 and ever since then, whenever I hit F5, just before my app appears, I see a quick flash of a small window labeled "Object Test Bench". ie, it appears and very quickly disappears.
I've read about Object Test Bench and (since this happened) had a quick play with it in View / Other Windows but I haven't been able to stop that quick flash.
It's not really a problem, VS seems to work fine but I'm always uncomfortable about something happening that I don't understand and didn't happen before.
I also have the same problem. I once had JetBrain's Resharper 4.5 installed. I uninstalled it after my trial expired, and I think that's when I noticed the Object Test Bench popping up when I debug.
Did either/both of you have Resharper or any other Visual Studio add-on installed/uninstalled before this problem?
UPDATE
Try resetting the Visual Studio settings. How to: Reset Your Settings
After resetting, the object test bench popup went away.
If you would rather not lose all of your settings:
export your current settings
reset all settings
import selected settings from your exported back-up settings. Keep everything else, but de-select 'window layouts'

Visual Studio 2008 Window layout annoyance

I'm having a weird issue with Visual Studio 2008. Every time I fire it up, the solution explorer is about an inch wide. It's like it can't remember it's layout settings.
Every un-docked window is in the position I place it. But if I dock a window, it's position is saved, but it's size will be reset to very-narrow (around an inch) when I load.
I've never come across this before and it's pretty annoying. Any ideas?
The things I've tried:
Saving, then reloading settings via Import/Export.
Resetting all environment settings via Import/Export.
Window -> Reset Window layout.
Comination of rebooting after changing the above.
Installed SP1. No improvement
none of which changed the behaviour of docked windows. (Also, definitely no other instances running..)
I do run two monitors, but I've had this setup on three different workstations and this is the first time I've come across it.
I had the same problem. It turned out that if the VS window was non-maximized, it was really
small. So after making the non-maximized wider, the problem disappeared.
I occasionally get this bug, and others related to layout/fonts/colouring etc. A little trick I've found is use the Tools -> Import and Export Settings, export your current settings once you've got everything setup as you like, then close and reopen Visual Studio and import. Hopefully that'll sort you out.
In 2005 there were some little bugs with viewing Project/Solution property panels when the Solution Explorer wasn't in its default position, docked on the left of the screen - I don't know if that's changed in VS2008, but you might want to put it back there and see.
Now, when are we going to get decent MultiMonitor support?!
Maybe you're closing Visual Studio while some other instance is still alive. The settings of the last instance that is closed is the one that will be applied.

Resources