Hi,
I've already searched all of the forum to find a list of possible variables to use inside of the Type Members Layout. The only one I found was ${ImplementingInterface}.
It's just because I want to define a different region layout in my C# code as I am used for some years now. It looks like the following.
//########################################################################################
#region Fields
// Contains all private fields (and also public fields in case there is a really
// good reason to have some)
...
#endregion Fields
//########################################################################################
#region Properties
// Contains all properties, that are not part of an interface implementation
// those go into "Implementation of I..."
// regardless of the access modifier (public, private, protected)
...
#endregion Properties
//########################################################################################
#region Delegates and Events
// Contains all delegate and events
#endregion Delegates and Events
//########################################################################################
#region Construction/Destruction/Initialisation
// Contains all constructors (class constructors as well as static constructors),
// All initialisation methods that need to be called before using the class
// And finally all finalization code (Finalizers, IDisposable implementation, ...)
...
#endregion Construction/Destruction/Initialisation
[...]
Does anybody knows if it is possible to implement those kind of regions inside of the Type Members Layout definition?
Asking greetings
Reiner
Hi,
ReSharper 7.1.1 can provide region layout for Type Members using default pattern 'Default layout using regions' available in "Code Editing → C# → Type Members Layout" options dialog.
Please let me know if it helps.
Thanks!
Hi Alex,
please read the thread subject and the first two sentences of my question carefully. ![]()
Hinting greetings
Reiner
Hey Reiner,
Right :-) Sorry that I didn't understand the question.
Unfortunately, this kind of layout is not supported by ReSharper at the moment.
We apologize for the inconvenience.
Thanks.