Rule of thumb for naming wrapper classes -


I feel myself creating a significant number of shelter classes, purely because I

< / P> Ul>
  • Classrooms that do not lend themselves well to RhinoMocks isolation models (like DirectoryInfo or WindowsIdentity )
  • Native Win API methods (I usually assemble all the methods in which I need a class and hide the original call as a class method
  • Then I would call myself 'W' (to indicate that this is a cover) and so I DirectoryInfoW ( DirectoryInfoWrapper NativeMethods.DuplicateTokenW .

    What will be the good rule of thumb after the naming of thumb squares?

    Naming conventions Whatever work you do for the team you are working with. As long as everyone is right with a particular conference, then it is fine.

    I prefer more verbose version, however, that is, DirectoryInfoWrapper is understandable to anyone who is not familiar with the code. But this is just me.


    Comments

    Popular posts from this blog

    c# - ListView onScroll event -

    PHP - get image from byte array -

    Linux Terminal Problem with Non-Canonical Terminal I/O app -