10 DEBUG;TRACE 06/30/2010 12:43:56 0 02/12/2011 16:12:50 456 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False All using directives must be placed inside of the namespace. 1 False All using directives must be placed inside of the namespace. 2 False The class must have a documentation header. 6 False The class must have an access modifier. 6 False The field must have a documentation header. 8 False The variable name 'mDisposed' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 8 False The constructor must have a documentation header. 10 False Variable names must start with a lower-case letter: CloneTable. 10 False The call to mDisposed must begin with the 'this.' prefix to indicate that the item is a member of the class. 13 False The method must have a documentation header. 16 False The call to Dispose must begin with the 'this.' prefix to indicate that the item is a member of the class. 18 False The method must have a documentation header. 22 False Variable names must start with a lower-case letter: Disposing. 22 False The call to mDisposed must begin with the 'this.' prefix to indicate that the item is a member of the class. 26 False The call to Clear should only use the 'base.' prefix if the item is declared virtual in the base class and an override is defined in the local class. Otherwise, prefix the call with this rather than base. 29 False 06/30/2010 12:43:56 0 02/14/2011 14:45:13 578 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False All using directives must be placed inside of the namespace. 1 False All using directives must be placed inside of the namespace. 2 False All using directives must be placed inside of the namespace. 3 False The class must have a documentation header. 7 False The class must have an access modifier. 7 False The field must have a documentation header. 9 False Fields must be declared with private access. Use properties to expose fields. 9 False Public and internal fields must start with an upper-case letter: data. 9 False The constructor must have a documentation header. 11 False An else, catch, or finally statement must not be preceded by a blank line. 49 False The call to data must begin with the 'this.' prefix to indicate that the item is a member of the class. 13 False The call to data must begin with the 'this.' prefix to indicate that the item is a member of the class. 40 False Use string.Empty rather than "". 24 False 06/30/2010 12:43:56 0 02/26/2011 16:00:42 489 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False All using directives must be placed inside of the namespace. 1 False All using directives must be placed inside of the namespace. 2 False All using directives must be placed inside of the namespace. 3 False All using directives must be placed inside of the namespace. 4 False All using directives must be placed inside of the namespace. 5 False The class must have a documentation header. 9 False The field must have a documentation header. 11 False The variable name 'mDisabled' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 11 False The method must have a documentation header. 13 False The body of the if statement must be wrapped in opening and closing curly brackets. 16 False Variable names must start with a lower-case letter: Line. 13 False The method must have a documentation header. 19 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 28 False Variable names must start with a lower-case letter: Msg. 24 False A line may only contain a single statement. 28 False The method must have a documentation header. 33 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 44 False Variable names must start with a lower-case letter: Msg. 38 False A line may only contain a single statement. 44 False The method must have a documentation header. 47 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 56 False Variable names must start with a lower-case letter: Msg. 52 False A line may only contain a single statement. 56 False The method must have a documentation header. 61 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 70 False Variable names must start with a lower-case letter: Msg. 66 False A line may only contain a single statement. 70 False The method must have a documentation header. 75 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 84 False Variable names must start with a lower-case letter: Msg. 80 False A line may only contain a single statement. 84 False The method must have a documentation header. 89 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 99 False Variable names must start with a lower-case letter: Exception. 89 False Variable names must start with a lower-case letter: Msg. 94 False A line may only contain a single statement. 99 False The method must have a documentation header. 102 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 113 False Variable names must start with a lower-case letter: Packet. 102 False Variable names must start with a lower-case letter: Msg. 108 False A line may only contain a single statement. 113 False The method must have a documentation header. 116 False Statements or elements wrapped in curly brackets must be followed by a blank line. 125 False Statements or elements wrapped in curly brackets must be followed by a blank line. 130 False Statements or elements wrapped in curly brackets must be followed by a blank line. 135 False Statements or elements wrapped in curly brackets must be followed by a blank line. 143 False Statements or elements wrapped in curly brackets must be followed by a blank line. 148 False Statements or elements wrapped in curly brackets must be followed by a blank line. 153 False Variable names must start with a lower-case letter: ExceptionData. 118 False The variable name 'pException' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 116 False Variable names must start with a lower-case letter: Entry. 139 False The method must have a documentation header. 159 False The method must have a documentation header. 165 False 06/30/2010 12:43:56 0 02/26/2011 16:00:42 558 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False All using directives must be placed inside of the namespace. 1 False All using directives must be placed inside of the namespace. 2 False All using directives must be placed inside of the namespace. 3 False All using directives must be placed inside of the namespace. 4 False All using directives must be placed inside of the namespace. 5 False All using directives must be placed inside of the namespace. 6 False All using directives must be placed inside of the namespace. 7 False All using directives must be placed inside of the namespace. 8 False The class must have a documentation header. 12 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 18 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 215 False The class must have an access modifier. 12 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 18 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 205 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 206 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 215 False The field must have a documentation header. 14 False Variable names must start with a lower-case letter: Configuration. 14 False All private fields must be placed after all internal fields. 20 False The field must have a documentation header. 15 False Variable names must start with a lower-case letter: DatabaseManager. 15 False The field must have a documentation header. 16 False Variable names must start with a lower-case letter: DefaultEncoding. 16 False The field must have a documentation header. 17 False Variable names must start with a lower-case letter: ConnectionManager. 17 False The field must have a documentation header. 19 False Variable names must start with a lower-case letter: Game. 19 False The field must have a documentation header. 20 False Fields must be declared with private access. Use properties to expose fields. 20 False The property must have a documentation header. 22 False All properties must be placed after all fields. 253 False The method must have a documentation header. 30 False The code must not contain multiple blank lines in a row. 70 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 73 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 77 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 77 False A closing curly bracket must not be preceded by a blank line. 90 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 88 False An else, catch, or finally statement must not be preceded by a blank line. 92 False An else, catch, or finally statement must not be preceded by a blank line. 103 False Variable names must start with a lower-case letter: Start. 55 False The variable name 'dbServer' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 57 False Variable names must start with a lower-case letter: TimeUsed. 84 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 71 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 77 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 88 False The method must have a documentation header. 115 False The line contains unnecessary parenthesis. 117 False Variable names must start with a lower-case letter: Enum. 115 False The method must have a documentation header. 120 False Variable names must start with a lower-case letter: Bool. 120 False The method must have a documentation header. 130 False Variable names must start with a lower-case letter: Quick. 132 False Variable names must start with a lower-case letter: Min. 130 False The method must have a documentation header. 136 False The line contains unnecessary parenthesis. 138 False Use the built-in type alias 'double' rather than Double or System.Double. 136 False The method must have a documentation header. 142 False Variable names must start with a lower-case letter: Input. 142 False The method must have a documentation header. 147 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 151 False Variable names must start with a lower-case letter: Input. 147 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 151 False The method must have a documentation header. 162 False The line contains unnecessary parenthesis. 171 False The method must have a documentation header. 180 False The method must have a documentation header. 185 False The method must have a documentation header. 190 False The method must have a documentation header. 195 False The method must have a documentation header. 200 False The method must have a documentation header. 217 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 245 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 232 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 240 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 242 False A line may only contain a single statement. 245 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 232 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 240 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 242 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 243 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 250 False The field must have a documentation header. 253 False Variable names must start with a lower-case letter: ShutdownInitiated. 253 False The method must have a documentation header. 255 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 263 False Variable names must start with a lower-case letter: Message. 255 False Variable names must start with a lower-case letter: HotelAlert. 259 False A line may only contain a single statement. 263 False The method must have a documentation header. 266 False The method must have a documentation header. 271 False The body of the if statement must be wrapped in opening and closing curly brackets. 274 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 306 False The body of the if statement must be wrapped in opening and closing curly brackets. 310 False Variable names must start with a lower-case letter: ExitWhenDone. 271 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 287 False A line may only contain a single statement. 306 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 304 False 06/30/2010 12:43:56 0 02/26/2011 16:00:42 470 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False The class must have a documentation header. 4 False The class must have an access modifier. 4 False The field must have a documentation header. 6 False Fields must be declared with private access. Use properties to expose fields. 6 False The field must have a documentation header. 7 False Fields must be declared with private access. Use properties to expose fields. 7 False The field must have a documentation header. 8 False Fields must be declared with private access. Use properties to expose fields. 8 False The field must have a documentation header. 9 False Fields must be declared with private access. Use properties to expose fields. 9 False The field must have a documentation header. 10 False Fields must be declared with private access. Use properties to expose fields. 10 False The field must have a documentation header. 11 False Fields must be declared with private access. Use properties to expose fields. 11 False The constructor must have a documentation header. 13 False Variable names must start with a lower-case letter: Id. 13 False 06/30/2010 12:43:56 0 02/26/2011 16:00:42 476 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False All using directives must be placed inside of the namespace. 1 False All using directives must be placed inside of the namespace. 2 False All using directives must be placed inside of the namespace. 3 False The struct must have a documentation header. 7 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 9 False The field must have a documentation header. 12 False The constructor must have a documentation header. 18 False The call to target must begin with the 'this.' prefix to indicate that the item is a member of the class. 20 False The method must have a documentation header. 23 False All internal methods must be placed after all public methods. 41 False The method must have a documentation header. 28 False Statements or elements wrapped in curly brackets must be followed by a blank line. 35 False The method must have a documentation header. 41 False The call to target must begin with the 'this.' prefix to indicate that the item is a member of the class. 43 False The class must have a documentation header. 49 False The constructor must have a documentation header. 51 False The constructor must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 53 False The constructor must have a documentation header. 54 False Adjacent elements must be separated by a blank line. 54 False The constructor must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 56 False The variable name 'pInfo' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 54 False All protected constructors must be placed after all public constructors. 57 False All protected constructors must be placed after all public constructors. 60 False The constructor must have a documentation header. 57 False Adjacent elements must be separated by a blank line. 57 False The constructor must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 59 False The variable name 'pException' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 57 False The constructor must have a documentation header. 60 False Adjacent elements must be separated by a blank line. 60 False The constructor must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 62 False The variable name 'pException' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 60 False 06/30/2010 12:43:56 0 02/26/2011 16:00:42 464 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False All using directives must be placed inside of the namespace. 1 False All using directives must be placed inside of the namespace. 2 False All using directives must be placed inside of the namespace. 3 False All using directives must be placed inside of the namespace. 4 False All using directives must be placed inside of the namespace. 5 False All using directives must be placed inside of the namespace. 6 False All using directives must be placed inside of the namespace. 7 False The class must have a documentation header. 11 False The class must have an access modifier. 11 False The field must have a documentation header. 13 False Fields must be declared with private access. Use properties to expose fields. 13 False The constructor must have a documentation header. 15 False The method must have a documentation header. 20 False Variable names must start with a lower-case letter: Data. 23 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 20 False Variable names must start with a lower-case letter: Row. 32 False All static internal methods must be placed before all non-static internal methods. 38 False All static internal methods must be placed before all non-static internal methods. 181 False All static internal methods must be placed before all non-static internal methods. 186 False The call to Achievements must begin with the 'this.' prefix to indicate that the item is a member of the class. 22 False The call to Achievements must begin with the 'this.' prefix to indicate that the item is a member of the class. 34 False The method must have a documentation header. 38 False Variable names must start with a lower-case letter: Session. 38 False Use the built-in type alias 'bool' rather than Boolean or System.Boolean. 38 False The method must have a documentation header. 53 False Variable names must start with a lower-case letter: AchievementsToList. 55 False Variable names must start with a lower-case letter: NextAchievementLevels. 56 False Variable names must start with a lower-case letter: Message. 80 False Variable names must start with a lower-case letter: Session. 53 False Variable names must start with a lower-case letter: Achievement. 60 False Variable names must start with a lower-case letter: Achievement. 83 False Variable names must start with a lower-case letter: Level. 85 False The call to Achievements must begin with the 'this.' prefix to indicate that the item is a member of the class. 60 False The call to Achievements must begin with the 'this.' prefix to indicate that the item is a member of the class. 58 False The method must have a documentation header. 95 False Variable names must start with a lower-case letter: Achievement. 98 False Variable names must start with a lower-case letter: Value. 107 False Variable names must start with a lower-case letter: Session. 95 False Variable names must start with a lower-case letter: BadgesToRemove. 112 False Variable names must start with a lower-case letter: Badge. 114 False Variable names must start with a lower-case letter: Badge. 122 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 136 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 145 False The call to Achievements must begin with the 'this.' prefix to indicate that the item is a member of the class. 98 False Use string.Empty rather than "". 163 False The method must have a documentation header. 181 False The line contains unnecessary parenthesis. 183 False Variable names must start with a lower-case letter: BaseValue. 181 False The method must have a documentation header. 186 False Variable names must start with a lower-case letter: BadgeTemplate. 186 False 06/30/2010 12:43:56 0 02/26/2011 16:00:42 457 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False All using directives must be placed inside of the namespace. 1 False All using directives must be placed inside of the namespace. 2 False All using directives must be placed inside of the namespace. 4 False The class must have a documentation header. 8 False The class must have an access modifier. 8 False The field must have a documentation header. 10 False Fields must be declared with private access. Use properties to expose fields. 10 False The constructor must have a documentation header. 12 False The call to RoomAdvertisements must begin with the 'this.' prefix to indicate that the item is a member of the class. 14 False The method must have a documentation header. 17 False Statements or elements wrapped in curly brackets must be followed by a blank line. 33 False Variable names must start with a lower-case letter: Data. 21 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 17 False Variable names must start with a lower-case letter: Row. 28 False All method parameters must be placed on the same line, or each parameter must be placed on a separate line. 30 False If the method parameters are on separate lines, the first parameter must begin on the line beneath the name of the method. 30 False The parameter must begin on the line after the previous parameter. 30 False The parameter must begin on the line after the previous parameter. 31 False The call to RoomAdvertisements must begin with the 'this.' prefix to indicate that the item is a member of the class. 19 False The call to RoomAdvertisements must begin with the 'this.' prefix to indicate that the item is a member of the class. 30 False The method must have a documentation header. 34 False Adjacent elements must be separated by a blank line. 34 False Variable names must start with a lower-case letter: RndId. 43 False The call to RoomAdvertisements must begin with the 'this.' prefix to indicate that the item is a member of the class. 36 False The call to RoomAdvertisements must begin with the 'this.' prefix to indicate that the item is a member of the class. 43 False The call to RoomAdvertisements must begin with the 'this.' prefix to indicate that the item is a member of the class. 47 False The call to RoomAdvertisements must begin with the 'this.' prefix to indicate that the item is a member of the class. 45 False 06/30/2010 12:43:56 0 02/26/2011 16:00:42 482 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False All using directives must be placed inside of the namespace. 1 False The class must have a documentation header. 5 False The constructor must have a documentation header. 9 False The constructor must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 9 False All constructors must be placed after all fields. 21 False All constructors must be placed after all fields. 23 False The constructor must have a documentation header. 11 False The call to i must begin with the 'this.' prefix to indicate that the item is a member of the class. 14 False The field must have a documentation header. 21 False Constants must start with an upper-case letter: a. 21 False The field must have a documentation header. 23 False The method must have a documentation header. 29 False A closing curly bracket must not be preceded by a blank line. 38 False The use of regions is not allowed within code elements. Remove the #region and #endregion tags. 31 False The call to i must begin with the 'this.' prefix to indicate that the item is a member of the class. 33 False The call to i must begin with the 'this.' prefix to indicate that the item is a member of the class. 34 False The class must have a documentation header. 43 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 68 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 140 False A C# document may only contain a single class at the root level unless all of the classes are partial and are of the same type. 43 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 60 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 61 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 63 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 65 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 66 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 68 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 130 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 131 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 134 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 136 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 137 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 140 False The constructor must have a documentation header. 47 False The constructor must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 47 False The constructor must have a documentation header. 49 False The constructor must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 49 False The method must have a documentation header. 55 False All protected methods must be placed after all public methods. 74 False All protected methods must be placed after all public methods. 76 False All protected methods must be placed after all public methods. 81 False All protected methods must be placed after all public methods. 86 False All protected methods must be placed after all public methods. 91 False All static protected methods must be placed before all non-static protected methods. 142 False The method must have a documentation header. 74 False The method must have a documentation header. 76 False The call to Next must begin with the 'this.' prefix to indicate that the item is a member of the class. 78 False The method must have a documentation header. 81 False Insert parenthesis within the arithmetic expression to declare the operator precedence. 83 False The call to Sample must begin with the 'this.' prefix to indicate that the item is a member of the class. 83 False The method must have a documentation header. 86 False The call to Sample must begin with the 'this.' prefix to indicate that the item is a member of the class. 88 False The method must have a documentation header. 91 False An opening curly bracket must not be followed by a blank line. 94 False The call to Next must begin with the 'this.' prefix to indicate that the item is a member of the class. 101 False The call to Next must begin with the 'this.' prefix to indicate that the item is a member of the class. 109 False The method must have a documentation header. 119 False An opening curly bracket must not be followed by a blank line. 120 False The call to Next must begin with the 'this.' prefix to indicate that the item is a member of the class. 123 False The method must have a documentation header. 142 False A closing curly bracket must not be preceded by a blank line. 146 False Use the built-in type alias 'int' rather than Int32 or System.Int32. 142 False 06/30/2010 12:43:56 0 02/26/2011 16:00:42 451 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False All using directives must be placed inside of the namespace. 1 False All using directives must be placed inside of the namespace. 3 False The class must have a documentation header. 7 False The class must have an access modifier. 7 False The field must have a documentation header. 9 False Fields must be declared with private access. Use properties to expose fields. 9 False The field must have a documentation header. 10 False Fields must be declared with private access. Use properties to expose fields. 10 False The field must have a documentation header. 11 False Fields must be declared with private access. Use properties to expose fields. 11 False The field must have a documentation header. 12 False Fields must be declared with private access. Use properties to expose fields. 12 False The field must have a documentation header. 13 False Fields must be declared with private access. Use properties to expose fields. 13 False The property must have a documentation header. 15 False All properties must be placed after all constructors. 33 False Use the built-in type alias 'bool' rather than Boolean or System.Boolean. 15 False The call to ViewsLimit must begin with the 'this.' prefix to indicate that the item is a member of the class. 19 False The call to Views must begin with the 'this.' prefix to indicate that the item is a member of the class. 24 False The constructor must have a documentation header. 33 False Variable names must start with a lower-case letter: Id. 33 False The method must have a documentation header. 42 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 46 False The call to Id must begin with the 'this.' prefix to indicate that the item is a member of the class. 48 False 06/30/2010 12:43:56 0 02/26/2011 16:00:42 439 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False All using directives must be placed inside of the namespace. 2 False The class must have a documentation header. 6 False The class must have an access modifier. 6 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 8 False The field must have a documentation header. 9 False Fields must be declared with private access. Use properties to expose fields. 9 False The field must have a documentation header. 10 False Fields must be declared with private access. Use properties to expose fields. 10 False The field must have a documentation header. 11 False Fields must be declared with private access. Use properties to expose fields. 11 False The constructor must have a documentation header. 13 False Variable names must start with a lower-case letter: DisplayId. 13 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 15 False The method must have a documentation header. 21 False 06/30/2010 12:43:56 0 02/12/2011 16:13:07 70 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False All using directives must be placed inside of the namespace. 1 False All using directives must be placed inside of the namespace. 2 False All using directives must be placed inside of the namespace. 3 False All using directives must be placed inside of the namespace. 4 False The class must have a documentation header. 8 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 17 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 17 False The class must have an access modifier. 8 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 17 False The field must have a documentation header. 10 False Fields must be declared with private access. Use properties to expose fields. 10 False The field must have a documentation header. 11 False Fields must be declared with private access. Use properties to expose fields. 11 False The field must have a documentation header. 12 False Fields must be declared with private access. Use properties to expose fields. 12 False The field must have a documentation header. 13 False Fields must be declared with private access. Use properties to expose fields. 13 False The field must have a documentation header. 14 False Fields must be declared with private access. Use properties to expose fields. 14 False The field must have a documentation header. 15 False Fields must be declared with private access. Use properties to expose fields. 15 False The field must have a documentation header. 16 False Fields must be declared with private access. Use properties to expose fields. 16 False The property must have a documentation header. 19 False All properties must be placed after all constructors. 27 False Use the built-in type alias 'bool' rather than Boolean or System.Boolean. 19 False The line contains unnecessary parenthesis. 23 False The call to ItemIds must begin with the 'this.' prefix to indicate that the item is a member of the class. 23 False The constructor must have a documentation header. 27 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 42 False Variable names must start with a lower-case letter: Id. 27 False The variable name 'pPageID' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 27 False Variable names must start with a lower-case letter: ItemId. 34 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 42 False The method must have a documentation header. 45 False The call to IsDeal must begin with the 'this.' prefix to indicate that the item is a member of the class. 47 False The call to ItemIds must begin with the 'this.' prefix to indicate that the item is a member of the class. 52 False The method must have a documentation header. 55 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 57 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 62 False Variable names must start with a lower-case letter: Message. 55 False The call to Id must begin with the 'this.' prefix to indicate that the item is a member of the class. 64 False The call to IsDeal must begin with the 'this.' prefix to indicate that the item is a member of the class. 59 False The call to Id must begin with the 'this.' prefix to indicate that the item is a member of the class. 68 False The call to Name must begin with the 'this.' prefix to indicate that the item is a member of the class. 69 False The call to CreditsCost must begin with the 'this.' prefix to indicate that the item is a member of the class. 70 False The call to PixelsCost must begin with the 'this.' prefix to indicate that the item is a member of the class. 71 False The call to GetBaseItem must begin with the 'this.' prefix to indicate that the item is a member of the class. 73 False The call to GetBaseItem must begin with the 'this.' prefix to indicate that the item is a member of the class. 74 False The call to Amount must begin with the 'this.' prefix to indicate that the item is a member of the class. 76 False Use string.Empty rather than "". 75 False 06/30/2010 12:43:56 0 02/26/2011 16:00:42 426 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False All using directives must be placed inside of the namespace. 1 False All using directives must be placed inside of the namespace. 2 False All using directives must be placed inside of the namespace. 3 False All using directives must be placed inside of the namespace. 4 False All using directives must be placed inside of the namespace. 5 False The class must have a documentation header. 9 False The class must have an access modifier. 9 False The method must have a documentation header. 11 False Variable names must start with a lower-case letter: Code. 11 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 13 False All private methods must be placed after all internal methods. 11 False All private methods must be placed after all internal methods. 53 False Use the built-in type alias 'bool' rather than Boolean or System.Boolean. 11 False The method must have a documentation header. 26 False Variable names must start with a lower-case letter: Data. 28 False Variable names must start with a lower-case letter: Code. 26 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 30 False The method must have a documentation header. 44 False Variable names must start with a lower-case letter: Code. 44 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 46 False The method must have a documentation header. 53 False Variable names must start with a lower-case letter: Value. 63 False Variable names must start with a lower-case letter: Session. 53 False Variable names must start with a lower-case letter: Error. 57 False 06/30/2010 12:43:56 0 02/26/2011 16:00:42 445 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False All using directives must be placed inside of the namespace. 1 False All using directives must be placed inside of the namespace. 2 False All using directives must be placed inside of the namespace. 3 False The class must have a documentation header. 7 False The class must have an access modifier. 7 False The field must have a documentation header. 9 False Variable names must start with a lower-case letter: Id. 9 False All private fields must be placed after all internal fields. 9 False The field must have a documentation header. 10 False Fields must be declared with private access. Use properties to expose fields. 10 False The field must have a documentation header. 12 False Fields must be declared with private access. Use properties to expose fields. 12 False The field must have a documentation header. 14 False Fields must be declared with private access. Use properties to expose fields. 14 False The field must have a documentation header. 15 False Fields must be declared with private access. Use properties to expose fields. 15 False The field must have a documentation header. 16 False Fields must be declared with private access. Use properties to expose fields. 16 False The field must have a documentation header. 18 False Fields must be declared with private access. Use properties to expose fields. 18 False The field must have a documentation header. 19 False Fields must be declared with private access. Use properties to expose fields. 19 False The field must have a documentation header. 21 False Fields must be declared with private access. Use properties to expose fields. 21 False The field must have a documentation header. 22 False Fields must be declared with private access. Use properties to expose fields. 22 False The field must have a documentation header. 24 False Fields must be declared with private access. Use properties to expose fields. 24 False The field must have a documentation header. 26 False Fields must be declared with private access. Use properties to expose fields. 26 False The field must have a documentation header. 27 False Fields must be declared with private access. Use properties to expose fields. 27 False The field must have a documentation header. 28 False Fields must be declared with private access. Use properties to expose fields. 28 False The field must have a documentation header. 30 False Fields must be declared with private access. Use properties to expose fields. 30 False The field must have a documentation header. 31 False Fields must be declared with private access. Use properties to expose fields. 31 False The field must have a documentation header. 32 False Fields must be declared with private access. Use properties to expose fields. 32 False The field must have a documentation header. 33 False Fields must be declared with private access. Use properties to expose fields. 33 False The field must have a documentation header. 35 False Fields must be declared with private access. Use properties to expose fields. 35 False The field must have a documentation header. 37 False The variable name 'mMessage' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 37 False The property must have a documentation header. 39 False All properties must be placed after all constructors. 47 False The call to Id must begin with the 'this.' prefix to indicate that the item is a member of the class. 43 False The constructor must have a documentation header. 47 False The body of the if statement must be wrapped in opening and closing curly brackets. 93 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 88 False Variable names must start with a lower-case letter: Id. 47 False Variable names must start with a lower-case letter: ComingSoon. 48 False Variable names must start with a lower-case letter: LayoutTeaser. 49 False Variable names must start with a lower-case letter: TextTeaser. 50 False Variable names must start with a lower-case letter: Item. 90 False All constructor parameters must be placed on the same line, or each parameter must be placed on a separate line. 47 False If the constructor parameters are on separate lines, the first parameter must begin on the line beneath the name of the constructor. 47 False The parameter must begin on the line after the previous parameter. 47 False The parameter must begin on the line after the previous parameter. 48 False The parameter must begin on the line after the previous parameter. 49 False The parameter must begin on the line after the previous parameter. 50 False The call to Items must begin with the 'this.' prefix to indicate that the item is a member of the class. 52 False The call to Items must begin with the 'this.' prefix to indicate that the item is a member of the class. 93 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 73 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 77 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 78 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 86 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 88 False The method must have a documentation header. 97 False All methods must be placed after all properties. 118 False The call to mMessage must begin with the 'this.' prefix to indicate that the item is a member of the class. 99 False The method must have a documentation header. 102 False Variable names must start with a lower-case letter: Item. 106 False The call to Items must begin with the 'this.' prefix to indicate that the item is a member of the class. 106 False The call to Items must begin with the 'this.' prefix to indicate that the item is a member of the class. 104 False The property must have a documentation header. 118 False The call to mMessage must begin with the 'this.' prefix to indicate that the item is a member of the class. 122 False The method must have a documentation header. 126 False Variable names must start with a lower-case letter: Rank. 126 False The call to Visible must begin with the 'this.' prefix to indicate that the item is a member of the class. 128 False The call to IconColor must begin with the 'this.' prefix to indicate that the item is a member of the class. 129 False The call to IconImage must begin with the 'this.' prefix to indicate that the item is a member of the class. 130 False The call to Id must begin with the 'this.' prefix to indicate that the item is a member of the class. 131 False The call to Caption must begin with the 'this.' prefix to indicate that the item is a member of the class. 132 False The call to ComingSoon must begin with the 'this.' prefix to indicate that the item is a member of the class. 133 False The call to Id must begin with the 'this.' prefix to indicate that the item is a member of the class. 134 False 06/30/2010 12:43:56 0 02/26/2011 16:00:42 432 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False All using directives must be placed inside of the namespace. 1 False All using directives must be placed inside of the namespace. 2 False All using directives must be placed inside of the namespace. 3 False All using directives must be placed inside of the namespace. 4 False All using directives must be placed inside of the namespace. 5 False All using directives must be placed inside of the namespace. 6 False All using directives must be placed inside of the namespace. 7 False The class must have a documentation header. 11 False The class must have an access modifier. 11 False The method must have a documentation header. 13 False Variable names must start with a lower-case letter: Item. 13 False Use the built-in type alias 'bool' rather than Boolean or System.Boolean. 13 False The method must have a documentation header. 23 False Variable names must start with a lower-case letter: Item. 25 False Variable names must start with a lower-case letter: Comission. 36 False Variable names must start with a lower-case letter: TotalPrice. 37 False Variable names must start with a lower-case letter: ItemType. 38 False Variable names must start with a lower-case letter: Session. 23 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 45 False The method must have a documentation header. 59 False Variable names must start with a lower-case letter: SellingPrice. 59 False The method must have a documentation header. 64 False Use the built-in type alias 'double' rather than Double or System.Double. 64 False The method must have a documentation header. 69 False The method must have a documentation header. 74 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 76 False Variable names must start with a lower-case letter: Data. 78 False Variable names must start with a lower-case letter: WhereClause. 79 False Variable names must start with a lower-case letter: OrderMode. 80 False Variable names must start with a lower-case letter: Message. 120 False Variable names must start with a lower-case letter: MinCost. 74 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 108 False Variable names must start with a lower-case letter: Row. 126 False Use the built-in type alias 'string' rather than String or System.String. 74 False Use string.Empty rather than "". 80 False Use string.Empty rather than "". 132 False The method must have a documentation header. 147 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 170 False Variable names must start with a lower-case letter: Profits. 149 False Variable names must start with a lower-case letter: HabboId. 147 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 151 False Variable names must start with a lower-case letter: Data. 153 False Variable names must start with a lower-case letter: RawProfit. 154 False Variable names must start with a lower-case letter: Message. 161 False Variable names must start with a lower-case letter: Row. 168 False Variable names must start with a lower-case letter: MinutesLeft. 172 False Use the built-in type alias 'string' rather than String or System.String. 154 False Use the built-in type alias 'double' rather than Double or System.Double. 172 False Use string.Empty rather than "". 185 False 06/30/2010 12:43:56 0 02/26/2011 16:06:04 42 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False The code must not contain multiple blank lines in a row. 18 False All using directives must be placed inside of the namespace. 1 False All using directives must be placed inside of the namespace. 2 False All using directives must be placed inside of the namespace. 3 False All using directives must be placed inside of the namespace. 4 False All using directives must be placed inside of the namespace. 5 False All using directives must be placed inside of the namespace. 6 False All using directives must be placed inside of the namespace. 7 False All using directives must be placed inside of the namespace. 8 False All using directives must be placed inside of the namespace. 9 False All using directives must be placed inside of the namespace. 10 False All using directives must be placed inside of the namespace. 11 False All using directives must be placed inside of the namespace. 12 False All using directives must be placed inside of the namespace. 13 False All using directives must be placed inside of the namespace. 14 False All using directives must be placed inside of the namespace. 15 False All using directives must be placed inside of the namespace. 16 False The class must have a documentation header. 21 False The class must have an access modifier. 21 False The field must have a documentation header. 23 False Variable names must start with a lower-case letter: ClientManager. 23 False The field must have a documentation header. 24 False Variable names must start with a lower-case letter: BanManager. 24 False The field must have a documentation header. 25 False Variable names must start with a lower-case letter: RoleManager. 25 False The field must have a documentation header. 26 False Variable names must start with a lower-case letter: HelpTool. 26 False The field must have a documentation header. 27 False Variable names must start with a lower-case letter: Catalog. 27 False The field must have a documentation header. 28 False Variable names must start with a lower-case letter: Navigator. 28 False The field must have a documentation header. 29 False Variable names must start with a lower-case letter: ItemManager. 29 False The field must have a documentation header. 30 False Variable names must start with a lower-case letter: RoomManager. 30 False The field must have a documentation header. 31 False Variable names must start with a lower-case letter: AdvertisementManager. 31 False The field must have a documentation header. 32 False Variable names must start with a lower-case letter: PixelManager. 32 False The field must have a documentation header. 33 False Variable names must start with a lower-case letter: AchievementManager. 33 False The field must have a documentation header. 34 False Variable names must start with a lower-case letter: ModerationTool. 34 False The field must have a documentation header. 35 False Variable names must start with a lower-case letter: BotManager. 35 False The field must have a documentation header. 36 False Variable names must start with a lower-case letter: StatisticsThread. 36 False The field must have a documentation header. 37 False The variable name 'mNavicache' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 37 False The constructor must have a documentation header. 39 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 54 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 54 False Variable names must start with a lower-case letter: Start. 48 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 50 False Variable names must start with a lower-case letter: TimeUsed. 52 False The call to ClientManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 41 False The call to ClientManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 45 False The call to BanManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 56 False The call to RoleManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 57 False The call to HelpTool must begin with the 'this.' prefix to indicate that the item is a member of the class. 58 False The call to Catalog must begin with the 'this.' prefix to indicate that the item is a member of the class. 59 False The call to Navigator must begin with the 'this.' prefix to indicate that the item is a member of the class. 60 False The call to ItemManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 61 False The call to RoomManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 62 False The call to AdvertisementManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 63 False The call to PixelManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 64 False The call to AchievementManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 65 False The call to ModerationTool must begin with the 'this.' prefix to indicate that the item is a member of the class. 66 False The call to BotManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 67 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 54 False The method must have a documentation header. 71 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 83 False Statements or elements wrapped in curly brackets must be followed by a blank line. 151 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 153 False Variable names must start with a lower-case letter: Start. 73 False Variable names must start with a lower-case letter: TimeUsed. 74 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 75 False All static internal methods must be placed before all non-static internal methods. 163 False The call to BanManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 78 False The call to RoleManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 84 False The call to HelpTool must begin with the 'this.' prefix to indicate that the item is a member of the class. 89 False The call to HelpTool must begin with the 'this.' prefix to indicate that the item is a member of the class. 90 False The call to Catalog must begin with the 'this.' prefix to indicate that the item is a member of the class. 95 False The call to Navigator must begin with the 'this.' prefix to indicate that the item is a member of the class. 100 False The call to ItemManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 105 False The call to RoomManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 110 False The call to RoomManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 111 False The call to mNavicache must begin with the 'this.' prefix to indicate that the item is a member of the class. 112 False The call to AdvertisementManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 117 False The call to PixelManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 122 False The call to AchievementManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 127 False The call to ModerationTool must begin with the 'this.' prefix to indicate that the item is a member of the class. 132 False The call to ModerationTool must begin with the 'this.' prefix to indicate that the item is a member of the class. 133 False The call to BotManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 138 False The call to Catalog must begin with the 'this.' prefix to indicate that the item is a member of the class. 143 False The call to StatisticsThread must begin with the 'this.' prefix to indicate that the item is a member of the class. 152 False The call to StatisticsThread must begin with the 'this.' prefix to indicate that the item is a member of the class. 155 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 83 False The method must have a documentation header. 163 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 169 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 163 False The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 167 False The method must have a documentation header. 174 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 179 False Statements or elements wrapped in curly brackets must be followed by a blank line. 184 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 205 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 181 False The call to GetClientManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 188 False The call to GetClientManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 185 False The call to PixelManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 193 False The call to GetPixelManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 191 False The method must have a documentation header. 210 False The call to ClientManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 212 False The method must have a documentation header. 215 False The call to BanManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 217 False The method must have a documentation header. 220 False The call to RoleManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 222 False The method must have a documentation header. 225 False The call to HelpTool must begin with the 'this.' prefix to indicate that the item is a member of the class. 227 False The method must have a documentation header. 230 False The call to Catalog must begin with the 'this.' prefix to indicate that the item is a member of the class. 232 False The method must have a documentation header. 235 False The call to Navigator must begin with the 'this.' prefix to indicate that the item is a member of the class. 237 False The method must have a documentation header. 240 False The call to ItemManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 242 False The method must have a documentation header. 245 False The call to RoomManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 247 False The method must have a documentation header. 250 False The call to AdvertisementManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 252 False The method must have a documentation header. 255 False The call to PixelManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 257 False The method must have a documentation header. 260 False The call to AchievementManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 262 False The method must have a documentation header. 265 False The call to ModerationTool must begin with the 'this.' prefix to indicate that the item is a member of the class. 267 False The method must have a documentation header. 270 False The call to BotManager must begin with the 'this.' prefix to indicate that the item is a member of the class. 272 False The method must have a documentation header. 275 False The call to mNavicache must begin with the 'this.' prefix to indicate that the item is a member of the class. 277 False 06/30/2010 12:43:56 0 02/26/2011 16:00:42 420 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False The class must have a documentation header. 16 False The field must have a documentation header. 18 False The field must have a documentation header. 19 False The field must have a documentation header. 21 False The field must have a documentation header. 22 False The property must have a documentation header. 24 False The body of the if statement must be wrapped in opening and closing curly brackets. 29 False The body of the if statement must be wrapped in opening and closing curly brackets. 34 False The body of the if statement must be wrapped in opening and closing curly brackets. 35 False The body of the if statement must be wrapped in opening and closing curly brackets. 36 False The constructor must have a documentation header. 44 False The method must have a documentation header. 52 False The body of the if statement must be wrapped in opening and closing curly brackets. 62 False The body of the if statement must be wrapped in opening and closing curly brackets. 65 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 69 False The method must have a documentation header. 75 False The body of the if statement must be wrapped in opening and closing curly brackets. 78 False The method must have a documentation header. 86 False The method must have a documentation header. 112 False The method must have a documentation header. 118 False The body of the if statement must be wrapped in opening and closing curly brackets. 123 False The method must have a documentation header. 131 False The method must have a documentation header. 144 False The method must have a documentation header. 156 False The body of the if statement must be wrapped in opening and closing curly brackets. 161 False The body of the if statement must be wrapped in opening and closing curly brackets. 177 False The body of the else statement must be wrapped in opening and closing curly brackets. 184 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 209 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 225 False The method must have a documentation header. 231 False The body of the if statement must be wrapped in opening and closing curly brackets. 234 False The body of the if statement must be wrapped in opening and closing curly brackets. 243 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 246 False The method must have a documentation header. 251 False The body of the if statement must be wrapped in opening and closing curly brackets. 259 False The body of the if statement must be wrapped in opening and closing curly brackets. 261 False The body of the if statement must be wrapped in opening and closing curly brackets. 264 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 267 False The method must have a documentation header. 271 False The body of the if statement must be wrapped in opening and closing curly brackets. 278 False The method must have a documentation header. 289 False The body of the if statement must be wrapped in opening and closing curly brackets. 295 False The body of the if statement must be wrapped in opening and closing curly brackets. 297 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 304 False The method must have a documentation header. 308 False The body of the if statement must be wrapped in opening and closing curly brackets. 314 False The body of the if statement must be wrapped in opening and closing curly brackets. 316 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 322 False The method must have a documentation header. 326 False The body of the if statement must be wrapped in opening and closing curly brackets. 332 False The body of the if statement must be wrapped in opening and closing curly brackets. 336 False The body of the if statement must be wrapped in opening and closing curly brackets. 337 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 341 False The method must have a documentation header. 345 False The body of the if statement must be wrapped in opening and closing curly brackets. 351 False The body of the if statement must be wrapped in opening and closing curly brackets. 353 False The method must have a documentation header. 359 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 377 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 407 False The method must have a documentation header. 419 False The body of the if statement must be wrapped in opening and closing curly brackets. 425 False The method must have a documentation header. 429 False The method must have a documentation header. 515 False The body of the if statement must be wrapped in opening and closing curly brackets. 520 False The body of the if statement must be wrapped in opening and closing curly brackets. 526 False The body of the if statement must be wrapped in opening and closing curly brackets. 528 False The method must have a documentation header. 541 False The body of the if statement must be wrapped in opening and closing curly brackets. 553 False The body of the if statement must be wrapped in opening and closing curly brackets. 555 False 06/30/2010 12:43:56 0 02/26/2011 16:00:42 552 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False The class must have a documentation header. 17 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 177 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 1087 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 1355 False The class must have an access modifier. 17 False The field must have a documentation header. 19 False Fields must be declared with private access. Use properties to expose fields. 19 False The field must have a documentation header. 20 False Fields must be declared with private access. Use properties to expose fields. 20 False The field must have a documentation header. 22 False Variable names must start with a lower-case letter: Marketplace. 22 False The field must have a documentation header. 24 False The variable name 'mCataIndexCache' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 24 False The field must have a documentation header. 25 False The variable name 'mFurniIDCYcler' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 25 False The constructor must have a documentation header. 27 False The method must have a documentation header. 32 False The body of the using statement must be wrapped in opening and closing curly brackets. 43 False Statements or elements wrapped in curly brackets must be followed by a blank line. 50 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 42 False The method must have a documentation header. 55 False The body of the using statement must be wrapped in opening and closing curly brackets. 58 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 57 False The method must have a documentation header. 61 False Statements or elements wrapped in curly brackets must be followed by a blank line. 80 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 82 False The code must not contain multiple blank lines in a row. 86 False Variable names must start with a lower-case letter: Data. 66 False Variable names must start with a lower-case letter: EcoData. 67 False Variable names must start with a lower-case letter: CataItems. 70 False Variable names must start with a lower-case letter: CatalogueItems. 71 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 61 False Variable names must start with a lower-case letter: Row. 75 False Variable names must start with a lower-case letter: Row. 92 False Variable names must start with a lower-case letter: Visible. 94 False Variable names must start with a lower-case letter: Enabled. 95 False Variable names must start with a lower-case letter: ComingSoon. 96 False Variable names must start with a lower-case letter: Row. 124 False The method must have a documentation header. 131 False Variable names must start with a lower-case letter: Page. 140 False The method must have a documentation header. 146 False Variable names must start with a lower-case letter: ItemId. 146 False Variable names must start with a lower-case letter: Page. 148 False Variable names must start with a lower-case letter: Item. 150 False The method must have a documentation header. 179 False The code must not contain multiple blank lines in a row. 196 False Variable names must start with a lower-case letter: TreeId. 179 False Variable names must start with a lower-case letter: Page. 183 False The method must have a documentation header. 200 False Variable names must start with a lower-case letter: Page. 200 False The method must have a documentation header. 210 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 250 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 292 False Statements or elements wrapped in curly brackets must be followed by a blank line. 310 False The code must not contain multiple blank lines in a row. 324 False Statements or elements wrapped in curly brackets must be followed by a blank line. 359 False Statements or elements wrapped in curly brackets must be followed by a blank line. 407 False Statements or elements wrapped in curly brackets must be followed by a blank line. 455 False Statements or elements wrapped in curly brackets must be followed by a blank line. 503 False Statements or elements wrapped in curly brackets must be followed by a blank line. 551 False Statements or elements wrapped in curly brackets must be followed by a blank line. 563 False Statements or elements wrapped in curly brackets must be followed by a blank line. 598 False Statements or elements wrapped in curly brackets must be followed by a blank line. 610 False Statements or elements wrapped in curly brackets must be followed by a blank line. 645 False Statements or elements wrapped in curly brackets must be followed by a blank line. 657 False Variable names must start with a lower-case letter: Page. 212 False Variable names must start with a lower-case letter: Item. 224 False Variable names must start with a lower-case letter: GiftUserId. 231 False Variable names must start with a lower-case letter: CreditsError. 264 False Variable names must start with a lower-case letter: PixelError. 265 False Variable names must start with a lower-case letter: Session. 210 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 242 False Variable names must start with a lower-case letter: Belcredits. 306 False Variable names must start with a lower-case letter: Bits. 325 False Variable names must start with a lower-case letter: PetName. 326 False Variable names must start with a lower-case letter: Race. 327 False Variable names must start with a lower-case letter: Color. 328 False Variable names must start with a lower-case letter: Belcredits. 355 False Variable names must start with a lower-case letter: Bits. 373 False Variable names must start with a lower-case letter: PetName. 374 False Variable names must start with a lower-case letter: Race. 375 False Variable names must start with a lower-case letter: Color. 376 False Variable names must start with a lower-case letter: Belcredits. 403 False Variable names must start with a lower-case letter: Bits. 421 False Variable names must start with a lower-case letter: PetName. 422 False Variable names must start with a lower-case letter: Race. 423 False Variable names must start with a lower-case letter: Color. 424 False Variable names must start with a lower-case letter: Belcredits. 451 False Variable names must start with a lower-case letter: Bits. 469 False Variable names must start with a lower-case letter: PetName. 470 False Variable names must start with a lower-case letter: Race. 471 False Variable names must start with a lower-case letter: Color. 472 False Variable names must start with a lower-case letter: Belcredits. 499 False Variable names must start with a lower-case letter: Bits. 517 False Variable names must start with a lower-case letter: PetName. 518 False Variable names must start with a lower-case letter: Race. 519 False Variable names must start with a lower-case letter: Color. 520 False Variable names must start with a lower-case letter: Belcredits. 547 False Variable names must start with a lower-case letter: Bits. 564 False Variable names must start with a lower-case letter: PetName. 565 False Variable names must start with a lower-case letter: Race. 566 False Variable names must start with a lower-case letter: Color. 567 False Variable names must start with a lower-case letter: Belcredits. 594 False Variable names must start with a lower-case letter: Bits. 611 False Variable names must start with a lower-case letter: PetName. 612 False Variable names must start with a lower-case letter: Race. 613 False Variable names must start with a lower-case letter: Color. 614 False Variable names must start with a lower-case letter: Belcredits. 641 False Variable names must start with a lower-case letter: Bits. 658 False Variable names must start with a lower-case letter: PetName. 659 False Variable names must start with a lower-case letter: Race. 660 False Variable names must start with a lower-case letter: Color. 661 False Variable names must start with a lower-case letter: Number. 687 False Variable names must start with a lower-case letter: GenId. 743 False Variable names must start with a lower-case letter: Present. 744 False Variable names must start with a lower-case letter: Receiver. 755 False The variable name 'dbClient' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 746 False The method must have a documentation header. 771 False The method must have a documentation header. 786 False The body of the if statement must be wrapped in opening and closing curly brackets. 968 False The code must not contain multiple blank lines in a row. 800 False The code must not contain multiple blank lines in a row. 810 False The code must not contain multiple blank lines in a row. 834 False The code must not contain multiple blank lines in a row. 877 False The code must not contain multiple blank lines in a row. 880 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 901 False The method must have a documentation header. 1005 False The method must have a documentation header. 1042 False An opening curly bracket must not be followed by a blank line. 1043 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 1048 False The method must have a documentation header. 1071 False The field must have a documentation header. 1089 False The method must have a documentation header. 1090 False Adjacent elements must be separated by a blank line. 1090 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 1098 False The method must have a documentation header. 1103 False The method must have a documentation header. 1136 False The code must not contain multiple blank lines in a row. 1148 False The method must have a documentation header. 1152 False The code must not contain multiple blank lines in a row. 1183 False The method must have a documentation header. 1187 False The body of the if statement must be wrapped in opening and closing curly brackets. 1190 False The body of the if statement must be wrapped in opening and closing curly brackets. 1192 False The method must have a documentation header. 1197 False The code must not contain multiple blank lines in a row. 1308 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 1309 False The method must have a documentation header. 1357 False 06/30/2010 12:43:56 0 02/26/2011 16:00:42 564 The file has no header, the header Xml is invalid, or the header is not located at the top of the file. 1 False All using directives must be placed inside of the namespace. 1 False All using directives must be placed inside of the namespace. 2 False All using directives must be placed inside of the namespace. 3 False All using directives must be placed inside of the namespace. 4 False All using directives must be placed inside of the namespace. 5 False All using directives must be placed inside of the namespace. 6 False All using directives must be placed inside of the namespace. 7 False All using directives must be placed inside of the namespace. 8 False All using directives must be placed inside of the namespace. 9 False All using directives must be placed inside of the namespace. 10 False The class must have a documentation header. 14 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 46 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 96 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 250 False The class must have an access modifier. 14 False The field must have a documentation header. 16 False Variable names must start with a lower-case letter: Id. 16 False All private fields must be placed after all internal fields. 23 False The field must have a documentation header. 18 False Variable names must start with a lower-case letter: Connection. 18 False The field must have a documentation header. 19 False Variable names must start with a lower-case letter: MessageHandler. 19 False The field must have a documentation header. 21 False Variable names must start with a lower-case letter: Habbo. 21 False The field must have a documentation header. 23 False Fields must be declared with private access. Use properties to expose fields. 23 False Use the built-in type alias 'bool' rather than Boolean or System.Boolean. 23 False The constructor must have a documentation header. 48 False A closing curly bracket must not be preceded by a blank line. 53 False Variable names must start with a lower-case letter: ClientId. 48 False The variable name 'pConnection' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 48 False All constructors must be placed after all fields. 273 False The call to Id must begin with the 'this.' prefix to indicate that the item is a member of the class. 50 False The call to Connection must begin with the 'this.' prefix to indicate that the item is a member of the class. 51 False The method must have a documentation header. 55 False The call to Connection must begin with the 'this.' prefix to indicate that the item is a member of the class. 57 False The method must have a documentation header. 60 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 62 False The method must have a documentation header. 65 False The call to Habbo must begin with the 'this.' prefix to indicate that the item is a member of the class. 67 False The method must have a documentation header. 70 False The code must not contain multiple blank lines in a row. 79 False Variable names must start with a lower-case letter: DataRouter. 80 False The call to Connection must begin with the 'this.' prefix to indicate that the item is a member of the class. 72 False The call to PongOK must begin with the 'this.' prefix to indicate that the item is a member of the class. 77 False The call to HandleConnectionData must begin with the 'this.' prefix to indicate that the item is a member of the class. 80 False The call to Connection must begin with the 'this.' prefix to indicate that the item is a member of the class. 81 False The method must have a documentation header. 84 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 86 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 88 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 89 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 90 False The method must have a documentation header. 98 False The body of the if statement must be wrapped in opening and closing curly brackets. 176 False The body of the if statement must be wrapped in opening and closing curly brackets. 205 False A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 141 False Variable names must start with a lower-case letter: Rights. 143 False Variable names must start with a lower-case letter: AuthTicket. 98 False Variable names must start with a lower-case letter: UserData. 102 False Variable names must start with a lower-case letter: NewHabbo. 110 False Variable names must start with a lower-case letter: Right. 148 False Variable names must start with a lower-case letter: Id. 186 False A comment may not be placed within the bracketed statement. 104 False The call to GetConnection must begin with the 'this.' prefix to indicate that the item is a member of the class. 102 False The call to Disconnect must begin with the 'this.' prefix to indicate that the item is a member of the class. 106 False The call to SendNotif must begin with the 'this.' prefix to indicate that the item is a member of the class. 119 False The call to Disconnect must begin with the 'this.' prefix to indicate that the item is a member of the class. 121 False The call to SendBanMessage must begin with the 'this.' prefix to indicate that the item is a member of the class. 132 False The call to Disconnect must begin with the 'this.' prefix to indicate that the item is a member of the class. 133 False The call to GetHabbo must begin with the 'this.' prefix to indicate that the item is a member of the class. 143 False The call to GetMessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 145 False The call to GetMessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 146 False The call to GetMessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 150 False The call to GetMessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 153 False The call to SendMessage must begin with the 'this.' prefix to indicate that the item is a member of the class. 157 False The call to GetHabbo must begin with the 'this.' prefix to indicate that the item is a member of the class. 155 False The call to SendMessage must begin with the 'this.' prefix to indicate that the item is a member of the class. 161 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 163 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 164 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 165 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 166 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 168 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 169 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 171 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 172 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 173 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 178 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 179 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 180 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 182 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 183 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 184 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 188 False The call to GetHabbo must begin with the 'this.' prefix to indicate that the item is a member of the class. 186 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 191 False The call to GetHabbo must begin with the 'this.' prefix to indicate that the item is a member of the class. 195 False The call to GetHabbo must begin with the 'this.' prefix to indicate that the item is a member of the class. 193 False The call to GetHabbo must begin with the 'this.' prefix to indicate that the item is a member of the class. 199 False The call to GetHabbo must begin with the 'this.' prefix to indicate that the item is a member of the class. 197 False The call to GetHabbo must begin with the 'this.' prefix to indicate that the item is a member of the class. 205 False The call to GetHabbo must begin with the 'this.' prefix to indicate that the item is a member of the class. 204 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 207 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 208 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 209 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 210 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 211 False The method must have a documentation header. 214 False Variable names must start with a lower-case letter: BanMessage. 216 False Variable names must start with a lower-case letter: Message. 214 False The call to GetConnection must begin with the 'this.' prefix to indicate that the item is a member of the class. 219 False The method must have a documentation header. 222 False Variable names must start with a lower-case letter: Message. 222 False The call to SendNotif must begin with the 'this.' prefix to indicate that the item is a member of the class. 224 False The method must have a documentation header. 227 False The variable name 'nMessage' begins with a prefix that looks like Hungarian notation. Remove the prefix or add it to the list of allowed prefixes. 229 False Variable names must start with a lower-case letter: Message. 227 False The call to GetConnection must begin with the 'this.' prefix to indicate that the item is a member of the class. 241 False Use the built-in type alias 'bool' rather than Boolean or System.Boolean. 227 False The method must have a documentation header. 252 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 257 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 263 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 269 False The call to Connection must begin with the 'this.' prefix to indicate that the item is a member of the class. 256 False The call to Connection must begin with the 'this.' prefix to indicate that the item is a member of the class. 254 False The call to Habbo must begin with the 'this.' prefix to indicate that the item is a member of the class. 262 False The call to GetHabbo must begin with the 'this.' prefix to indicate that the item is a member of the class. 260 False The call to MessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 268 False The call to GetMessageHandler must begin with the 'this.' prefix to indicate that the item is a member of the class. 266 False The field must have a documentation header. 273 False Variable names must start with a lower-case letter: Disconnected. 273 False The method must have a documentation header. 275 False The method must have a documentation header. 284 False A statement containing curly brackets must not be placed on a single line. The opening and closing curly brackets must each be placed on their own line. 316 False A single-line comment must be preceded by a blank line or another single-line comment, or must be the first item in its scope. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. 317 False Variable names must start with a lower-case letter: MessageLength. 294 False Variable names must start with a lower-case letter: MessageId. 295 False Variable names must start with a lower-case letter: Content. 297 False Variable names must start with a lower-case letter: Message. 304 False A line may only contain a single statement. 316 False The method must have a documentation header. 342 False The body of the if statement must be wrapped in opening and closing curly brackets. 345 False The body of the if statement must be wrapped in opening and closing curly brackets. 347 False Variable names must start with a lower-case letter: Message. 342 False