Valentin Breuß

**This draft is to gather feedback about the suggested approach in general.** *Currently no event is triggered, when the file is only accessed. This could be quite easily added after...

@fgreinacher > Any reason to not expose this as regular events, as e.g. suggested https://github.com/TestableIO/System.IO.Abstractions/issues/168#issuecomment-263130564? It probably boils down to personal preference :-) I think callbacks are easier and for...

@fgreinacher : I think in the end it boils down to preference. Especially in unit tests I like the fluent syntax (I also use FluentAssertions in my xUnit tests). Regarding...

@fgreinacher : In the beginning I started doing exactly that, however the interfaces are not completely identical: - I separated the interfaces from the default implementation with wrappers in separate...

@fgreinacher > > @fgreinacher : In the beginning I started doing exactly that, however the interfaces are not completely identical: > > > > * I separated the interfaces from...

> I think a simple way would be keep the namespaces as-is and change the NuGet package structure a bit: > > * Add `TestableIO.System.IO.Abstractions` with just the interfaces >...

When using it in a web environment I often have the "problem" of matching errors to http status codes. For this use case I often use an ErrorType property that...

I didn't suggest to directly use an http status code in the library. It's just an example for the use case of an error categorization. But I am not sure...

I don't mean to require users to enhance the error class, but to support it. This way you can create your own hierarchy of errors, but the library itself doesn't...

I would give it a try...