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.
Related
When I run my project in Xcode a few things happen (especially if there was an exception)
The debug (output) window slides up into view
The file directory pane on the left switches to the Debug navigator
The code file you left off on switches to main.m or some other file where the error happened.
That's all great, but when I'm done running the application none of this goes back to how it was. So that means there's this constant repetition of hiding the output window, clicking on the file directory icon, and finding the file I was just on.
This is just completely unacceptable as I may run the application a dozen times in a minute.
Coming from Visual Studio, the same experience happens when debugging, but everything returns back to normal when you stop debugging.
How can I make things return back to normal?
Assuming you're using Xcode 4 or later, you can set up behaviors to set up things how you want. Under the Xcode Preferences, click on the Behaviors tab and select "Completes" under the "Running" section. You have the option to open or close any of the various panes.
Here's an interesting article on customizing Xcode to make it work better for you.
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")
My computer crashed while I had VS2010 open, and when I recovered (all I did was reset the computer) and opened visual studio again, all my layout was messed up. Since I had very little customization done, I figured I would just reset the window layout. I tried Window > Reset Window Layout, but that didn't work. I even tried resetting the environment. How can I get back the default layout that I had right after installing?
Specifically, the changes I notice right away are the Solution explorer/etc. group of windows being on the right instead of the left, and the error reporting/output/code definition windows missing from the bottom. I know that I can just fix these things myself, but I don't know what else I am not noticing that has changed, and therefore would like to see everything reset automatically.
I found this which worked: Visual studio forgets window settings and makes a mess
Using VS2008 visual designer occasionally the designer seems to stop recognising changes. Normally you get a * next to the filename in the tabs when a change is made but sometimes this stops appearing when I am making changes. When this happens may changes are getting "lost" so if I close/reopen the file all my changes are gone.
Has anyone else encountered this and know why it happens and if there's a fix/workaround?
Cheers.
We ran into a similar problem in Visual Studio 2010. When attempting to resize a user control, the designer simply refused to recognize that a change was made (no * shown), and when you rebuilt, all source file changes were lost.
I found this link from another person having the same problem.
After stepping back through source control and comparing the .designer.cs file for the user control and its child controls, it turned out to be the same problem. At some point, the line:
this.components = new System.ComponentModel.Container();
disappeared from the designer file of one of the child controls (not the user control that I was having problems with). Incidentally, within that designer file, all of the references to "this.components" were also removed.
After fixing the child control (restoring the creation of this.components, and fixing the original references), the top level user control then started recognizing changes again.
We're not sure what caused the corruption of the child control. Perhaps it was a source code merge or a designer bug.
It's a very difficult problem to debug. Even if you attach a debugger to debug the design time behavior of the user control (and its children), there are no exceptions thrown and there is no indication that anything is wrong.
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.