Possible Duplicate:
How to name C# source files for generic classes
Today I noticed that while watching built-in generic class\interface metadata in VS2010 the window name contains the exact (well, missing out
keyword) name of the class/interface, i.e.:
Then I tried to name my own cs file, containing a generic class, accordingly, say Foo<T>.cs
and got an error, saying that <
and >
are not acceptable.
So, intuitively I can see that, while displaying built-in class/interface metadata the name of the window can be substituted by the IDE. It's OK. But is there any naming convention (some best practise) for the names of the files, containg generics, within a project. That is, if I had both Foo<T>
and Foo
, am I expected to keep them in separate files and how should I name these file then?