Well, you won’t get a commitment from Microsoft one way or the other on TxF is what I suspect, because the general rules of engagement with the outside development community are quite clear on not discussing future product plans with same.
I’ve been watching the TxF evolution for 10+ years now and I must admit, I’ve always tried to understand who was truly going to use it. The only real-world use that I’ve seen for it is in implementing TxR and installers.
The most telling thing to me is that ReFS does not support transactions. That suggests to me this is a feature that does not have sufficient demand to justify expending the resources to build TxF support into ReFS. In some ways, ReFS allows Microsoft to focus on those file system features that are useful and to drop support for those features that aren’t (and yet cost tremendous resources to maintain).
I have not noticed the warning message you’ve described on the MSDN documentation pages I’ve viewed regarding transactions. For example: http://msdn.microsoft.com/en-us/library/windows/hardware/ff566422(v=vs.85).aspx describes ZwCreateEnlistment, and I don’t see any caveats to this saying that this API will not be supported in future OS releases.
Tony
OSR