Environment versions
Network:
Windows 2000 Server
Hi,
If the class hierarchies are reasonably shallow there may be a case for putting the classes in the same .cs. Advantage is that you can use source control to make sure, for example, that incompatable changes aren't made to a parent class whilst working on a derived class.
Just my .02c,
Viv
>Coding in C#, which is a better practice: put one class per file and allow the file share the same name as class name (like in Java) or put multiple classes in a file (like in VFP)?
>
>I'm inclined toward the former since it's easier to find a class by just looking at the file name.
>
>Any suggestions or comments will be appreciated!
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only