Visual Studio Community 'Ctrl+K,Ctrl+C' not available - visual-studio

Visual Studio Newb but trying to get used to it.
Right off the bat trying to comment out a few lines of a powershell script.
If I highlight the lines and then do a 'Ctrl+K, Ctrl+C', not letting go of Ctrl(But I did try it every which way).
I get the message -
The key combination(Ctrl+K,Ctrl+C) is bound to command (Comment
Selection) which is not currently available.
Or in the menu its greyed out.
Comment Greyed Out in Menu
Haha, this just seems like such a standard thing to be able to do...I can't believe it has to be turned on somehow in Visual Studio.
I'd appreciate any advice on what I'm doing wrong... thank you!!

Related

Visual Studio Intellisense suggestions disappears immediately after coming up

I am using Visual Studio Community and Visual GDB to code and debug STM32 projects.
The problem:
When I type something that is known to Intellisense, (path, variable or anything really), the suggestions come up briefly and then immediately disappear therafter. For that split second I can see that Intellisense has the correct suggestions, but TAB or ENTER does not work since the suggestions disappear very quickly.
Does anyone know how to fix this?
Thank you
You might try to disable any extensions in Visual Studio.
I had the same problem, surfed around and read in some places that disabling extensions would work.
So I disabled them one by one and the problem was gone.

Visual Studio Duplicate Shortcut Not Working

I have always used Ctrl + D to duplicate lines in Microsoft Visual Studio Community 2019
Version 16.8.5.
But recently, for seemingly no reason, it doesn't work. It doesn't even respond. It doesn't work when text is selected or not.
I was wondering if anyone else was encountering this issue. I wonder if it has something to do with an update or something. Any information or help to fix this issue is appreciated.
In VS keyboard options, check what is assigned to the Ctrl+D shortcut and Edit.Duplicate command:

Visual Studio text editor does not recognize F# source?

I have got the following problem with F# code recently: almost the complete code is underlines with curly red lines (indicating problems) and whenever I hover with the mouse cursor over any word the pop-up appears with the message "Unexpected token". IntelliSence doesn't work either.
Nonetheless if I start the project it is executed without any problem.
This happens both to already existing F# files and to newly created F# projects. I remember it was working just 2-3 months ago!
I tried to deactivate all possible extensions but it doesn't help.
Any ideas?
I get this too. Sometimes, simply exiting and going back into VS helps. When I tweeted the problem, Don answered with this:
"do you have "python tools for visual studio alpha" installed? if so, uninstall it or apply the hot fix"
This wasn't relevant to me (as I haven't been anywhere near python) but I'm posting here in case it helps you.
-- Edit: here's a link to the patch, thanks to Alexander Galkin: http://pytools.codeplex.com/workitem/599
I haven't seen this situation before but here's a guess at why it's happening and how you might cure it.
Visual studio works on a system for plugins. Even the stuff that is "native", like the C#/F#/VB.NET project systems, are just plugins that uses the visual studio shell. It looks like the F# plugin has been damaged in someway.
If this is Visual Studio 2010:
You might try opening the visual studio installer and trying a repair installation or deactivation and reactivating the F# project system
If this is Visual Studio 2008:
You might try uninstalling and reinstalling the F# plugin

Why does the "Navigate To" feature stops working in Visual Studio 2010

I have been a fan of the new "Navigate To" feature that was released with Visual Studio 2010 since I saw Scott Hanselman using it in one of his presentation.
For some unknown reason, it randomly stops working.
I hit "Ctrl + ,", type what I am looking for and then nothing happens.
It seems to wait for something and the window shows no progression in the research.
The only way I found to fix this is to restart Visual Studio and wait for the problem to happen again.
Does anyone have any idea why Visual Studio is behaving like this and how I can fix this?
I got this working by simply selecting an item from the Search Items dropdown. Once you do that, the search starts working again as expected.
I got this working again by uninstalling ReShaper. It fixed some other things like the solution wide search aswell. I'm not so happy about the solution though...
Any chance you're using resharper, powercommands, or productivity power tools?
I suspect the issue is related to one of those (I have the same issue), but since it's difficult to reproduce, it's hard to test that.

Updating JScript intellisense hangs VS 2010

I have a web application and whenever I load it in VS 2010 RTM, the left hand corner of VS says "updating JScript intellisense" which never completes. When I click anywhere in the editor (becuase the solution has finished loading), I see a balloon on the right hand corner saying Visual studio is performing an internal operation...) and ultimately I have to end the VS process. Very frustrating..
I went ahead and disabled JScript intellisense as described here and that didn't help.
Anybody has any clue in this?
Pin open your Output window to get specific information on what Visual Studio is doing. Chances are it is parsing js file links in your webpage, including master page and trying to download these files over the network or encountering an error trying make intellisense of them all. Try commenting out your javascript links, using local copies instead of remote, or attempt to resolve the specific errors. More info here.
I restarted my machine and It resolved the problem. :-(
Maybe I'm late answering this question, but I found a way to disable JScript Intellisense. Following this: http://msdn.microsoft.com/en-us/library/ecfczya1.aspx , in the "Text Editor" options, select JScript. In the "General" options, deselect the checkboxes saying "Auto list members" and "Parameter Information". It worked fine for me.

Resources