Stop using region things, unless your code is really looong. Regions are only for your or someone elses notification to find some code faster, and its better organized as well.
Usually we put fields, properties, delegates on top of the class (together in some order), below are methods and events.
is there anything else you would like to know, something more specifically=
I didnt say you must not use Regions, sure you can, but they will only your code "less readable" is your code is "short".
Reagions comes right, I repeat, when you have a lot of code, maybe 1000 of lines on one *.cs file.
Otherwise, they are sure a good option to divide the code into peaces.
But remebember on thing too: its better to create more *.cs files then using Regions. The whole code still looks mor clear.
I'm the opposite of Mitja, I use regions all over the place. Usually have them for Properties, Constructors, Public Methods, Private Methods, Internal Classes (usually named Helper Classes), Events, and Interfaces, to name a few.
This is very kinda a personal question. Every one has his own opinion on this, this question is like "Which car you like?". Im sure you will get almost as many different answeres, as many people you will ask.
But try to hold one princial: Keep same kind of data (methods in this case) together.
I would recommend you ones again to split methods into classes, so one class would have similar method and stuff around.
And try to hold on this 3 or n - Tier Arcitecture. This means splitting data into sectors:
- data access - if you work with databases),
- buisiness layer - additional code, like some calculations, ...
- graphical user interface (code for controls)