When I try to check changes using team explorer on visual studio 2019, if I open any file to check differences I cannot see horizontal scrollbar.
Is there any config I have to modify?
I answer myself:
The scrollbar is there, but it's only visible when the width is large enough. The tick and the "No problems found" message let too litle space for the scrollbar.
BTW, at first glance I feel like this version GUI of VS is worse than previous version. Just an opinion.
Related
I don't know why but Microsoft decided to make the title bars of the windows of Visual Studio 2013 and Office applications huge! They are so thicker than normal windows and this is really annoying especially if you have a small screen.
Do you think there is a way to change this?
There is an extension for Visual Commander to hide Visual Studio 2013 title bar. In the HideTitleBar function instead of setting visibility to collapsed you can try to change height.
I don't think you can change the size of the title bar. The best you can do is to auto-hide it, that way you see the ribbon only when you need it.
There is an extension of Visual Studio https://visualstudiogallery.msdn.microsoft.com/4bb76b8a-cef1-4223-8f9c-8e815e50e56c for download.
It can change the title bar smaller instead of hiding it. Because if you hide it, you loose the control to move the window around or minimize it.
I am having an issue within the razor view in Visual Studio 2012. For some reason, most of the time when I am trying to edit a style property, my keyboard freezes and doesn't allow me to type anything.
<section style="height: 15[Try to edit here]">
For instance, trying to add in a zero or 'px' where the "Try to edit here" has been placed above is impossible as the keyboard freezes.
I have ReSharper 7.1 installed, I'm not sure if that is the culprit?
Closing the tab and re-opening it fixes the issue, but it then re-occurs later on (not sure if there is a pattern as to when it re-occurs)
This happens to me often. I just switch tabs and come back and it doesn't happen(for sometime of course :-)). It could be some kind of unresolvable bug although i would suggest that you uninstall ReSharper and try again to see if it gets fixed.
It happens to me and my other colleagues as well.
I have found it to be linked to having a floating code window(s). Unlike the floating window for something like Find Results (without a title bar), these appear almost like another instance of Visual Studio. These do not come to the front when the main Visual Studio Window is selected. I have found the keyboard stops responding only on these windows if there is a Find Results kind of floating window open. When the problem occurs, clicking on another VS window and come back sorts it.
In earlier versions of VS, any pulled code windows appeared without a thick title bar and window controls box.
I tried posting images of the two kinds of floating windows but don't have enough reputation to do so! Let me know if it is confusing and I'll try to clarify.
This may not be the only way for this problem to occur but this is what I've observed consistently in the last few weeks of using Visual Studio 2012. I have C# environment settings with Resharper 7 and Reflector installed.
It's basically in the title.
Whenever you "select all" in the Visual Studio code editor, the editor will scroll down to the bottom of the file. Is there a way to prevent this?
I'm using Visual Studio 2008 at the moment, but this applies to all versions.
No, you cannot change this behavior.
Microsoft has been aware of this since at least VS 2010, but either doesn't think it's a bug or doesn't think it's important enough to fix.
From their response to a 2010 bug report filed on the issue:
We unfortunately do not plan to change Ctrl+A's scrolling at this
time, so we're unfortunately resolving this issue as Won't Fix for VS
2010. However, it will remain in our database to be revisited for a future release of Visual Studio.
Source: Microsoft Connect
A quick Ctrl-Z-Ctrl-Y will get you back to where you were. If you tend to do a Ctrl-S Ctrl-A Ctrl-C a lot then just get used to this whole chain instead: Ctrl-SACZY. Or, create a macro: https://msdn.microsoft.com/en-us/library/a0003t62%28v=vs.90%29.aspx
I was struggling with this myself, but the "undo" suggestion gave me an idea and I feel kinda dumb for not thinking of it earlier. Visual Studio includes "Navigate Backwards" and "Navigate Forwards" buttons (CTRL-, and CTRL+, respectively). So after you finish selecting and copying, simple click the navigate backwards button or type CTRL- and voilà! you're back where you were.
I know it doesn't stop the scroll to begin with, but at least it puts your cursor back exactly where you left it!
At Visual Studio 2010, there will be a red dot(s) on scroll bar indicated where your code has errors. Also a other color dots for other message etc.
But after installed Visual Studio 2012, I cannot see this feature anywhere, tried toolbar-options, nowhere to found.
Am I miss something? Or Microsoft just removed this feature.
{EDIT}
Sample of Visual Studio 2010
And Visual Studio 2012, where these nice little dot candy go?
The dots you see on the scrollbar are definitely a feature of the "Productivity Power Tools" Extensions "Enhanced Scrollbar".
Link
There are 3 Modes to enhance the Scrollbar, your Screenshot displays the first (default) one.
Unfortunately, there seems to be no equivalent for VS2012. Or does anyone know of an extension that improves the scrollbar like that?
Is it possible you were using the jetbrains resharper tool? That provides the feature you describe, but I don't recall ever seeing it in visual studio
Have you got code errors? :P
Check the editor settings out, I am pretty sure it is there it might just be off by default.
As you add code and build your solution, you may see different-colored wavy underlines (known as squiggles) appearing in your code. These marks notify you of problems Visual Studio has detected in your code. For example, red squiggles denote syntax errors, blue squiggles denote compiler errors, green squiggles denote warnings, and purple squiggles denote other types of error. For example, they are used for "rude" edits in Visual Basic, which are changes that are made during Edit and Continue and that will result in compiler errors.
You can see the default color for each error and warning squiggle in the Tools/Options/Environment/Fonts and Colors dialog box. Look for Syntax Error, Compiler Error, Warning, and Other Error.
From here: http://msdn.microsoft.com/en-us/library/efc4xwkb%28v=vs.110%29.aspx
Picture says it all, it should currently be showing a file but as you can see its having issues drawing the content of the file.
I have unloaded all addons and restart visual studio.
If it mathers the previus project was a VS 2k8.
New Info:
If i wait a good 5min ( I have a Quad core I7 with 6gb ram, 295gtx. VS is running from a SSD).
It will load the text, but im unable to "edit", as it will have loaded some document (.cs ) but when i select the one i want to edit it not realy open that file.
It can best be described as visual studio having a 5min lag.
I had this precise bug. I would open files from the solution explorer but the editor window would either not appear, only 1-2 lines of 100+ line files would display, or the file would display but I could not scroll or otherwise edit the file. Some parts of VS were working, i.e. little tooltips would appear if I moused over the right part of the (invisible) text but I obviously couldn't do much in this state.
I have a lot of VS stuff installed so I thought it was some sort of plugin or extension that was causing things to go screwy. These installed items include:
Visual Studio 2010 10.0.30319.1
ReSharper 5.1.3000.12 (JetBrains)
DevExpress DXCore 10.1.5 (free community edition)
DX Source Outliner (reason for DXCore, from sbohlen)
Tabs Studio 2.0.6 (www.tabsstudio.com)
Productivity Power Tools 10.0.11019.3 (Microsoft)
Snippet Designer 1.3.0 (Matt Manela)
I solved it (2/18/2011) by Tools... Extension Manager... disabling the Productivity Power Tools and Snippet Designer. No idea what was going on but this fixed it for me and I was back to work. Probably something in the system drawing and/or display options.
EDIT
The issue continues. Unfortunately it is intermittent and I have not be able to reproduce it reliably. Now the suspects are the BugShooting and CaptureWiz screen capture tools. I've had the behavior show up and then disappear in and around the time of logging bugs with them.
2nd EDIT
The issue continually continues. I have not yet been able to determine the cause but usually quitting VS and restarting resolves the issue(s). Other parts of the behavior includes the menu options (File, Edit, View, etc.) not operating properly as they show only the highlight but not the actual menu items. The solution will build and run just fine, but things still won't show up properly.
I had a similar issue whereby VS2012 was telling me that I had active (open) files, but the text editor was not displaying them. Clicking on the file(s) in the solution explorer seemingly did nothing. Alt + Tab just cycled through the open files, but still, nothing rendered on screen.
I solved it by clicking on the "WINDOW" menu item and then"Close All Documents". Visual Studio then behaved as expected and opened (and rendered) the files correctly.
This bug was created by mumble 1.2.x, but is fixed in the snapshot versions of 1.3.x. YOu can likely get simular bugs by other software that does DirectX overlay.
I had the same issue in Visual Studio 2012. It was fixed by running a repair of Visual Studio 2012 via Add/ Remove Programs.
The following had no effect:
Closing and reopening a solution
Opening different file types
Restarting Visual Studio
Adding and removing plugins
Resetting options via the 'Reset all Settings' option in Visual Studio's 'Import and Export Settings'
Rebooting windows
I had this problem in Visual Studio 2013. Problem was: extension "Regex Tester". I had to uninstall this extension.