Migration Guide

[flowerey]

Is there one?

[LTRData]

Unfortunately, there is not. Which is not really good, we should ideally have one.

I have migrated a few projects over the years to this fork of DiscUtils from older DiscUtils versions, as well as between different versions of this fork. In most cases it is fairly straightforward. Features have largely been added or existing features optimized in various ways with the goal of as few breaking changes as possible. That has not always been possible though, particularly where methods have returned values or accepted parameters of types that I wanted to avoid. Therefore, directory enumeration methods return enumerators instead of arrays and similar changes, but I think it is in most cases not a lot of work to adjust consuming code for this.

That is for consuming code. If we go into other libraries that implement interfaces or base classes of DiscUtils, things get a lot more complex. I feel I no longer have a clear picture of where all changes have been made. There are several new requirements even for very basic interfaces such as IFileSystem and lots of parameter changes and added overloads for async and span based operations in many classes and interfaces. But on the other hand, other libraries implementing interfaces or base classes from DiscUtils are probably not that common.

[flowerey]

Hmm, I see. Thanks.