@Stefan,
I'm having a hard time understanding the usage scenario for this feature.
Do you want it to be implemented because you don't like the type members layout scheme used in your team and consequently you'd like to use your preferred scheme when reviewing File Structure?
Alternatively, is it a common scenario that you and another team member are working on the same code file concurrently, and one of you applies Code Cleanup before committing?

Problem: We have a type members layout scheme which e.g. sort members alphabetically. User 1-3 add new methods in Foo.cs, commits without applying the Code Cleanup with the shared type members layout (very common).
Then user4 wants to add a new method, and actually "remembers" to apply the Code Cleanup before committing. If user1-3 continues to edit "their" methods, they will get in trouble when updating user4's changes since now these methods are located at different locations in file. Then the user must re-align his current work with version from user4 to see if user4 also updated something in the method he "moved" to another location in the file.

Another issue with reordering a file, which e.g. hasn't been reordered for quite a while, makes the SCC providers "Annotate" function (e.g. in Subversion and TFS) useless (Annotate indicates which user last modified the current code line).

Since our reordering/regioning of members only is used to get a better overview of the file (especially when using RS's file hierarchy), it would be better if we had a window that dynamically updates, so it doesn't matter if a user places a method inside wrong region, or sort method names incorrect etc.

(VA has something similar they call "Hovering Class Browser", which dynamically changes when one hovers with the mouse over a type/variable which is very helpfu back in the C++ days to get an overview of the class without even have to go to the class definition).

See also the forum thread at http://devnet.jetbrains.net/thread/286640

@Stefan Thanks for providing the details.
There's almost no chance we can get this done for ReSharper 6 but we'll consider it during feature planning for a future version.

+1 on this, the scenario Stefan details here is the one I had in mind when creating RSRP-7846.
This was one of the regressions I experienced when moving from Eclipse/Java, which has a "Java outline" window instead of a "File structure" window, so it would be nice to see it rectified.
(ref http://help.eclipse.org/helios/topic/org.eclipse.jdt.doc.user/reference/views/ref-view-outline.htm )

+1. Agree with Hans Christian Falkenberg wholeheartedly.