The fact that they exist and are supported means that you need to handle them. If past history is any guide, then Microsoft will bend over backwards to support applications that use 'legacy’ APIs for decades to come; and certainly this is what their principal customers expect. Soon we may even be rid of 16 bit support and NTVDM!
Having said all of this, if you are not planning mass market distribution, you may be able to get away without this support
Sent from Surface Pro
From: xxxxx@lenovo.com
Sent: Thursday, August 21, 2014 10:22 AM
To: Windows File Systems Devs Interest List
Hi,
I’m writing a file activity monitor using a mini filter. I’ve taken a good hard look at the change and delete sample drivers from Microsoft, and those examples devote a lot of code to dealing with transactions. I’ve read that Microsoft is discouraging new designs from using Transactional NTFS. My project is targeted at Windows 8 or later and might not ship until Threshold is released. Is it still worth the effort to support transactions in a mini filter driver? What would the side effects be from ignoring transactions?
As a matter of quality of design, I’d prefer to support transactions since the Microsoft examples still do. But I have found it hard to devise any test procedures. Does anyone know of a utility to create some transactions? Ideally I’d like to cause a few rollbacks as well as commits. I even had trouble finding sample code to make my own utility. Thanks for any advice.
- Joaquin Luna
NTFSD is sponsored by OSR
OSR is hiring!! Info at http://www.osr.com/careers
For our schedule of debugging and file system seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer