title: Rule of thumb for naming wrapper classes
body: <p>I find myself creating a significant number of wrapper classes, purely because I want to mock out the behaviour of </p>
  
  <ul>
  <li>Classes that don't lend themselves well to the RhinoMocks isolation model (for instance like <code>DirectoryInfo</code> or <code>WindowsIdentity</code>)</li>
  <li>Native Win API methods (I normally collect all the methods I need into a single class and wrap the native calls as a class method)</li>
  </ul>
  
  <p>I then find myself appending the class that is wrapped with a 'W' (to indicate that it's a wrapper) and so I end up with <code>DirectoryInfoW</code> (as opposed to <code>DirectoryInfoWrapper</code> which seems rather verbose). Similarly, I end up with wrapped native methods called <code>NativeMethods.DuplicateTokenW</code>.</p>
  
  <p>What would be a good rule of thumb to follow when naming wrapper classes?</p>