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.
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.
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?
I agree, and I wrote an article that seems related to this idea: http://loyc-etc.blogspot.com/2010/08/pervasive-services-and-di.html
My idea is basically that the system should provide hooks for replacing or augmenting all the standard services, so that we can e.g. create files the same way we have in the past, without suffering from "dependency injection overload".