Cleanup of old rules (#143)

Author: bkoelman

_pages/1700_NamingGuidelines.md

@@ -37,6 +37,7 @@ Parameter | Camel | `typeName` |
 Type Parameter | Pascal | `TView` |
 Property | Pascal | `BackColor` |
 Tuple element | Camel | `firstName` |
+Resource key | Pascal | `SaveButtonTooltipText` |
 
 ### <a name="av1704"></a> Don't include numbers in variables, parameters and type members  (AV1704) ![](/assets/images/3.png)
 In most cases they are a lazy excuse for not defining a clear and intention-revealing name.

_pages/2200_FrameworkGuidelines.md

@@ -11,22 +11,12 @@ For instance, use `object` instead of `Object`, `string` instead of `String`, an
 
 **Exception:** When referring to static members of those types, it is custom to use the full CLS name, e.g. `Int32.Parse()` instead of `int.Parse()`. The same applies to members that need to specify the type they return, e.g. `ReadInt32`, `GetUInt16`. 
 
-### <a name="av2205"></a> Properly name properties, variables or fields referring to localized resources  (AV2205) ![](/assets/images/3.png)
-The guidelines in this topic apply to localizable resources such as error messages and menu text.
-
-- Use Pascal casing in resource keys.
-- Provide descriptive identifiers rather than short ones. Keep them concise where possible, but don't sacrifice readability.
-- Use only alphanumeric characters in naming resources.
-
 ### <a name="av2207"></a> Don't hard-code strings that change based on the deployment  (AV2207) ![](/assets/images/3.png)
 Examples include connection strings, server addresses, etc. Use `Resources`, the `ConnectionStrings` property of the `ConfigurationManager` class, or the `Settings` class generated by Visual Studio. Maintain the actual values into the `app.config` or `web.config` (and most definitely not in a custom configuration store).
 
 ### <a name="av2210"></a> Build with the highest warning level  (AV2210) ![](/assets/images/1.png)
 Configure the development environment to use **Warning Level 4** for the C# compiler, and enable the option **Treat warnings as errors** . This allows the compiler to enforce the highest possible code quality.
 
-### <a name="av2215"></a> Properly fill the attributes of the `AssemblyInfo.cs` file  (AV2215) ![](/assets/images/3.png)
-Ensure that the attributes for the company name, description, copyright statement, version, etc. are filled. One way to ensure that version and other fields that are common to all assemblies have the same values, is to move the corresponding attributes out of the `AssemblyInfo.cs` into a `SolutionInfo.cs` file that is shared by all projects within a solution. 
-
 ### <a name="av2220"></a> Avoid LINQ for simple expressions  (AV2220) ![](/assets/images/3.png)
 Rather than: