Whenever I save code while using Visual Studio 2005, an MS-DOS window fills the screen (very) briefly several times. I suspect it is something to do with IntelliSense. This has happened for several months now, and I don't know what initially caused it to start behaving the way it has. It is quite annoying, so I was wondering if anyone else has experienced this problem; and if so, what they did to resolve it?
Update: having pressed Alt+Enter while it was running, I got a glimpse of the program name: it's the VBC (Visual Basic Compiler). Any ideas on how to make this not fill the screen?
Since solved here: https://superuser.com/questions/239049/how-to-stop-command-line-program-from-running-in-full-screen-mode. Definitely worth knowing!
Related
I am using Visual Studio Community and Visual GDB to code and debug STM32 projects.
The problem:
When I type something that is known to Intellisense, (path, variable or anything really), the suggestions come up briefly and then immediately disappear therafter. For that split second I can see that Intellisense has the correct suggestions, but TAB or ENTER does not work since the suggestions disappear very quickly.
Does anyone know how to fix this?
Thank you
You might try to disable any extensions in Visual Studio.
I had the same problem, surfed around and read in some places that disabling extensions would work.
So I disabled them one by one and the problem was gone.
Since some days Visual Studio is stealing the focus. The weird thing is, this happens when using other applications in Windows (such as Chrome) but also when working in Visual Studio (such as typing).
My considerations so far:
It only happens when VS is running.
Happens in VS 2012 Premium and in VS 2012 Professional.
Also happens in Safe Mode.
Tried reinstalling. No success.
Uninstalled 3rd-party extensions. No success.
The focus goes to "nowhere" - I don't see any application or window having the focus. Also a [Windows]+[Array up] does not maximize anything.
[Alt]+[Space] has no effect.
[Alt]+[F4] has no effect.
I'm running Windows 8.1.
Does anyone have an idea what the cause is, or what I can do to further analyze it?
It seems I found the cause by disabling background tasks step-by-step. The focus stealing was gone when I killed the QuickSet application on my Dell XPS 13. I also read on Dell forums that others were having similar problems with focus stealing. The strange thing is, that it only happened when VS was running.
But anyway, as VS is more important to me I decided to split up with QuickSet. :'-(
Many times a day, on a new work computer, Visual Studio's code window turns red and blue all of a sudden! The problem only goes away if I restart that instance of Visual Studio or re-apply the fonts & colors settings, closing and opening a file/tab doesn't help.
Only the currently visible file gets the glitch at first when it happens, other open tabs generally retain their proper colors until I reopen them or I open new files - which are then shown with the glitched colors. Sometimes certain types of text in other open files turns blue though, like a virus spreading ;)
I'm guessing there's a plugin or a missing hotfix or glitchy graphics driver but I haven't figured out what the problem is yet and it's driving me nuts.
I've had this problem once before but don't recall how I fixed it, it's been a while since then and I have many similar installations since that's not showing this issue.
There's also a Microsoft Connect issue on it that is closed with status "cannot reproduce" - and it's easy for me to reproduce by simply launching IE9. Sometimes, however, the problem appears without me launching IE.
Visual Studio 2010 SP1 on Windows 7 SP1, ReSharper 6.1 and Reflector 7.5.4.20. I've disabled hardware acceleration in VS with no difference, it's an Nvidia Geforce 210 with a dual screen setup with primary screen on the right. Also, the markup shown is not written by me and contains no sensitive information
This seems to be a small hiccup with the dark theme in Visual Studio. It happened to me when I did a system resume with the VS project still open. The solution to this is just restarting Visual Studio. Works like a charm.
It seems it actually helped to update Nvidias graphics driver, even though it was just a few months old and for quite an old and trusted graphics card. Oh well - now I'm happy that the problem is gone, and upset that it was so easy.
Found this be searching for an answer to the same issue.
They way I fix it is to open Tools -> Options and then click on Environment -> Fonts & Colors to reset the coloring for the current buffer.
It appears to be VS is not recoloring the current buffer after locking the screen for at least 4 mins. I believe this to be a bug in the themes handling in VS, but I this is really the only place I could find this mentioned.
Just installed SP1 for VS 2010 hoping that it will help, but it does not.
I faced the same issue with vs2013...
This solved the issue..http://madskristensen.net/post/visual-studio-update-2-and-web-essentials
I have been having an issue with Visual Studio 2010 that is driving me completely bonkers. The general problem is that Visual Studio 2010 does not seem to be remembering my window positions. (Visual Studio 2010, v.10.0.40219.1 SP1Rel on Windows XP SP3.)
Now, I am aware that Visual Studio 2010 has different window layouts for Build and Design mode. I have come to accept this as there are some things in life I cannot change. If I could turn off this feature, I would be over-joyed, but I do not think it is possible.
My biggest issue at this point is that Visual Studio 2010 doesn't remember the window positions in Design mode after going into Build mode and returning to Design mode.
Here are some screenshots to illustrate this issue:
Imagine me coding. OK, time to build.
OK, the window layouts changed. This is annoying, but whatever. Let's go back to design mode.
This looks OK, but WAIT -- why don't the windows return to their previous position?
I'm using a small Visual Studio window size here, but as the red box shows -- there is a difference. Why does this happen and what can I do to fix this issue? It is driving the OCD in me completely nuts. It doesn't look like a big change in these screen shots, but when I have my VS instance maximized across my two monitors (configured to display as one continuous desktop, instead of two desktops) -- it's a very noticeable and annoying change.
Possible problems that I thought were causing this issue:
I store my working copy in a Dropbox folder. I work from that dropbox folder. However, I've tried this same issue with Dropbox turned off and reproduced the above issue.
Corrupted settings file. I tried this with a new MVC application, saved it outside of the Dropbox, and the same thing happened.
Windows XP issue. I know I need to upgrade, but unfortunately that is not always an option. If Windows 7 doesn't have this issue, I will gladly upgrade.
#Shtong has answered below that I should use a dual monitor setup with different desktop configurations and install Visual Studio Productivity Power Tools. While this will technically fix the problem (I can now have two sets of mixed tabs and the sizes do not change) - the docking positions are forgotten instead. This means that if I dock the Solution Explorer to the right in design mode, then build, then go back to design mode -- my docked window is no longer docked.
I've also had this same problem in Visual Studio 2008.
Did you try installing the Visual Studio Productivity Power Tools that lets you split your editors into different windows, making two windows and attaching each to one monitor (instead of having one stretched over the two monitors) ? That way each window should fit into its monitor like every other window and your problem should disappear.
I have been a fan of the new "Navigate To" feature that was released with Visual Studio 2010 since I saw Scott Hanselman using it in one of his presentation.
For some unknown reason, it randomly stops working.
I hit "Ctrl + ,", type what I am looking for and then nothing happens.
It seems to wait for something and the window shows no progression in the research.
The only way I found to fix this is to restart Visual Studio and wait for the problem to happen again.
Does anyone have any idea why Visual Studio is behaving like this and how I can fix this?
I got this working by simply selecting an item from the Search Items dropdown. Once you do that, the search starts working again as expected.
I got this working again by uninstalling ReShaper. It fixed some other things like the solution wide search aswell. I'm not so happy about the solution though...
Any chance you're using resharper, powercommands, or productivity power tools?
I suspect the issue is related to one of those (I have the same issue), but since it's difficult to reproduce, it's hard to test that.