Visual Studio 2010 RC Intellisense doesn´t work - c#

I installed VS2010 on my Windows 7 x64...
The patch to fix Intellisense as well (http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=26662)...
But my C# Intellisense doesn´t work... It doesn´t crash, but nothing happens when I typing... Just if I press a Ctrl+Backspace it appears...
In my Javascript file the Intellisense is working fine...
Any idea?
Thanks

EDIT: These are the options that should be enabled:
Tools->Options->Text Editor->C#->General->Auto list members
Tools->Options->Text Editor->C#->General->Parameter information
Tools->Options->Text Editor->C#->Intellisense->Show completion list after a character is typed
See my response to VS2010 RC - Is intellisense broken? How do I turn it on?:
Did you have ReSharper installed with Visual Studio 2008? ReSharper (in VS2008) turns off Intellisense explicitly in order to replace it with their own.
If this is the case, you can turn it back on with the options under Tools->Options->Text Editor->[language] (and sometimes also under the Intellisense node under each language).
For example, for C#, the first checkbox under Tools->Options->Text Editor->C#->Intellisense is "Show completion list after a character is typed". Make sure that is checked.

Scott Gu posted an entry about Intellisence crashing with VS2010 RC1. And later about a patch. This may be causing your problem. If not try Noah's suggestion.

Related

Visual Studio 2022 not showing syntax errors and Intellisense is not working properly

Working on a project I made a class with properties and when I tried to auto-generate a class constructor I got an error saying something on lines of "auto generation of class constructor failed... and will be disabled" and ever sense then the "generate constructor" option has been taken off the Refactor menu and on top of that I don't get syntax error highlighting anymore and intellisense doesn't seem to be working proper or at all.
I tried using going into Tools > Options > Text Editor > various fields including "C#" and "general") and I don't see anything obviously wrong. I also tried to use Visual Studio Installer to try to repair and that didn't do anything. I am completely out of ideas and I can't find anything that is remotely close to my case. TIA
I can't add this reply as a comment as I don't have 50 reputation.
I created a .Net 6.0 C# console project in Visual Studio 2022, add a class, and add two private fields. Selecting these two fields, press Alt+Enter to quickly generate the constructor. I did not encounter your issue.
Please try:
Go to Visual Studio Installer, click Modify, uncheck IntelliCode in Individual components, then click Modify button to save the change, wait for the installation to complete, and then reinstall IntelliCode.
In Visual Studio, go to Tools->Options->IntelliCode to check if the setting is Default.
Go to Tools menu, and select Options. Under Intellicode select General. Just uncheck “C# Suggestions”. Then restart Visual Studio and check that intellisence and syntax errors are appearing.
Note, I was not able to figure out what this option does, as the C# code suggestions seemed to continue to work as expected.

Crtl+Shift+Space shortcut in Visual Studio 2015

I started use Visual Studio 2015. In prev version I use Ctrl+Shift+Space shortcut to display Parameter Info, but in current version it not working.
How can I restore it, what is name for this shortcut in keyboardconfiguration?
I had the same issue, got it working by doing this:
Go to Tools > Options > Text Editor > All Languages > General, Statement Completion check Parameter Information (like most of the options in the General dialog, it was a full black box by default).
Ref:
https://msdn.microsoft.com/en-us/library/vstudio/ecfczya1(v=vs.100).aspx
It is called Parameter Info, or as it appears in the list: Edit.ParameterInfo
The default shortcut is: Ctrl+K, P
So give that a try. It also binds to Ctrl+Shift+Space in VS 2012/13 as you have mentioned.
It is supposedly supported in VS 2015 too so not sure why it isn't working for you - I seem to recall reading something on SO the other day that was causing shortcut problems, I think it was something to do with keyboard language settings, but I can't seem to find a reference at the moment so don't quote me on that!
For a full list of shortcut keys, see these references: VS 2013, VS 2015
You can search for example "Space" and it's not hard to find the one you wanted.

ReSharper 7 autocomplete incorrectly displays "No suggestions" after typing "this."

I'm using Visual Studio 2010 SP 1 w/ .NET 4.0 and I just upgraded to ReSharper 7. Since upgrading, when I type "this.", Resharper autocomplete always displays "No suggestions" as shown in this screenshot:
If I type ctrl+space at this point, it will come up with suggestions. I can also get suggestions if I hit escape (exit autocomplete) and then delete and re-type the dot. Either way, functioning autocomplete looks like this:
I'd really, really like autocomplete to work automatically as soon as I type "this."; can you help?
I've tried suspending and unsuspending ReSharper, restarting Visual Studio, restarting Visual Studio with ReSharper suspended, and combing the ReSharper autocomplete options. I've tried clearing the ReSharper cache, suspending ReSharper, and then restarting Visual Studio. It doesn't appear to be related to these things in a way that I can see.
I've also tried typing "this." very slowly and the behavior did not change; it doesn't appear to be a race condition. Visual Studio itself auto-completes correctly but using ReSharper autocomplete always has this problem.
Thanks in advance for any advice you can give!
Update: After restarting Visual Studio again, the autocomplete selections did appear correctly once if I typed "this." before VS / ReSharper seemed to fully load (it hiccuped while I typed and when it recovered, the autocomplete was correct). Subsequent attempts reverted to the undesirable behavior.
This is really weird. I've filed an issue with JetBrains here:
http://youtrack.jetbrains.com/issue/RSRP-330185
I'm using the same setup and it works. Your issue can be caused by:
a defective ReSharper installation
additional plugins that interfere with the Resharper IntelliSense
your computer is just a bit to slow and doesn't build the list fast enough
Edit:
I would reinstall resharper (completly remove it - don't repair) and try again.
You may disable ResharperIntellisense or limit it from Resharper->Options->Intellisense->General. I think it is beacause my computer is too slow also or a problem with VS2010.

Visual Studio 2012 and Intellisense

I think this is just happening to me, but every time I start my project in VS I have to do devenv.exe/resettsettings otherwise the intellisense doesn't work. Does anyone know any special reasons as to why?
These options should be enabled:
Tools->Options->Text Editor->C#->General->Auto list members
Tools->Options->Text Editor->C#->General->Parameter information
Tools->Options->Text Editor->C#->Intellisense->Show completion list after a character is typed
If it doesn't work try this:
Tools->Import and export settings->Reset all settings
after many posts, I can solve this problem well:
Execute developer prompt command for visual studio 2012 --> gacutil /u Microsoft.VisualStudio.CSharp.Services.Language.Interop
solved the problem for me.
Close the current Tab (in which Intellisense is not working) and reoppen it. Many times this was enough for me, boring, but enough.

Can you get ReSharper to display exceptions in Intellisense?

I'm a fan of the overridden Intellisense behaviour provided by ReSharper. However, I can't seem to get it to display exceptions (anything with the /// <exception cref="SomeExcpetionName"/> xml comment). Does anyone know a way to enable this functionality?
NOTE: This is not an issue related to not including the xml comment file from a dll as it is happening for all classes (even core .Net ones). Plus, any of my own libraries, which I have ensured the XML file is included, are not displaying the exceptions in the comments either.
NOTE 2: I have tried selecting Visual Studio Intellisense instead of the ReSharper Intellisense (via Tools > Options > Text Editor > C# and turning on the Auto list members and Parameter information settings under the Statement completion section). This seemed to bring back the exceptions (after a Visual Studio restart). However, it only works when I bring up Intellisense via tab completion and not when I just bring up the tooltip for a method by hovering over the method call (this used to work... it even works properly for the first few seconds after starting up Visual Studio, but then something disables it again).
Specs:
ReSharper 5.1.3
Visual Studio 2008 Professional
Well after a reinstall that made no difference, I realized that the %appdata%\JetBrains\Resharper\v5.1\vs9.0\UserSettings.xml file was still there (which explains why a reinstall didn't work). I then did a diff on the file with another developer in my group that wasn't having the issue. I found the setting that was causing the issue.
If you wish to have your tooltips (inside of Visual Studio) show the exceptions that a method throws, you must have the following option turned off:
(In Visual Studio via the menu)
Choose ReSharper > Options > Code Inspection > Settings > Color identifiers
Uncheck the option if it is checked (disabled by default)
(In %appdata%\JetBrains\Resharper\v5.1\vs9.0\UserSettings.xml):
Find the <Highlighting Settings> section.
Delete <IdentifierHighlightingEnabled>True</IdentifierHighlightingEnabled> (You could also set it to False, but when you uncheck it via Visual Studio it actually deletes it).
Hopefully this saves some other people from the same headache. I believe this is actually a bug since using colour identifiers should have nothing to do with tool tips/Intellisense displaying possible exceptions. I'll report it to JetBrains.
UPDATE:
This issue has already been reported here.
UPDATE 2:
I was talking about this issue with one of the JetBrains support engineers and he said they'll see what they can do to address the issue in ReSharper 6. (No guarantees, but they are at least considering it).
UPDATE 3:
There is a linked case (same issue) that has been recently updated. The case has been set to a priority of show-stopper and is slated to be fixed for version 7.0.1.

Categories