Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
After maintaining lots of code littered with #region (in both C# and VB.NET), it seems to me that this construct is just a bunch of ‘make work’ for the programmer. It’s work to PUT the dang things into the code, and then they make searching and reading code very annoying.
What are the benefits? Why do coders go to the extra trouble to put this in their code.
Make me a believer!
A similar question has already been asked.
but…
I would say not anymore. It was originally intended to hide generated code from WinForms in early versions of .NET. With partial classes the need seems to go away. IMHO it gets way overused now as an organizational construct and has no compiler value whatsoever. It’s all for the IDE.