Recently, probably by some accidental key-combination stroke during furious development, my IntelliSense window has a small text input field above which is really annoying, because I can no longer just type and hit Enter to use the autocompletion feature.
How do I get rid of it?
The key combination you probably pressed was Ctrl + Alt + Space, which toggles the completion methods of intellisense.
Can be switched back to the other completion mode by going to:
Edit-> Intellisense -> Toggle Completion Mode.
this seems like a bug in VS, please see below
http://connect.microsoft.com/VisualStudio/feedback/details/587691/vs2010-bug-intellisense-shows-empty-text-field-and-stops-working-correctly
and this bug is closed as "Not Reproducable"...
did you try restarting the VS? propbably, that should fix your problem.
If yes, can you try restarting the machine?
Related
The indentation behaviour of Visual Studio 2022 version 17.4 has changed.
Has anyone figured out how to make it behave like it did in 17.3?
I have this typed:
Then I hit [enter], and I get
The cursor is now indented, as opposed to being under the 'f' like it used to in previous builds.
If the statement "foo" was a valid statement, then the cursor does not get indented.
Obviously, I could just write perfect code from top to bottom without ever typing an incomplete statement, but I'm just not that good :-/
It's worse than that. The option Text Editor->All languages->Tabs->Indenting (or Text Editor->any language->Tabs->Indenting for that matter), which is a radio between None, Block and Smart, is completely botched - in 17.4, no matter what you set there, you get the "smart" behavior. Way to go Micro%$#^.
Btw - upon seeing this, I made the mistake of my life - roll back Visual Studio to the previous version (using the Rollback button in the VS installer) - that fixed the Indenting behavior, but completely reset all of my Visual Studio settings, including colors, everything. Starting with a blank slate. Thank you, thank you, thank you MS.
After my testing, I reproduced your problem, this is a bug.
I suggest you post this to the dc forums and attach the relevant link to the question.
Either something has come undone in my brain overnight, or there has been a change to my instance of Visual Studio that I made by accident. I was running v17.3.1 and just updated to v17.3.4 to see if it would fix the issue, but it has not.
For the last few years of pushing out lines of sub-optimal code, I have gotten a space when I pressed the spacebar and a period when I push the period button. I use intellisense a great deal, to the point that when I want to log something, I type logger.in[tab] and I get logger.LogInformation written, waiting for me to type what I want logged.
This morning, my code was way worse than usual. I wasn't getting spaces or periods being typed to the screen. Initially, I thought it was my keyboard, but a quick test showed that my keyboard was fine. Then I noticed that when I would press either the period or spacebar buttons, the intellisense would complete the selection but not insert the space or the period.
Even trying to create a new variable is painful. Typing string[space]myString leaves me with stringmyString in the IDE.
Double tapping the space or period button feels really unnatural to me. Does anyone know what options I may have accidently changed, or how I can get it back to how it was working yesterday?
Thanks in advance.
EDIT: I thought I had fixed it with Edit -> Intellisense -> Switch between automatic and tab-only Intellisense completion, but then I had to double click on the autocomplete that I wanted for it to insert it.
You can open the visual studio installer and Repair the VS it will solve the problem.
This issue was caused by the Telerik extension, in my case "Progress Telerik UI for Blazor". This was reported to Telerik, who quickly published a new version.
The new version of the extension (2022.3.921.3) fixed this issue.
I have not (knowingly) created or reassigned any keyboard shortcuts, and thought that I should be at using only 'default' keyboard shortcuts. But when I attempt to type an uppercase 'E', the status bar displays,
"(Shift+E) was pressed. Waiting for the second key of the chord..."
. If I hit Esc as suggested in the question, How do you stop Visual Studio from waiting for the second part of a shortcut-combination?, the status bar displays,
"The key combination (Shift+E, Esc) is not a command."
No other key combinations have produced an alternative outcome. This issue only exists for E and only exists in Visual Studio. Shift+E isn't in any Default Keyboard Shortcut I saw on MSDN.
I installed the Intellicommand Extension as recommended in the Display Possible Chord Continuations in Visual Studio discussion, but no prompts are displayed when I type Shift+E.
Any suggestions for troubleshooting?
Go to Tools > Options > Environment/Keyboard dialog. Then put focus on the Press shortcut keys: textbox, do shift+E and see what comes up. Once you find where it is set just update it to something else.
I've just noticed this problem, removed the PowerShell Tools for Visual Studio extension, which I updated the other day and now Shift-E works again...
Just had this happen to me.
Can confirm its definitely caused by the PowerShell Tools for Visual Studio extension.
Pressing Shift+E in the Keyboard dialogue didn't bring up anything, however having read responses to this post about it possibly being related to the mentioned extension searched for PowerShell in the "Show commands containing:" box. It brings up a few, and the second one down for me "EditorContextMenus.CodeWindow.PowerShell.ExecuteAsAScript" had Shift+E, F5. I removed this shortcut and now Shift+E is working fine.
Visual Studio's behaving like you have something bound to Shift-E, _.
Since you say you haven't set up any keybindings, have you tried following MSDN's instructions on resetting your environment?
I got the same problem, but manage to get rid of it.
Most probable cause for me was extension "PowerShell Tools for Visual Studio".
Additionaly, I've disabled keyboard shortcuts synchronization in Tools>Options>Synchronized Settings and restored default keyboard mapping scheme as well.
Hope that helps!
I am using Visual Studio and Resharper 8.
For some reasons, my favorite shortcut Ctrl+K, Ctrl+C or Ctrl+D no longer works.
Indeed, the application shows in the status bar the message: The key combination is(Ctrl K Ctrl C ) is not a command.
Any ideas how to reset them?
Many thanks.
Very strange problem. Yes, it is possible to edit the command in Visual Studio. Select Tools and then Options. Once the window is shown, select the Environment option group and then Keyboard, as shown in the picture below:
There, you can edit the shortcuts:
Edit.CommentSelection for commenting a selection (Default shortcut: Ctrl+K, Ctrl+C)
Edit.FormatDocument to format the document (Default shortcut: Ctrl+K, Ctrl+D)
I have had this issue off and on myself in different versions of VS (now VS 2017). I just figured out that it is a combination of two keys to comment and uncomment code in VS.
To comment code: Press Ctrl+K, then also press C while still holding the Ctrl key.
To uncomment code: Press Ctrl+K, then also press U while still holding the Ctrl key.
You can release the Ctrl key after pressing K, then press Ctrl+C (or Ctrl+U to uncomment), but is just easier to press the keys in succession.
I had never noticed the status bar at the bottom of the window stating it was waiting on the second key press (C or U).
Sorry to resurrect a old thread like this but I have had issues with chording since this whole WFH/Covid-19 thing started. When it first happened the only thing that worked was to reinstall VS 2019. It happened again and this time I reset the keyboard setting back to default and it fixed it with out having to reinstall VS2019. It happened again today. Resetting keyboard settings didn't work and I was not in the mood to re-install so I was living with it for a while. It was after I took a lunch break that I noticed that a light on the top right of my keyboard, which is usually on, was off. It's the light for scroll lock. I hit the scroll lock key, the light came back on my keyboard and suddenly all my short cuts were back.
May not be the answer for everyone but if it's intermittent like mine was, it may be this ridiculous key that I have apparently never hit at work...
Visual Studio 2019 here, not using Resharper - CTRL + K, CTRL + C "stopped working".
In my case, the solution was simple.
While editing your files, make sure that you are in the Solution View, not the Folder View.
I also has this issue and found this post, but then realised that ctrl-K wasn't working if code already has a comment within it, Not this is specifically when trying to make a comment in a razor view where there are html comment <!-- --> within the code that needs commenting. This is odd and the first time I have encounter this since the first version of VS.
The solution here is to delete or uncomment that code first.
Faced this issue with Resharper enabled just a few minutes ago in VS2019.
All I had to do was to reset the mappings. No restart required. (Warning : that will reset all your manually added mappings to its default values)
Tools --> Options
Had the same problem with Format.
Follow the directions in the previous post - if Ctrl+K already appears under Edit.FormatDocument, click on Remove and then define it again as Ctrl+K. A warning will come up saying command Ctrl+K was used to clear bookmarks. This may be the root cause, as Ctrl+K is defined in multiple places by default. Once I redefined it, it worked properly.
Select Tools and then Options.Then select the Environment > Keyboard.
In the Keyboard section click Reset.
'Ctrl+K' following with C for comment and U for uncomment while holding Ctrl works. However to simplify and unify the keyboard shortcut to what you are used to you can just change the mapping scheme to something else like VSCode:
'Tools>Options>Environment>Keyboard'
Be sure that you saved the file with .py extension. Otherwise, the software does not perceive the code as command lines and thus does not transfer the lines to comments
All of a sudden, my intellisense window in VS2010 Express has a input field which has exactly what I'm typing. This wouldn't bother me, except that now space doesn't commit the selected choice that intellisense gives me.
Also note that the option in Tools-Options-Text Editor-C#-IntelliSense does have the "Comitted by pressing the spacebar" checked, yet it doesn't work.
Looks like you've messed with completion mode at some point. This can be changed by going to Edit -> IntelliSense -> Toggle Completion Mode or by just hitting Ctrl + Alt + Space
Microsoft finally fixed it.
It looks like the state of completion mode (toggled by Ctrl-Alt-Space) is finally persisted and applied to new windows.
Set it the way you like it. Close and reopen. Start new windows. It should stick to all of them.
Version: SP1 for Microsoft SQL Server Management Studio 2014