Visual Studio no longer displays "Show Potential Fixes" - c#

Suddenly I can no longer see the option to show potential fixes when hovering over a squiggled item. I don't understand why this option disappeared.

Try using the shortcut.
Ctrl+.
or
Alt+Shift+F10

You want to hover over the item and hold your control key, this should display your error correction menu. If not it's most likely a settings issue, you can contact Microsoft support for quick efficient help, it's been awhile since I've dabbled in visual studio.
Here's a link to their visual studio help center. I hope you work it out!
https://www.visualstudio.com/support/

Related

Keybind to correct a suggestion in Rider

I'm new to Rider and in Visual Studio I can press Alt+Enter to correct something to what Visual Studio suggests.
I've tried to illustrate the situation in the picture below. So the editor (ReSharper (?)) suggests I use the wording MyRoom instead (which makes sense for methods), but is there a command to auto correct this as with visual studio 2017? And in that case, what is its name? I've been trying to find it in the keymap but cant find it
I am not quite sure, but there is an extension call IntelliSpell
Easy-to-use, one-click operation to spell-check your Microsoft Visual Studio files, projects, or entire solution.
you can find it here: https://marketplace.visualstudio.com/items?itemName=GrapeCityinc.IntelliSpell-SpellCheckerforVisualStudio
In the Rider help it is written, that you can also use Alt + Enter. You could also try Ctrl + .. If I remember correctly it worked in Visual Studio with Resharper.
It's apparently called "Show Intention Action" and was bound to something weird on MacOS! I've bound it to cmd+enter now. Thank you for your help though! :-)

Hide XML comments in Visual Studio 2017 (version 15.5.1)

When collapsing the XML comments for methods etc. It used to be that the summary was hidden. As I would like it to be. Then in VS2015 they broke this. I asked a similar question about VS2015 and got a nice workaround here - to use <para>.
The workaround continued working in VS2017 until now. Now I updated to version 15.5.1 and the workaround is broken, (why??...) and I can't find a setting to change that.
Is there one somewhere?
The way XML comments clutter up the code has always bothered me. In the past I've tried a few different Visual Studio Extensions and they've always sucked.
However, I just installed NoComment and it seems to do the job. I'm running Visual Studio 2017 version 15.7.3.
While I was looking for this I came across your question, so I thought I'd provide an answer. Hopefully you'll find it helpful :)
Since NoComment is no longer supported. I found Collapse Comments is the closest extension.
It works perfectly on Visual Studio 2019. It does a similar act of hiding xml comments. With options to hide small (single-line), long (multi-lines), and documentation (xml) comments.
Choose what you want to hide in the toolbar that you will see after installing the extension.
Click on the comment icon to show, click somewhere else and it will auto hide.
Quote of features the listed features by the developer in readme.md
Ctrl+M, Ctrl+C collapses all comments (and using/Import statements)
Ctrl+M, Ctrl+D expands all comments and closes all other areas
Works with C#, VB, and XML comments
Can also collapse (or expand) using/import directives
Can be configured to collapse comments when a document is opened

Visual studio TEST missing from the main menu

After updating to visual studio 2013, update 4, the TEST option is missing from my screen, I thought Visual Studio update 5 would fix it, but it did not. "TEST" is missing from my options and I don't know why.
I have tried resetting the settings, it does not help, reset settings:
I cannot add test via TOOLS -> CUSTOMIZE -> COMMANDS -> ADD COMMAND, it is not there.
What edition of Visual Studio are you working with? Have you ever had
the TEST menu present?
Yes, I've run tests before, I'm currently
at Visual Studio 2013.5 - Premium flavor
#OP answered:
I don't know why, but uninstalling Office Tools extension seems to have fixed it.
I wanted to provide an explanation for why Menu's can go missing. One reason for this is when you install another component for Visual Studio, like Team Foundation Client or in this case Office Tools extension. They "may" automatically select a different setting. To check if this is the problem:
In Visual Studio click Tools Menu > Import and Export Settings:
See here how Project Management Settings is selected, that is the wrong setting if you're a Developer.
To see the missing developer menu's reset it back to a developer setting.
Ref: http://blog.accentient.com/a-visual-studio-mystery-the-case-of-the-missing-menu-items/
I had the same issue in VS 2015 Update 2 Community and the culprit apparently was AppInsights extension (https://github.com/dotnet/roslyn/issues/11653). To provide some detail:
Noticed test menu missing in existing solution where I previously ran tests
Made a blank test project, still no test menu
closed vs and reopened. Still not test menu
Got error referencing C:\Users{username}\AppData\Roaming\Microsoft\VisualStudio\14.0\ActivityLog.xml
Last error in there was NullReferenceException in CodeLensIndicatorService
Googling that found link above, tieing to this add-in.
disabling it fixed the issue and test menu not appears and I can run tests.
Forgive me if I complain a bit, but if any VS team is reading: Under no circumstances should an add-in failing cause a built-in menu to not appear. As much as this is a bug caused by the the various add-ins, it is also a flaw in VS IMO- and one that is not trivial for end-users to connect the dots on.
Somehow the settings (settings have menu items configuration also) for your visual studio may have issue. Either you can try reset. Only in case that doesn't work you can always customize your menu item. so
Tool -> Customize (by default standard should be selected)
select commands tab and then menu bar option. You can see options to add commands. Under that you can select test so make testing option visible.
Also for testing test case, you can always right click on class and run it.
Hi Please try to reset all setting
http://blog.accentient.com/a-visual-studio-mystery-the-case-of-the-missing-menu-items/
If not then there is workaround to add your setting
http://blogs.msdn.com/b/visualstudioalm/archive/2012/09/11/visual-studio-2012-where-is-the-test-toolbar-couldn-t-find-it-anywhere.aspx
After doing close visual studio instances and reopen it.
I don't know why, but uninstalling Office Tools extension seems to have fixed it.
Edit: I tried to reproduce this bug, I ran the VS2013.5 update and clicked repair. The update took +5 hours, figured it got stuck. So I cancelled it, got stuck cancelling. So I ended the process. Now I started visual studio and TEST is missing, basically my visual studio installation is messed up I think.
Edit: Found the culprit, it was Microsoft Intune Endpoint Protection that was installed on my pc. It basically scanned everything and when visual studio got updated and files were written to the disk, something went wrong and corrupted my install. I turned it off by excluding C:\* from being scanned and ran VS2013.5 update and clicked repair. Everything is fine now.

There are no usable controls in this group. Drag an item onto this text to add it to the toolbox" Visual Studio 2012

Its Not a Programming Question But about Visual studio express 2012.
Trying to create a new report in the visual studio 2012 but can not see the list of data sets, parameters etc: In general tab i am seeing this
"There are no usable controls in this group. Drag an item onto this text to add it to the toolbox"
I have searched to fixed it but not succeeded till now..
I came across this same issue today and read plenty of things such as "this is VS bug...." but the solution was much simpler than that, I just needed to stop debugging (Shift+F5).
If that doesn't work, I recommend restarting the IDE.
If this doesn't work, I guess that uninstalling VS and doing a fresh installation is the answer you're looking for. It's important to note that it's recommended to restart Windows after installing VS and before launching it.
Right click on the Toolbox and press "Show All"
Right click on Toolbox, Click on "choose Items.". Restart IDE. That worked for me.
Right click on Toolbar and select: Reset Toolbox.
MFC controls will reappear.
I also had this problem, and it turned out I was trying to open the wrong toolbox: what I was actually looking for was the 'SSIS toolbox'. If none of the other options have worked, try selecting View -> Other Windows -> SSIS Toolbox. That fixed it for me.
[I found this out from this blog by James Serra]
In VS 2015, the SSIS Toolbox is under SSIS tab, not under View.
"There are no usable controls..." is shown when you have currently opened a file that is not designer file (e.g. "Form1.cs"). Once you open the designer file (e.g. "Form1.Designer.cs") the items should be shown again.
Just hover over the design and then press escape. A control that you had selected and not dropped is holding up memory.
This happened to me, and it was because I was currently debugging. Once I ended debugging, the usable controls appeared.

WP8.1 SDK. Error adding controls

Just recently, WP8.1 Update was released. I decided to get the SDKfrom Here. Everything installed and it's all working but I'm getting errors when adding certain controls. Some of those controls are:
AutoSuggestBox
CommandBar
PivotControl
There could be more but, whenever i add these controls, Visual Studio Express 2013 either freezes for an insanely long time, or gives me the error: Syntax error found in XBF Generation
So can someone please clear things for me? How can I get these to work. Am I missing anything?
Thanks!
Check if some resource you are using has any type different of x in your .xaml files.
Like this:
<System:String x:Key="AppName"> <!-- this could produce the error
because the "System" namspace being called instead of "x" -->
Try to change things like the one above to this:
<x:String x:Key="AppName">
Maybe this can help you.
I found this information here.
Hope it helps!
UPDATED:
Microsoft has released the Update 2 for Visual Studio 2013 and there is a similar issue that has been fixed.
You can try to update your Visual Studio 2013 and check if this issue has gone.
Here is the link to the update: Update 2 VS 2013

Categories

Resources