Home Dashboard Directory Help
Search

Save Outlining collapse state of methods, etc. by Qnomad


Status: 

Closed
 as Fixed Help for as Fixed


6
0
Sign in
to vote
Type: Suggestion
ID: 467059
Opened: 6/14/2009 10:35:37 AM
Access Restriction: Public
0
Workaround(s)
view

Description

Currently, Visual Studio remembers the expand/collapse state of #region's in a C# code file. Upon closing the file, however, it forgets which methods, etc. have been collapsed. Users who rely on the Outlining feature to "drill down" into relevant details, are frustrated by this shortcoming. Upon re-opening the file, the user is inundated with irrelevant details.

From a user perspective, no fundamental difference exists between collapsing a #region and collapsing a method.
Details
Sign in to post a comment.
Posted by Peshay on 11/21/2013 at 11:17 AM
Outlining states for custom regions (created through Ctrl+M, Ctrl+H) are not being remembered at all.
Posted by endasil on 10/20/2011 at 12:52 AM
Atleast In VS 2008, the state of outlines created with Ctrl M+H are not saved, and it is a feature that i would also like to see.
Posted by avrelian on 12/27/2009 at 9:05 AM
I agree with hornerj99. Big JScript files is a nightmare. The only workaround is to split them.
Posted by hornerj99 on 12/22/2009 at 10:29 AM
I'm not sure it is Brittany. For example, as a UI-focused developer I work with pretty complex javascript files. Since the automatic outlining doesn't work with JS, I typically create outlines in the JS (CTRL M+H), but I have to do this everytime I open the file because the outlines are not saved. For some developers this may not be a big deal, but for those of us who use JS regularly (especially now with the jQuery integration), it becomes a big time waster. Please consider keeping this issue open! Thanks.
Posted by Microsoft on 6/30/2009 at 2:40 PM
Hi HappyNomad (and Martin/other raters),

Thank you for submitting this suggestion. Visual Studio actually does have this feature: in both VS 2008 and the recent VS 2010 Beta1, outlining state is persisted for any files that are part of a project or solution. If you're using stand-alone files that are not part of a project or solution, though, outlining state will not persist because we store the collapsed/expanded state data with other project-level metadata.

None of the resolutions seems quite right here, so I'm resolving this bug as Fixed because it's a feature we already have in VS. If you try this with files in a solution and outlining state is not remembered correctly, please post again here and we'll take another look.

Thanks for using VS and sending your feedback!

Brittany Behrens
Program Manager, VS Platform
http://blogs.msdn.com/vseditor
Posted by macthestack on 6/28/2009 at 10:12 AM
I totally agree. A feature like this would save alot of time.
Posted by Microsoft on 6/16/2009 at 3:26 AM
Thank you for your feedback, we are currently reviewing the feedback you have submitted.
Sign in to post a workaround.