Maybe someone know how I could change this highlight effect in 'Output Window' of Visual Studio 2015
Here is example:
P.S. I have VSColorOutput extension installed but I checked twice that it does not set any background color.
This is, in fact, a problem related to VSColorOutput and, according to the VSColorOutput's author, it's caused by a bug in Visual Studio.
You can see the whole conversation regarding this issue here: https://github.com/mike-ward/VSColorOutput/issues/4
In the meanwhile, you can try the workaround they propose there:
Go to Tools --> Options --> Environment --> Fonts and Colors
Show settings for:Output Window
Set Item background to Black (not Default or Automatic)
It worked for me after I restarted Visual Studio.
Related
Firstly, I've been using Visual Studio Code and Visual Studio 2017 for C# code. In VS Code, it's much easier to get themes as you can just download them but for VS 2017, you have to go through this behemoth and set change each one separately. Fonts and Colors
I want to make my VS 2017 as close to VS Code as possible. Currently my VS Code has the Monokai Pro theme installed. I'd like to know which items to change from VS 2017 in order to achieve the same colors as VS Code. Here are example pictures, basically I want the bottom image to look like the top one.
Example VS Code
Example VS 2017
Sorry if I said something wrong I'm new to stackoverflow and I've looked a lot but couldn't find an answer or guide
There has got to be a better way! There is a better way, use the Visual Studio Color Theme Editor.
This theme looks to be close or you could at least import and use as a starting point:
https://studiostyl.es/schemes/litle-monokai-vstudio
Does anyone know why every time I save changes to a file within Visual Studio 2017 it changes my file icon (see screenshot below)?
I'm not sure if this is the result of an extension I've installed or was rolled out within an update to Visual Studio.
I would really like to disable this, any help is appreciated.
UPDATE 1
This doesn't seem to be related to Git integration as the icons still change with source control features disabled (see screenshot below).
This seems to be a known issue for .NET Core solutions within Visual Studio 2017.
The developer community has already reported this issue, see Solution Shows Missing File Icon, which is currently "Under Investigation".
Updated August 30, 2017
The fix for this known issue is now currently marked as "Fixed - Pending Release".
Updated September 15, 2017
This issue has been fixed and is included within version 15.4 which is included in Visual Studio 2017 Preview. Downloaded and confirmed this is not longer an issue with the preview edition.
If you made sure VS didn't throw any error, warning or info exception in its Error List regarding the modified file, it most likely is related to the Git integration this Visual Studio edition came with. It works like a file version controller software, showing visual icons like this one to show if the files were commited and if they were, if they are new or not and altered or not.
To disable source code control, go to Tools, Options, Source Code Control and select None. If nothing changes instantly, I recommend restarting VS and checking again.
I've installed Visual Studio 2017, and when I opened VS 2013, and attempted to do a code compare, it looks like this:
What am I doing wrong? Are there settings that I can update to make the colors more reader-friendly?
Same problem on Visual Studio 2017 !
I found a fix, that might also help on VS2013 : Tools -> Options -> Environment -> Fonts and Colors. Select Text Editor in the "Show settings for" dropdown, and look for an item relative to CodeCompare (in my case that was Code Compare Symbol Difference). You can set a more appropriate foreground and background color here.
I would like to continue running Visual Studio 2010 on a new Windows 10 PC, in order to maintain some older projects, which I'm not ready to bring across to VS2015 yet.
However, on windows 10, I find that all of the drop down menus (and right-click context menus) stop appearing after running after a debug session. The only way to get them back again is to exit visual studio and re-launch it.
When clicking any of the File/Edit/etc menus in the top bar, the item will appear highlighted, but the menu that should appear below is completely invisible. Note this is not the same issue that is talked about at https://connect.microsoft.com/VisualStudio/feedback/details/653315/ui-gets-messed-up (which seems to be garbled menus) - mine are not there at all.
I've followed the advice there anyway, to disable hardware acceleration in the VS GUI, but I'm still having the same problem.
Any suggestions?
ADDITIONAL INFO (Edit):
I should add that the PC (laptop) in question is a Thinkpad Yoga 460 with an NVidia GeForce 940M display adapter with switchable graphics (Intel HD Graphics 520).
I have tried using the NVidia control panel to force VS2010 to use the intel graphics, and I have also tried the reverse (forcing it to use the NVidia). The problem still occurs either way.
The menus stop working as soon as a debug session is entered (rather than on return from debug)
In the end, it seems one of my visual studio settings had caused the problem with the invisible/missing drop down menus.
I had imported all visual studio settings from my previous machine (using the Tools --> import/export settings option).
Resetting all Visual studio settings to defaults fixed the menus. I found that re-importing my settings, except for the "options" branch maintained the working menus.
I could dig further and try to figure out which specific setting from the "options" branch is causing the problem, but I'm leaving it here: I've got coding to do! :)
The refactoring menu isn't showing up for me in Visual Studio 2012 RC. It's not showing in the menu bar or in the context sensitive help. Is there a setting I need to change to make it appear. I see the refactor menu in the customize option but can't make it show up in the menu bar. This is in a c# project.
I had this happen to me just now. Turned out I was editing a file that wasn't part of the open solution -- it was from another branch. Confused the heck out of me until I realized that.
I had a similar instance. Turns out, the project I was working on doesn't always have some of the files set to compile. In this case, it was an ASMX file, and none of the refactor bits worked.