++ @Herbie and @blowdart
1 class per file - generally. Break the rule when it makes sense
In addition to the rationale already given, it eases team work - especially if your source control employs a "Lock model".
@Maddus LOL you kill me ![]()
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
++ @Herbie and @blowdart
1 class per file - generally. Break the rule when it makes sense
In addition to the rationale already given, it eases team work - especially if your source control employs a "Lock model".
@Maddus LOL you kill me ![]()