Region. The #region directive partitions your code. With #region, we can organize code into blocks that can be expanded or collapsed visually.
Syntax notes. We must indicate the start of the region and the end of the region. Two separate directives, region and endregion, are used for this purpose.
In this example, we demonstrate some common usages of the #region directive. Please pay attention to the #region and #endregion directives. These are balanced throughout the source file.
Tip You can optionally specify an identifier for the region, such as with #region FIELDS.
And When you compile this program, the #region directives do not affect the intermediate language output.
using System;
#region
class Example
{
}
#endregion
class Program
{
#region FIELDS
int _field1;
int _field2;
#endregion
static void Main()
{
#region BODY
Console.WriteLine("Hello world!");
Console.WriteLine("How are you today?");
#endregion
}
}Hello world!
How are you today?
Example screenshot. In the code example, we see the complete program. In the screenshot, we see the code in Visual Studio environment with the #region areas collapsed.
Tip To collapse a region, click the plus-minus sign on the left margin of Visual Studio next to your code.
#region LABEL
#endregion
#region
#endregion
A discussion. Region is not ideal. Consider instead using more classes and scopes. This enables compile-time detection of problems. It helps use the full capabilities of the C# language.
A summary. The #region directive operates at the level of the text. It does not require any particular scope to be balanced in the file. Regions do not affect the final compiled metadata.
Dot Net Perls is a collection of tested code examples. Pages are continually updated to stay current, with code correctness a top priority.
Sam Allen is passionate about computer languages. In the past, his work has been recommended by Apple and Microsoft and he has studied computers at a selective university in the United States.
