I suggest you ...

Implement interfaces for you objects so we don't have use SystemWrapper.codeplex.com

In order to Unit Test and mock things like Registry and File System, we have to create an interface and then wrap your code because your .NET code in the System Namespace doesn't already have an interface.

See http://systemwrapper.codeplex.com

If you added the interfaces from systemwrapper.codeplex.com to .NET and then made your objects implement the interfaces, then we could mock things like Registry, File IO, DirectoryEntry, etc., without having to write our own interface and a wrapper.

191 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jared Barneck shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • SleeperSmith commented  ·   ·  Flag as inappropriate

        I'm sorry, but the fact that we even have to vote on this make me cringe.

        Does the designer of .net framework not give a f*** about unit tests or what?

      Feedback and Knowledge Base