>I did not know that. Personally I would probably change the ReadOnly enum slightly, to Read_Only for instance, in a way that makes the meaning clear without conflicting with a reserved word, but that's useful to know. Thanks.

I am filtering near 30 reserved words for SQL Server SQL commands. So, everytime there is a reserved word that I need to take care of, I wouldn't want to do it in the code but let the framework decide to adjust on its own. As for SQL Server SQL commands, on that one, there is just no possibility of changing a word. So, it would also end up like [Table] if I have a table named Table. I believe it is important that the developer relies on the commonly used word instead of trying to know what is its mirroring representation. In this case, it is an enumeration. Thus, in the application code, we simply use Framework.FileAttribute.ReadOnly, Framework.FileAttribute.System and Framework.FileAttribute.Hidden. I wouldn't really do not want to have in there Framework.FileAttribute.Read_Only.