Resharper: Ctrl-Backspace deletes just one subword of a CamelCaseWord - visual-studio

When I have the text:
new ResharperFeature
And I press Ctrl-Backspace, I get:
new Resharper
And I want:
new
This issue exists only on my work PC. It must be misconfigured. What is the setting that I can change to get the "normal" behavior?
Note: I verified that this is a R# problem by suspending R#. The problem went away.

Go to ReSharper > Options > Environment > Editor, and deselect Use CamelHumps
Note that this will also affect Ctrl+W/Ctrl+Shift+W (Extend/Shrink Selection) and Ctrl+Left/Right

This is a known bug in Visual Studio 2010. https://connect.microsoft.com/VisualStudio/feedback/details/533093
Hope it will be fixed for VS 2012

Related

Visual Studio 2022: Resharper - IntelliCode AutoComplete disappearing when typing

When using the Resharper extension, I noticed that I can no longer use the IntelliCode auto complete suggestions as they disappear straight after a key press
Is it possible to use this feature in conjunction with Resharper?
Expected Outcome
Auto complete suggestion is visible after keypress
Actual Outcome
Auto complete suggestion disappears after keypress
Version
Visual Studio 17.3.0
The issue appears to be fixed with the release of Visual Studio 17.4.0.
I would recommend anyone having the same issue with versions < 17.4.0 to update by doing the following:
Visual Studio Menu Bar -> Help -> Check For Updates -> Update
Does pressing ctrl+J can show any suggestions?
You can try to disable extensions in Visual Studio. This might be the cause of the problem.
We've created a new issue in our bug tracker: https://youtrack.jetbrains.com/issue/RSRP-490187. Please comment or vote for it to monitor the status of this issue.

How to prevent enter key from making new line during resharper intellisense completion

I have a lot of experience as an Intellij developer where the enter key will always insert the first auto-complete suggestion. In visual studio with resharper however, the enter key will create a new line instead of inserting the first intellisense suggestion. Can anyone suggest a way to allow the enter key to replicate the Intellij behavior? I know pressing the tab key behaves as expected by my muscle memory keeps pressing enter without me thinking about it.
Can anyone suggest a way to allow the enter key to replicate the
Intellij behavior? I know pressing the tab key behaves as expected by
my muscle memory keeps pressing enter without me thinking about it.
In your side, you have installed Resharper, so you have two ways to use Intellisense: Visual Studio Intellisense which is the default way for Visual Studio, Resharper Intellisense.
1) If you use Visual Studio Intellisense(make sure you choose Visual Studio by the top menu ReSharper-->Options-->Environment-->Intellisense-->General) and face this issue, please try this:
choose Never add new line on enter by Tools-->Options-->Text Editor-->C#(please choose the corresponding development language)-->Intellisense-->Enter Key Behavior.
2) If you use Resharper Intellisense(make sure you choose Resharper by the top menu ReSharper-->Options-->Environment-->Intellisense-->General), you will not face this issue.
Note: if you face this issue in Resharper Intellisense, l think it is the issue about some changes in Resharper Option.You can try to reset Resharper settings by Resharper-->Manage Options-->Reset all settings.
Hope it could help you.
Just a quick update for the previously posted answer as I noticed the location has changed slightly as of now. I found this option (using Visual Studio Intellisense) under:
Tools menu > Text Editor > C/C++ (or whatever language you are using) > Advanced > IntelliSense section > set Member List Commit Aggressive to True.

Backspace doesn't work in Visual Studio

I keep getting a very annoying problem in Visual Studio. When I try to delete some text by pressing backspace it doesn't work. Why is this? What is going on? Sometimes I have to close and open Visual Studio to make this problem go away but I just tried that right now and it didn't work. Backspace works in Notepad in case you are wondering.
In Visual Studio go to:
Tools
Options
Environment
Keyboard
Find "Edit.DeleteBackwards" command.
In "Use new shortcut in:" dropdown select "Text Editor".
In "Press shortcut keys:" click backspace so it would show "Bkspce"
Click "OK".
Backspace should start working for you again.
This seems to happen to me when I open a solution and there are files already open. I used to close the files, then close and re-open the solution to fix it, but now I just hit Alt + Enter.
Here is the blog where I found this trick.
I solved this issue resetting keyboard mapping scheme.
Tools -> Options -> Environment -> Keyboard -> Reset.
A quick fix for me is to simply open any menu from the menu bar. Once the menu is closed the non-character keys start to work again.
Except for the above methods.
You should also check the shortcut key settings:
File -> Preferences -> Keyboard Shortcuts -> 'Then check the item: deleteLeft'.
I get this from time to time in VS2010 as well and simply just using the mouse to change tabs/files seems to always fix it now. Nothing more.
This method is working at 100%.
Go to "File-> Preferences -> Keyboard Shortcuts" and search for deleteLeft and add keybinding "Backspace".
Odd that this is still an issue even in VS 2019. Both the backspace and delete keys didn't work. Quick fix, I just ran the project and it seemed to give it the kick it needed.
All I did was exit visual studio and restart it.None of the above options worked for me.
In my case the problem was the "When" Condition in "File-> Preferences -> Keyboard Shortcuts".
I removed "textInputFocus && !editorReadonly" and it works now as expected.
I'm looking forward to the side effects ;).
Try resetting your Visual Studio Settings
Go to :
All Program > Visual Studio 20xx > Visual Studio Tools
Run Developer Command Prompt for VS20xx as Administrator and this command:
devenv.exe /resetsettings
A quick work-around for me is locking the pc (Windows+L) and logging in again.
You can reset keyboard mapping scheme like this
Options => Environment => Keyboard then select (Default) in the comboBox and click Reset button and then Ok button to confirm
Visual studio 2019 : Keyboard mapping sheme
Tested in Visual Studio 2019
This problem happened for me when I used a different version of resharper at home and then took that project to my employment. Backspace works for me now after I deleted the bin and obj and resharper directories.
I have this problem after I install Vim, uninstall Vim Backspace works fine.
When this issue has happened to me, I've found that hitting delete or backspace is unresponsive only within a portion of my code. This portion happened to be some code that I've pasted in from the internet somewhere.
To fix this issue, I cut out the recently pasted problematic code and then pasted it into a text editor like Notepad++. Then copying and pasting that same code out of the text editor and back into Visual Studio fixed the problem.
Using Visual Studio Community 2019 (16.4.3)
I just searched this issue because I could click in my document, type, et cetera, but I could not use backspace, delete, ctrl+z, or the arrow keys.
Opening the "File" menu, I noticed the Save option referred to a different file. I checked that file and found that all of the keys that seemed not to work were actually editing that other file.
Switching between the file in half-focus and the file I intended to edit worked and, luckily, undo was able to fix the file I unknowingly butchered.
If you wound up here, check your "File" menu to make sure the correct file is referenced, since the fix is quick and easy to try.
Just had this exact issue (along with 'Enter', 'Ctrl+X', 'Ctrl+C', 'Ctrl+V', 'Ctrl+Z' keyboard mappings seemingly doing nothing) in the latest VS preview version below:
Microsoft Visual Studio Professional 2022 (64-bit) - Preview
Version 17.2.0 Preview 6.0
The fix for me was to move to another tab (I had multiple open) use the backspace key which worked fine, then move back to the original tab with which it wasn't working, save the file (as it had outstanding changes) and then I found backspace and all other shortcuts then worked!
I can only think that VS got in a locked (to keyboard mappings) state for that particular tab.
A few notes on this:
I knew it wasn't a keyboard issue as I was able to use those
keys/mappings fine in other apps.
I found closing and reopening VS didn't work.
Also resetting the keyboard mappings (through Options menu as others have described) didn't work.
I had multiple tabs open.
Resharper was disabled.
I just had this happen in one instance of Visual Studio 2022, caused by the debug settings editor window being open in another instance of Visual Studio 2022 in the background where I couldn't see it.
Closing that window resolved it.
I've had this issue for a long time. I'm not sure what causes it, but Alt + Enter works.
The extensions that I'm running include AnkhSVN, MySQL Tools, and Productivity Power Tools.

F12 no longer works in Visual Studio

This is driving me crazy. Ever since I installed ReSharper 4, F12 no longer seems to work. If you look at the all the ReSharper short cuts in the Goto sub menu Declaration doesn't have any assigned!
The only way I can go to declaration is by using Alt and ` and then selecting Declaration.
I have tried un-installing and re-installing ReSharper with no luck, I have also, in ReSharper option asked it to use the default Visual Studio Key Bindings but that doesn't to work either.
Interestingly, when I do use Alt and ` I actually get two entries for the Declaration option.
Has anyone come across this problem?
I am using Visual Studio 2005 SP1.
I ran into the same issue and resolved it by first resetting my Visual Studio keyboard mappings:
Tools > Options > Keyboard > Reset
Then going into the ReSharper options and applying the scheme:
Resharper > Options > Visual Studio Integration > Apply Scheme
Update:
For VS2017 onwards:
Tools > Options > Environment > Keyboard > Reset
For Resharper 2017.2:
Resharper > Options > Environment > Keyboard & Menus > Keyboard Shortcuts > Apply Scheme
I have had a few occasions where Resharper and Visual Studio keybindings got mixed up and I had problems sorting them out.
If it is only one or two bindings you care about then you can change them by going to the
Tools->Customize->Keyboard menu option.
For ReSharper 8 and Visual Studio 2012:
Tools > Options > Keyboard > Reset
Then going into the ReSharper options and applying the scheme:
Resharper > Options > Environment > Keyboard & Menus > (Select Visual Studio under Keyboard Shortcuts) > Apply Scheme > Save
I had this problem and it was resolved by following the steps described in the picture:
Open Visual Studio Tabs on the path: Tools>>Options>>Keyboard
Open Visual Studio Tabs on the path: Resharper>>Options>>Keyboard & Menus and Do the following:
And Then Reopen the path above and do the following:
Finally, close the Visual Studio and open it.
I had this issue in VS2015 using Resharper 9.1.3, I tried Ryan's answer but it still didn't work.
After doing the steps Ryan outlined, I clicked F12 where Resharper asks What do you want to do?, I select Use Visual Studio commands. Still doesn't work.
Tools > Options > Keyboard > Select ReSharper.ReSharper_GotoNextHighlight from command list box
Change Shortcuts for selected command to F12 (Text Editor), click Remove and OK.
After this it works!
Try simple way to enable it, press Fn + Esc key of the keyboard.
It is possible that you have enabled Fn mode (Blue Keys) on your keyboard which overrides default behavior of functional keys including F12.
I had the same problem with VS2013 and Resharper 9. I have a code like this:
gridList.Method1();
gridList.Method2();
I then right-click on any of gridList and click Find Usages (or just use Shift+F12) but it says "Usages not found" even though it is just one line away! Sometimes VS restart would help, sometimes it wouldn't. It looks like clearing the cache of Reshaper helps though: Resharper -> Options -> Environment -> General -> Clear Caches. This needs VS to be restarted, but then it started working as expected.
My problem was that I couldn't use the command "Alt + F12" when trying to "peek definition" in Visual Studio. I found out through another forum-thread that it was Nvidia's GeForce Experience that overrides some of the "Alt" shortcuts and uses them for their functionalities with screen recordings etc.
What solved it for me, was going into the GeForce Experience settings and switch off the use of in-game overlay:
Alternatively, if you want to use the overlay, you can just change the short cut commands.
For ReSharper Ultimate 2017.3.3 and Visual Studio 2017:
Tools > Options > Tools > External Sources > Default Visual Studio Navigation > Save
I ran into this problem after an organizational change that caused my windows profile to change. I tried the solutions listed above, but nothing seemed to work.
Here is how I fixed it (brute force worked!)
NOTE: Steps listed are for VS 2012 and ReSharper 7.1.3
Uninstalled Re-Sharper
Exit visual studio, ensure the process devenv.exe is no longer there in the running processes (was there in my case and I had to do a "End Process Tree" from Task Manager)
Fired up VS 2012, and from the menu Tools -> Options -> Environment -> Keyboard selected Visual C# 2005 (or any other setting you love) and pressed Reset
Shutdown VS again (and ensure devenv.exe has been killed in Task manager)
Re-installed re-sharper
Best of luck!
These steps solved it for me:
Uninstall keyboard in Device Manager
Re-insert your keyboard usb
"Web Essentials"
Add or update visual studio "Web Essentials" You can find it at:
Menu>>Tools>>Extensions and Updates
I hope this will save your time. It worked for me.
ReSharper added a crap 'good' new thing that they now call a feature: Smart Go To Declaration. As dumb as it may sound, it comes enabled by default: crap 'good'.
The feature is described on the link provided from here but honestly at least it should've keep it disabled, not reinvent the wheel. It also tells you how to disable that crap 'good' feature.
Sometimes it has noting to do with Visual Studio at all. Be sure your keyboard has its function key setting of the keyboard itself to send the F12 function to Visual Studio. It is an easy thing to miss.
I had just installed Pulover’s Macro Creator and F12 was set as the global hotkey to pause a macro. It was intercepting the keypress before it had a chance to get to VS.
Solution is to change that hotkey to something else. I chose Ctrl-F12. The input box is on the top right of the Pulover window.
Update 2020. I had the same problem and also tried a lot of ways, but that was still didn't working... [VS 2015, ReSharper 2019.3.1]
But, like Andrius said:
Resharper -> Options -> Environment -> General -> Clear Caches. This needs VS to be restarted, but then it started working as expected.
Summary is: (try steps above) + Resharper..-> Clear Caches + VS restart. Hope this will be useful

Visual Studio Editor does not underline errors anymore

My Visual Studio (2008) Editor has stopped to underline Errors (this nifty wavy red lines). I can't really tell when, but it can be related to the installation of .Net Framework 3.5 SP 1 or the MVC Beta (which I guess is unlikely). Furthermore have I installed and uninstalled both CodeRush and Resharper for evaluation purposes (decided not to keep either one of them).
Does anyone know the problem and how to restore this functionality again?
Have you checked Tools→Options...→Text Editor→C#→Advanced→Underline errors in the editor?
I usually like to reset my settings after messing around with plugins, as they tend to mess with settings: Tools→Import and Export Settings...→Reset all settings.
About possible causes.
For VS 2012 and 2013 if you have more than one instance of Visual Studio on different machines binded to one "live" account and have installed ReSharper on one of them, it disables the native IntelliSense and error underlines (to replace by it's own rules) that will be synchronised through your account to another machine without ReSharper.
Found it in Visual Studio 2019 as: Tools > Options > Text Editor > General > Show error squiggles
This is generally called Disable Squiggly or Wavy lines in Visual Studio.
How you will do in Visual studio 2013?
TOOLS -> Options... -> Text Editor -> C/C++ -> Advanced -> Disable Squiggles: True/False (Under IntelliSense) -> Press OK
I know its an old question, and with various solutions, but I have fixed it in different way. I'm working with Unity3D on my C# code using VS2017, when suddenly VS decides to stop underlining error while im typing. However, if I close the file tab and reopen, it suddenly undelines the error.
For example:
class A {
public int x;
s;
}
should obvsiouly give an error for that lonely 's' symbol. But, VS doesn't underline it until I close and reopen this file tab.
Solution:
Copied the entire Unity Project folder (which is like a regular VS Solution folder basically) and worked with the new folder, which issue was gone there.
For visual studio 2017 act according to HeeJae's comments in:
https://developercommunity.visualstudio.com/content/problem/113112/design-time-error-checking-isnt-working.html
i.e:
Hi. you are probably hitting a known issue. can you try this?
1.Update to latest release If that doesn’t solve it
2.Go to Tools\Options\Projects and Solutions\General and uncheck “Allow parallel project initialization”.
3.Close VS.
4.Delete the “.vs” directory beside their solution file.
5.Reopen VS.
..
thank you
You can re-enable the "Allow parallel project initialization" option after the issue was solved.
I tried to upgrade VS, reset VS settings, clear VS cache and everything people do conventionally but none of them solved this issue! At the end the mentioned solution worked for me magically.
Good luck
Unloading and loading same project again from the solution does the trick. Just right click on the project and click "Unload Project". Once unloaded, again right click the same project and click "Reload Project". Error highlighting will return.
I had the same issue with 2017. There was a 'disable intelisense' option, make sure that is set to false.
For everyone wondering in 2021..
search for "C_Cpp.errorSquiggles" in the settings.
Make sure to have it active for the user, as well as the workspace.
No need to restart Visual Studio.
For me (VS 2019) , after trying the other answers also, setting the scope of analysis from "Current document" to Open document" brought back the missing error markers
Just go to settings and search for errors and Image in Error Squiggles. You can see the Error squiggles (Modified: Workspace - Right now you can't see it because I modified it). Just click on modified and you will see the disabled option. If by mistake you disabled it, just enable it and you can see the red line errors again in your code.
In latest edition, check for .vscode folder in same project folder. There will be a setting.json file in that. Delete the key value pair of "C_Cpp.errorSquiggles": "Disabled". Restart the vs code.

Resources