Its also my own personal habit to use the word "task" when documenting my
code using regions which are both a blessing and a curse... so I use the
word to indicate code that require logical processing of some type,
branching logic and so on... whereas methods, events and properties should
be terms that are self evident eh?
#region Task: Membership Control Panel
// code to manage some membership processes...
....
#endregion
I also use other "keywords" in my regions...
#region Method: ...
#regtion Event: ...
#region Properties:...
The blessing should be obvious as regions are collapisble and help keep the
collection of code organized and easier to scroll through a file with
thousands of lines of code but the curse is it hides the code when collapsed
making it impossible to see something and easy to forget which region the
code you are looking for exists. That is why I broke my regions into named
categories as it helps manage the curse.
"Family Tree Mike" <Fa************@discussions.microsoft.comwrote in
message news:85**********************************@microsof t.com...
If you mean the Tasks View, then there are two options (at least).
1. You enter a task reminder like "Hey, fix the code in class XYZ, method
ABC."
2. You enter a comment task such as "// todo: Fix the line below this
comment.
Item one shows up as user tasks while item two shows up as comment tasks.
VS will put a ton of comment tasks when using the automagic conversion
utility from VS 2003 -2005/2008.
"Bernard.Mangay" wrote:
> It's such a common word that I can't find any documentation on the
subject.
I'm using Visual Studio Express 2008
