(add and remove actually are listed above. It's under "Contextual Keywords")

The add and remove accessor methods (similar to the get and set for a property) are not included in the list above.

These allow you to intercept the calls when others wire up to your events in much the same was as get/set allows you to intercept calls to a property.

Below is some sample code that shows the accessor functions.

public event EventHandler OnClick
{
   add {
      Debug.WriteLine("add called");
      Click += value;
   }
   remove {
      Debug.WriteLine("remove called");
      Click -= value;
   }
}

The descending keyword (as in orderby ... descending) is not listed above.

There's actually a bunch of keywords missing!

As mentioned before, there are add and remove, and, of coure, descending and (!) ascending!

In addition to this, I miss the context-based alias-Keyword (as in extern alias).

Then, if I may ask, why don't you document the __makeref, __reftype, __refvalue und __arglist keywords?

And last but not least, though they are not really "keywords", I think that attribute path specifiers would fit here (assembly, module, method etc.)

using System;

class Myclass
{
static void Main()
{
//int[] iPages = { 5,345345 };
//Console.WriteLine(iPages.ToString().Length); => This will output 14

//string[] iPages = { "5","adf","345345" };
//Console.WriteLine(iPages.ToString().Length); => This will output 15
}

}

I'm diving with C# data types, can someone please explain why the results are 14, 15 always?

Reply: If you view the iPages.ToString() you will get something like "System.String[]" Or "System.Int32[]" it doesn't actually print what is contained in the array

Comment:

int intLength = "System.Int32[]".Length;
Assert.IsTrue(intLength==14);