Given that “Test in Production” is all the rage these days, constant version churn isn’t restricted just to Microsoft components. We’ve seen third party code, both applications and File System Minifilters, change both dramatically and sometime frequently. The fact that the name of a third-party component hasn’t changed doesn’t necessarily mean its internal components or implementation mechanisms are the same.
Of course, this just serves to further complicate interoperability and repro scenarios.
Prior to the release of a recent version of FESF, we did very thorough testing with a specific Cloud Storage Provider. We were happy to know that FESF was fully interoperable. Imagine our surprise, some months later, when we got a problem report saying that FESF didn’t work at all with this same package. We did some quick exploration and discovered (surprise!) that the mechanism the product used to store and retrieve files from the cloud had completely changed.