Those region discussions are really amusing. It's as if there is a law to use or not use them. I myself am using regions in all classes. Even if they are only a couple of lines in them. I group them into a declaration part, constructors, properties, methods, event handling, overridden methods and interface implementations. and maybe some other things if neccessary. And I use sub-regions inside the regions to group things that logically belong together. I think my code is very well structured, and if I find my class does get too long and should be refactored, the regions usually help me because the parts that can be separated usually are in the same region. I do not see an advantage of seeing all the code when I open a file except for that it looks more complex and "impressive". If that's what you need, you really have a problem. If you are too lazy to click once to open a regions...then actually I don't understand why you are not too lazy to use the scroll wheel maybe even a couple of times. (btw. if you're using vs then you should read the manual because you can switch on/off region folding when opening a file in the preferences). I have seen a lot of smelly code by people who tried to avoid regions...well around 50% of code was smelly with or without them, but people claimed it was all fine, in some cases people used hundreds of partial classes which did not make the code any better than with regions, but made it harder to see the code of a single class because you had to browse several files to do so, and in some other cases I got crazy because people insisted on making hundreds of classes to make their code shorter, and seperated things that actually belonged together, with the result that you had to call a.b.c.d.e.f.g to get the value of a property Not to mention how horrible it is to browse to the class that finally contains the property you want (go to definition...go to definition...go to definition...sic!).
Oh, and a big bunch of people are simply too lazy to structure their code and use the smelly code argument as an excuse.
Rubbish, because it's all in your hand if you are ill-using regions to hide bad code. It's like not using cupboards to put your clothes in because some people's cupboards are messy.
But regions help you structuring you code, and group properties and constructures and methods and all together, and easily jump to that region to add a new one. Sure you can do that without regions too...you can also write your code with notepad if you want.
Tools like StyleCop or such that group your code? Hmmm but if you need them then isn't your code smelly too? Because you claim you do need to hide anything. I do not need any tools to find my way around my code because regions do it all for me...