.NET file system wrapper library [closed]

Answer 1

There is also a FileInfo class, which does the same things as the static methods.

On the other hand, you probably don't want to mock the entirety of the FileInfo class. Instead, you want to place all of your file operations into a single class, then extract an interface from the class (describing the public methods), and use the interface to mock the file operations that you perform, not the entire set of operations that Microsoft thinks should be in the FileInfo class.

Answer 2

https://github.com/tathamoddie/System.IO.Abstractions allows you to do this (example from github)

public class MyComponent
{
readonly IFileSystem fileSystem;

// <summary>Create MyComponent with the given fileSystem implementation</summary>
public MyComponent(IFileSystem fileSystem)
{
    this.fileSystem = fileSystem;
}
/// <summary>Create MyComponent</summary>
public MyComponent() : this( 
    fileSystem: new FileSystem() //use default implementation which calls System.IO
) 
{
}

public void Validate()
{
    foreach (var textFile in fileSystem.Directory.GetFiles(@"c:\", "*.txt", SearchOption.TopDirectoryOnly))
    {
        var text = fileSystem.File.ReadAllText(textFile);
        if (text != "Testing is awesome.")
            throw new NotSupportedException("We can't go on together. It's not me, it's you.");
    }
}
}

Answer 3

I maintain the Jolt.NET project on CodePlex, which contains a library to generate such interfaces and their implementations for you. Please refer to the Jolt.Testing library for more information.

Answer 4

I found SystemWrapper a few minutes before yours, but yours suits my purposes better.

Answer 5

All good answers, but they all left me where I started - recreating some sort of IFileSystem for every project I end up working on. I ended up creating a generic IFileSystem library around the .NET libraries that I can use reuse between all my projects. Not great, but it works for now.

Answer 6

Instead of looking for a library that wraps the whole filesystem. Why not create a simple IFileSystem interface and start adding the methods that you need.

The rest of your application should depend on IFileSystem which will allow for mocking

You can have one implementation that simply calls the static methods that .Net gives you and then your code can depend on the interface.