The plus / minus signs are gone to expand / collapse regions. The vertical lines to indicate regions are gone too.
The regions are collapsing and all the commands under edit, outlining work fine.
It's just I have to double click on the collapsed region to expand and there's no way to collapse a region with the mouse. Only the shortcut keys (ctrl m, m) or the menu will do it.
I swear it was right this morning but I did something to mess it up. I can't find any option in tools to fix it either.
UPDATE
Now, some files are doing this and other files (both opened at same time) are not doing it. If anyone can explain, I'm all ears.
Press ctrl+, (control plus semicolon) to open the settings. And type Folding Strategy in the setting's search bar. It is set to auto by default. You can set it to always for the controls to be visible at all times, otherwise, it shows only on mouse over.
This same thing happens to me multiple times a day using VS.NET 2015 Pro version 14.0.24720.00 Update 1. Restarting the IDE always restores normal function for a while but the problem always returns, seemingly at random.
UPDATE:
I tried changing the theme from dark to blue and it restored the outlining. I then changed back to dark from blue and the outlining continued to work normally. Still a pain but definitely a lot faster than restarting the IDE.
It happened with me also. One file was just fine and other file (js) was not. I searched it a lot.
Try selecting a method/if check etc and press ctrl+M+H which is short cut for right click outlining > Hide Selection.
You can do it on the whole document as well.
This might be helpful when working on a file which has too much code in it and you are going through different functions again and again. It is painful with scrolling mouse for so long.
You can use short cut for for moving at the start of the method or at the end of the method with the following :
select parenthesis { start or end } and press ctrl+}
Hope this helps.
It works again.
I closed all windows and reopened my code file.
Now it shows the plus minus glyphs again.
I know this is an old post, but I wanted to share a quick solution. if you right click and hover over 'Outlining' and then click 'Collapse to Definition', the widget comes back. Then just press [ctrl] + z to undo and continue where you left off.
With Golang, if the code has some syntactic mistakes that would prevent it from compiling, the language server cannot decide which parts of the code are collapsible, and which not.
Therefore the solution is either switching to the Folding Strategy in VSCode settings to indentation folding, or fixing the syntactic errors.
Simple solution : CTRL + M + O, then CTRL + Z
Thanks to SparrowEatsHawk
Everything was working perfect. Today suddenly VS 2015 RC started to open the Task Runner instead of what it should do "{".
Any suggestions?
When I open Notepad it works.
I guess the issue is somehow related to the fact that the shortcut is similar to Ctrl Gr + รค.
I never changed anything. Strange. How to fix this?
I don't know why that happened, but you can try the following to fix it:
Open Tools - Options, select Environment - Keyboard.
Under "Show commands containing", type taskrunner.
The View.TaskRunnerExplorer entry will appear in the list. Select it.
Select the offending shortcut in the "Shortcuts for selected command" list, and click "Remove". Or, you can also focus the textbox under "Press shortcut keys", press a new key combination, and click "Assign" (although I'm not sure if this will remove the old one).
I am running Xamarin Studio 4.2.3 on Windows. I have it set to show the autocomplete window automatically when typing... so for instance, when I type cw the following appears:
The editor will allow me to choose CswWriter from the list and press either TAB or ENTER to replace the cw with CswWriter.
However... it will not allow me to choose the cw snippet from the dropdown. I also dug through the Key Bindings dialog looking for the ability to bind something like "Expand Snippet" to a key and did not see it.
Anyone know what's going on? How do I expand the snippet?
I CAN bind a key to "Insert Template...", which pops up another autocomplete-like window with only code snippets in it... but why put them in the normal autocomplete if it won't actually let you choose them?
Xamarin Studio has similar behaviour to Visual Studio. To expand the snippet you need to press tab when the completion window is closed.
When you type in cw, the auto-completion window is displayed, pressing tab will then complete the text, in this case cw, which you have already written. Now if you press tab again the code snippet will be expanded.
The first tab key press in your example is a bit confusing since you have already typed in the full text, however for longer code snippet names (e.g. 'prop' and you have typed in just 'pr'), it is less confusing since you will complete the text for the code snippet with the initial tab key press, then pressing tab again will expand it.
Visual Studio displays the message "Press TAB twice to insert the snippet" in the code completion window to make it more obvious what you need to do.
I just upgraded my Visual Studio from 2012 to 2013 and haven't done anything else yet short of installing all the updates recommended.
For whatever reason, when I go into my solution and press F10 or F11, it runs the entire program as if I had pressed F5... F8 works the way F10 used to, but I don't know why the keys I've always used now don't.
I set up visual studio as a VB environment.
How can I fix this?
Thanks!!!
Additional Info:
Just to add on as much information as I can, if I set a breakpoint in my code, then I can use F10 / F11 to continue stepping through my code once the breakpoint is hit and execution is stopped as would be expected.
EDIT 2013-12-31:
Based upon a comment made by Neolisk, it appears this is simply a change in default behavior in Visual Studio 2013... If anyone knows how to change this back to the way it was in 2012, that would be GREATLY appreciated, but at least I now know it's not an error / installation issue.
If 2013 works the same as previous versions, then do the following:
Navigate to Tools > Import and Export Settings
Choose "Import selected environment settings"
On the next screen, choose to save your current setings if you want to.
When you get to the point where you can import, just select "General Development Settings"
That should set everything back to what you're probably used to. Most people are set up using general settings and either don't realize it or just forget.
EDIT: If your issue is that the program executes when you press F10 or F11 when you are not debugging, then I think you might be out of luck. It's done that to me personally since VS 2008 (I'll frequently miss the F12 key when I'm in a hurry), and, after some searching, I think it actually happens to everyone:
Visual Studio - Prevent F11 from starting the debugger?
My guess is that this is a side-effect of not being able to set contextual hot keys based on whether you are or are not debugging. Since F10 and F11 are tied to debug-execution-related operations, my guess is that Visual Studio realizes that it needs to be debugging to process them, and thus starts the program.
ANOTHER EDIT: Of course, it's also possible that you had the scheme set to something else entirely in VS2012. Check out all of Visual Studio's pre-defined hotkeys by environment here: http://msdn.microsoft.com/en-us/library/da5kh0wa(v=vs.120).aspx
If none of those have the mappings that you're used to for F8, F10, or F11, then it's possible that you or an add-on may have had few custom hotkeys defined.
Worst-case scenario, you can simply redefine your shortcuts manually by key in the keyboard settings: Tools > Options > Environment > Keyboard
It sounds like you are in VB settings and not C#. You should try changing your settings to one or the other and see if those debug options change. On my machine
Tools - Import Export Settings - Reset All Settings - C# (If you want F10/F11) VB if you want F8/Shift-F8. It doesn't matter what your settings are you can still code in both languages, but if you are used to pressing F10 to debug VB.NET code you've been using C# settings this whole time. Nothing new with Visual Studio in this regard. I am using VS2013 Ultimate, have been using Visual Studio since VS2003.
The first image is VB.net, second is C# settings
You can try some of these reset settings:
And different combinations thereof, i.e. ResetToBasic first. If does not help, try ResetToC#, then back to Basic. Then try General, back to Basic. See if you can hack your way through like this.
EDIT: I tried my VS 2012, and compared to VS 2013. What you described is completely normal. VS 2012 used to step in Form_Load and similar on F10 and F11, VS 2013 no longer does it. So it seems like your VS 2013 is working as expected.
Microsoft probably has a reason to not allow to step into a property by default.
Properties are supposed to be mostly get and set and not contain a whole lot of implementation in it. But that may not be the case all the time.
If somebody is trying to step into a property that means this developer is suspecting something in that property that may be causing problems. So by default this behavior needs to be reversed and allow stepping into properties.
For now this is how you can enable stepping into properties.
Go to Tools > Options menu in Visual Studio.
Goto Debugging > General menu item in left pane.
In right view you will see and option Step over properties and operators (Managed only). Uncheck this option and then you are all set.
Enable step into properties in Visual Studio Debugger
If the above didn't work then follow this
In the Options.Keyboard page, please select "Debug.StepOver" from the command listbox, and then put focus to the "Press shortcut keys" textbox and press F10, click Assign button to re-assign shortcut, does it work?
You can also try to run Visual Studio under safe mode, which will prevents all third-party VSPackages from loading when Visual Studio starts; if the issue disappear under safe mode, you may consider checking your installed add-ons or VSPackages.
Second, to log all activity of Visual Studio to a log file for further troubleshooting, please use the /Log switch, and post the log file content here, so we can do more investigation on it.
If this feature works well before, and suddenly behave abnormally, it usually indicate that some files or configurations of Visual Studio installation is corrupted or missed, you can:
Restores Visual Studio default settings by using "Devenv.exe /ResetSettings" command. Please backup your settings before restore to default settings.
Repair/reinstall Visual Studio;
To repair Visual Studio In the Add or Remove Programs dialog box, select Visual Studio then click Change/Remove.
I found I had to run VS as Administrator to debug properly. I also do a clean solution prior to debugging, especially on x64 machines. If you put a manual debug breakpoint in the code and the IDE indicates it can't stop at that point, then it's possible that the debugger is out of sync with the source code.
An idea to test it in a short way:
Create a Hello World console app.
1 Module Module1
2
3 Sub Main()
4 Console.WriteLine("Hello")
5 End Sub
6
7 End Module
Build first.
Put the cursor in line 4 (before each step), commands should start Debug Mode if you are in Design Mode.
F10 (StepOver): Should break on line 3
F11 (StepInto): Should break on line 3
CTRL+F10 (RunToCursor): Should break on line 4
If it is working properly: Maybe the assembly which containing the entry point of your program had modified and wasn't been rebuilded, or there is somthing other problem with the point where the control expected to break.
If it doesn't work as expected on the sample, I think you should ask on MSDN FORUM or make a bug report.
I don't know why they might have intent to change this behavior.
It is working for me in my 2013 Express Edition with C# recently.
I found what I think is an acceptable workaround for the non-functioning F10/F11 Keys. They are probably the most used keys in stepping through code, and it is a real pain to click on debug and select the key from the dropdown.
I got around this shortcoming by adding icons to the toolbar for these operations.
If you are not sure how to do this, On the Debug toolbar click on the down pointing arrow near the right side of the bar. Click on Add or remove buttons.
Select Customize...
Select Add Command
Select Debug
Scroll down to the desired key (Step over / Step into)
You once clicked, you will see the two icons added at the left side
of the toolbar, Unfortunately they are the same Icon, but with a
little use, you should be able to select the right key to click on.
I actually prefer this method to trying to remember which function key
to press.
On many branded laptops, there is an extra button "Fn", Press "Fn" and "Esc" together. Functional keys will be enabled in visual studio.
Kindly press Fn key and Esc (with Lock with Fn label).
Sometimes it gets locked and Media Player buttons get activated.
Sounds stupid to ask but what type of keyboard do you have? I know some keyboards have different modes that allow you to set different profiles for keys based upon the application. I use the feature with my Microsoft Natural keyboard. However I have had problems with the profile still being active when I switch into Visual Studio and then F10, etc doesn't work correctly.
I faced the problem that F10/F11 doesn't work but the breakpoint works.
Once I uninstall the Security Software and unload the relevant drives it works again.
So my advice is that. And I guess it's due to the drives, so if these don't work just try to unload those questionable drives may connected with this question.
Using Logitech MX 3000 Keyboard, I've upgraded to the last setpoint version and these keys work now perfectly. (Driver version 5.90.41)
I'm using coderush with vs 2008. coding in VB.net.
I don't see any evidence of Intellassist, all i see is the usual VS intellisense.
Is this normal? Preferred? Do most people leave the defaults or do most/some turn off vs's intellisense?
Does intellassist somehow agument intellisence?
thanks
jonathan
I see CodeRush Intellassist as an extension of Visual Studio Intellisense and not its replacement or anything else. Intellassist completes the text at the editor caret position with an in-scope identifier and may include other suggestions, such as physical file path completion or enumeration elements completion (which is not actual for Visual Basic).
To use Intellassist, just write code as you normally would. When Intellassist senses one or more suggestions matching the code you've entered so far, the best suggestion will be displayed to the right of the editor caret.
Once Intellassist is active, you have several options:
Press Enter to accept the highlighted suggestion. If you have the case-sensitive option turned off, Intellassist will ensure the entire suggestion is properly cased to match the declaration.
Press Shift+Enter to accept a portion of the suggestion. Shift+Enter accepts from the caret to the character preceding the next uppercase letter in the suggestion. For example, if "AllowMultipleSelections" was the suggestion, and "al" had been typed in, pressing Shift+Enter successive times would cause the selection to shift as follows:
Shift+Enter is useful when you need to create a new variable name that is similar to a portion of an existing suggestion, or when you want to quickly access a different but similarly-named suggestion (differing only in the latter portions of the text). You can press Shift+Enter to move the selection right, and then start typing to get other suggestions.
If more than one entry is suggested you can cycle forward and backward through the suggestions by pressing the Tab and Shift+Tab.
Press the Delete key to cancel the suggestion.
Do nothing for a few moments and Intellassist will hide the suggestion.
If the text you've entered is a code template that you want to expand, just press Space or ; to expand the template normally.
Continue typing (narrowing down the suggestion list or ultimately ignoring all suggestions).
Intellassist is highly configurable. You can specify whether case-insensitive suggestions should be made, and also change a host of other options.