As a suggestion - the string concatenation operator is provided by the
C# compiler, not the String class; this allows "a" + "b" + "c" + "d"
etc to be a single call (to String.Concat), not successive add
operations.

This might also refer to CLS compliance?

Marc

Of course, re my last post, you could argue that this *is* supported,
precisely by calling string.Concat()...

Marc

Fister,

   One can interpret the first statement:

Some features are supported by.NET but not by C#

   To mean that features that you see in the language are not necessarily
implemented in the language, but rather, in the framework.  In this case, I
would say the type aliases, like int, string, etc, etc.  The functionality
is provided by the framework.

   As for the second statement, regarding operator overloading, .NET
doesn't support it outright.  The language picks it up through specially
named static method signatures.  VB now honors this convention as well, but
the framework doesn't enforce it.

   I do think that the author could have phrased the second part a little
better.

They might be referring to features built into the CLR, and not exposed by
the C# language, but which might be used/exposed in some other .NET
language.

I'm not expert enough to give an example, but it *might* be that the CLR has
direct support for pointers and associated logic in order to implement C++,
but such features are not used/exposed/"supported" by C#.