.Net Core transition: Inject IIOHelper wherever possible

This task is up for grabs, for contributing to the .Net Core transition project

On the development branch of the .net core transition project netcore/dev, we have already abstracted the static IOHelper, into an interface (IIOHelper) and an instance class (IOHelper).

This was required to not block some other tasks. To finish that task as fast as possible, we just added a new static property on the static helper Current (Current.IOHelper). This new static property is used all over the system, instead of the original static IOHelper.

This task is about eliminating the usage of Current.IOHelper, by replacing it with a constructor injection of IIOHelper.

Expected Procedure:

• Find an instance class that uses Current.IOHelper.
• Add IIOHelper ioHelper to the constructor.
• Save the ioHelper in a private readonly IIOHelper _ioHelper; field.
• Replace the usages of Current.IOHelper.* with _ioHelper.*.
• Make sure the project builds
• Ensure unit tests all pass
• Repeat the process

If any questions, feel free to ask 😃

---

Related: AB#3667

[Shazwazza]

@soreng please leave Umbraco.Core.IO.IOHelper.Default as-is, this can also be used in unit tests if necessary. It shouldn’t be used in the Core/Web projects though, only for registering IIOHelper in DI in the Core/Web Runtime.

[soreng]

Wow, then my work needs a bit more… work 😉