I'm using Son of Obsidian color scheme and I've noticed every so often ReSharper Current Line Highlight goes back to the default color. To fix it all I have to do is go into Fonts and Colors and press ok and it goes back to normal. However it's really annoying when it happens and was wondering if anyone else is having this issue? Not sure if it's a VS or ReSharper bug.
I've had the same issue, I think I have narrowed it down to when I upgrade Resharper. Best way is to export your settings and then reimport them after upgrading.
Another thing that I have noticed is if you have two instances of VS open when you close the last instance it will override any changes you made in the previous instance.
Related
I've noticed that my VS15 forgets changes I make to the settings in options and check boxes under Tools on reboot.
For instance, when I exchange a string in a document, I get the pop-up telling my how many substitutions have been made. There's the check box showing/hiding this message next time. I uncheck it and fairly enough the pop-up doesn't come up again. Until I restart VS, that is. After that, the pop-up is back!
The same goes for many other options (typical NuGet packages' suggestion based on the contents of CSHTML-file, for instance). However, all the settings I make in Resharper menu are remembered. Also, the key short-cuts seem to be remembered.
I restarted, updated and reinstalled - no luck there. Starting VS in admin mode gives no change, neither. I noticed that if I change the values in the registry, the changes are effective in VS. It's like VS won't write the modified settings to the registry by itself (and I'm damn sure too chicken and too lazy to horse around in the registry for that).
Has anybody else experienced that?
What more can I do to diagnose it?
How do I kill the problem?
I've already done some searching on this, but to no avail, and it's driving me insane.
I use the dark theme in VS 2013, and I have a selection of add-ons installed that change how the text is displayed in some circumstances. The two that immediately spring to mind are ReSharper (v9) and VS Commands.
The issue I have is that whenever I go into the VS options, or even ReSharper options, I'm greeted with some dark text, and some light text, which actually makes using the options extraordinarily difficult, as shown here:
If anybody knows what's causing this, or how to fix it, I'll be eternally grateful. I've tried resetting the font colour settings, but nothing seems to be touching it. I don't particularly want to reset all of my VS settings, so I'm holding off on that in the hope that somebody can point me in the right direction.
Update (21 Aug 15):
I've noticed today that my ReSharper options appear to be correct when I open Visual Studio initially - not opening via a solution file. As soon as I open a solution, the colours change to how they are in the screenshot. It doesn't appear to matter what solution I open, but as soon as a solution is opened the problem presents itself again.
I like a dark background when coding and have customised it to a scheme that suits me. However each time I start VS some colours are wrong. To fix this I have to go to "Tools\Options\Fonts and Colours", click on "Display items" and click OK. This fixes it for that session but the next time I start up VS the colours are wrong again.
Clearly the colour scheme is remembered because I don't have to set them again, just having to go through the above process. Is there any way to fix this problem so that I get the correct colour scheme the first time I start VS?
The problem seems to have disappeared. I don't know exactly what did it. Our MSDN license came through and I reinstalled Expression Blend (which might have updated some files for VS and we also got a licensed version of Resharper (I had a trial one only till then and downloaded a slightly newer version after we got the license).
Using Beta 2 of Visual Studio 2010. I'm using C# and have always enabled Virtual Space. A notable difference in this version between past versions is that when I'm at the beginning of a line in the .cs file and I hit the left arrow, the cursor jumps to the line above. Previous versions of Visual Studio would perform no action (i.e. stay at the beginning of the line). I never realized how much I depended on that working as it did until now. Because when it jumps to the previous line, I hit the right arrow key, but being in virtual mode it keeps me on the same line.
I searched and searched for a setting that changes this behavior and compared my Visual Studio 2008 settings to 2010 and couldn't find the magic switch. Is this a setting and if so, what is it?
Thank you.
Looking at the implementation, it appears the current behavior is expected, but is likely not intentionally different than Orcas. It was probably just an oversight when virtual space was (re)implemented in the new editor.
If you want to track the progress of the fix, can you file a bug on Connect? I can file one internally, but you won't be publicly visible. Also, the bug will probably be "Won't Fixed" for Visual Studio 2010 RTM (it's too late to fix now), but the fix could make it into SP1. Please let me know if you don't file a Connect bug, in which case I will file an internal one.
Since VS2010 is still Beta, it may well be a bug. An option could be to export vs2008 settings and import them to vs2010 to ensure you have the correct settings (assuming you haven't changed anything specific to vs 2010).
Are you trying to disable Virtual Space in VS2010?
Virtual Space is enabled in Column Selection mode. When Virtual Space mode is not enabled, the insertion point moves from the end of one line directly to the first character of the next.
Steps here
As the others said, it could be a bug, or an annoying intentional change of behaviour.
But to add to this, I'd say that since VS2003 I have always re-evaluated my use of the IDE (and specifically the key bindings) every time I upgrade.
I find the standard VS behaviour an extremely useful way of getting to the end of the preceeding line. If I want to get to the beginning of the line, I press home (once to get to the start of the code, and again to get to the start of the line), so I never press left-arrow at the start of the line unless I intend to move to the end of the previous line. I would personally find it utterly irritating to press left arrow and have it not do anything - if I've pressed the key I expect it to do something useful.
Perhaps if you spend a few days trialling a new navigation approach, you will discover an easier, more efficient way of using the IDE. You just have to put up with a few days of minor frustration until you can reprogram your muscle-memory. From my point of view, it's always worth a try... (Indeed I've never found a change to a newer key binding set to be a problem at all, apart from the bookmark keys changing from a single keystroke to a double-keystroke. ANd that is easily fixed if necessary by just editing the key bindings)
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.