How to remove the function minimize sidebar in Visual Studio 2019 - visual-studio-2019

How can I remove the little sidebar to the left of the code in Visual Studio 2019? I mean the little minus signs that appear next to each function or code block header and, if clicked, minimize that function or code block.
Is there a way to disable these?

The feature is known as "outlining" and enabling/disabling it is language-specific. In all cases, use the "Options" command from the "Tools" menu and then, in the left-hand pane of the displayed pop-up box, open the "Text Editor" node.
For C/C++ files, the option is under the "View" sub-node:
For C# files (and also Basic, F# and Python), it's under "Advanced":
For other languages, it's likely to be in one or other of those places, but I can't guarantee that. In all cases, changes only come into effect on files that are opened after the option is changed.
If you have another specific language for which you can't find this option, just let me know and I'll try to help.

Related

Hide suggested text when typing in Visual Studio 2019

Does anyone know how to turn off this annoying popup in Visual Studio Community 2019?
All the answers I see for it are for Visual Studio Code when I google it, which says to change it under the "File" > "Preferences" menu. Visual Studio 2019 doesn't have that menu. I just want to code without visual obstructions from my editor. Driving me nuts. Thank you!
The language is VB in ASP Classic environment.
I have turned off everything I could find that seems like it could be related to a popup under the "Options" menu, but many of the descriptions there are obscure. You could seriously make a full time job out of learning what all this stuff means.
I found an answer, however odd it may be. With #JackArbiter's help in narrowing down the possibilities, it turned out to be the file type within the environment that was the issue. I didn't realize at first that it was only a certain file extension that was creating the issue. The *.asp files behaved appropriately, but the *.inc files were the problem.
I went to "Options" > "Text Editor" > "File Extension" and added the "inc" file extension there with the editor set to Visual Basic. These files now behave the same as the asp files.
Go to Tools>Options>Text Editor>[Your markup or language] and you can adjust the intellisense settings. In your case there will be no intellisense settings listed (general HTML is what I assume to be the issue here, though you'll have to do this again probably for the language of the IF/Else code blocks) so go to HTML>General and uncheck "Auto list members" at the top.

I would need some hints with F# interactive usability

Now in VS2013 and F#3.1.1, I noticed that it is a bit cumbersome to send code to F# interactive.
There are separate menus for but no keyboard shortcuts for
sending project output as reference to F# interactive
sending project references to F# interactive
In the editor window, there is no "send whole file" to f# interactive. You have to select it all, right click and send.
It feels very unpolished. Are any faster ways of doing this?
What are your IDE workflows?
As I am righting these questions, i think about maybe using shellplus powershell integration for invoking this...
Just in case it helps: you can right click on any reference in the Solution Explorer and do 'Send reference to interactive' - or you can right click on the References node and send them all to interactive.
You can also do this in your source:
#r #"c:\mycode\myassembly.dll"
...and you can surround that with #if interactive to stop it messing up your compiles.
#if INTERACTIVE
#r #"c:\temp\myassembly.dll"
#endif
Finally you might also want to look at script files (.fsx) - googling for "f# script files" produces some useful references.
For sending references, yes, you have to right-click on the individual reference or the references node and click "Send reference to FSI." Not perfect if you prefer keyboard shortcuts, but much improved from VS 2012 when you had no choice but to type out a full #r statement every time...
For sending code, Alt+Enter is the easiest/most popular shortcut. Highlight the code you want to execute (using either mouse or keyboard), then hit Alt+Enter. To send the entire file, just use select-all (Ctrl+A) to highlight everything.

Turn off context menu for Component applied by CnPack (design time)

After I installed cnPack, right clicking on a component in my form seems to have taken away any specific items that the component itself may have applied.
eg, right clicking on any Dev Express component will usually bring up version details. Now I get a bunch of other context menu items and the Dev Express ones have disappeared.
Is there a wizard or some other option I can disable to stop this? I can't find one anywhere.
Thanks
EDIT
Restarting Delphi fixed it in the short term - but has come back again so I'd still like to find a resolution to this....
Right-click menus are controlled by component editors, and AFAIK there can only be one component editor registered to a particular class type at a time. If CnPack's design-time package is loaded after DevExpress's design-time package, then CnPack's component editor will be the last one registered and take priority.

How keep the debug layout the same as the desktop layout

I try to have a similar layout during editing as well debugging. When running the program my structure and object inspector disappear. I did create my own desktop speedsetting, set the debug desktop to it as well, but as soon as the program runs structure and obejct inspector disappear. How can I prevent that?
A question related to this: the edit menu changes as well. A right click on a procedure name results in a popup menu with the first item being "find declaration". When debugging the first item is "close page". I find the find declaration item a fast way to find some code. Apart from that it is frustrating to lose one's code because you click "no" on the question to save the information (I know, it's my fault but menu's shouldn't change in my opinion).
Thanks,
Arnold
What version of Delphi? Dialogs and menus change between versions (and even between SKUs of the same version).
For the first, open Tools->Options->Environment Options and uncheck Hide designers on run in the Running group box (D2010, XE, and XE2), or Tools->Options->Environment Options and unchecking Hide designers on run in the Compiling and Running group box (D2007).
For the second: The right-click menu is called a context menu, meaning it displays what is appropriate in the context of when it's being shown. It's entirely appropriate for it to change depending on when and how you're using it; that's the way it's supposed to work.
Right-clicking on a .zip file in Windows Explorer is different than right-clicking on a Word .doc file, because they have different options based on context - a zip file has an 'Extract to...' option that the Word document doesn't have, because 'extracting' a Word document doesn't apply. Same applies to right-clicking a .exe file, which has the Run as Administrator option (Win7), as opposed to right-clicking a .pas file, which doesn't offer that option.

F# compiler order of source files

As I understand it, when using F#, you have to manually list the source files in dependency order for the compiler's benefit (if there is any way around that, please let me know!)
Listing them on the command line from left to right obviously isn't going to scale. Is there a way to at least make it accept the list of files in a text file, one per line, preferably with the ability to put in blank lines and comments? I've checked the compiler options, and I don't see anything that looks promising.
About the Visual Studio 2008 integration, you can move up/down source files with a right click and choosing Move Up, Move Down or use the shortcut Alt+Up Arrow, Alt+Down Arrow after having selected the file.
No, but the typical way to compile F# (at least on Windows; dunno about Mono) is via MSBuild; the .fsproj project file puts each file as a separate <Compile> item on a separate line. What build tools are you using?

Resources