I will be decommissioning Directory Monitor version 1.x and starting the development of version 2.0 with some new features based on user requests. Please leave a comment for any requests that are not on the roadmap and I will add them.
I have recently uploaded MSI installers as well as a standalone ‘portable’ version of Directory Monitor. I will make one more update with information and links on updating to 2.0 when it’s ready.
Because supporting this will take quite a bit of my personal time I have decided to make it ‘trial’ based. I will create a poll soon to decide on a selling price while it is still in development. Version 1.x will always remain free but will not be updated any further.
 |
Implemented |
 |
In Progress |
 |
Not Implemented Yet |
New Features
 |
Ability to monitor directories as a Windows Service (will double as console version). |
 |
Attempt to detect which user made the changes to the files/directory using NETBIOS. Will try and support doing this across network but you will need to be an admin for the share being monitored. |
 |
Options to include/exclude file types and subdirectories from getting logged. This will allow for executing a custom application when just a directory changes and not files (e.g. exclude *.* files). |
 |
Option to allow specifying how many log entries to be generated before performing the custom application execution. |
 |
Trial based with web functionality to verify license keys and unlocking and piracy alerting. |
 |
Advanced monitoring options to be specific about what entries get created for (attribute changes, security etc.) |
 |
CHM help file for information with extending and executing custom application with examples. |
 |
Ability to extend to UI and/or execution functionality programmatically. |
 |
Investigate monitoring Linux and NAS directories by detecting the type and falling back on some sort of polling because Windows event hooks won’t work. |
Improvements
 |
Remove settings from the registry to avoid full trust and use the standard application configuration file. |
 |
Directories to monitor will each have their own separate settings in an XML configuration file, easier to change, export and parse. Existing export format can be used for migration. |
 |
Use a file based memory map to read the log so that it can be shared by a UI client and also the service. This will greatly improve performance and reduce memory usage for large logs. |
 |
Remove ClickOnce for a custom updating and installing solution to avoid certificate issues and smart updates when installing using an MSI (or use them both). |
Maintenance
 |
Host project/bug tracking using either something basic like BugTracker.NET. |
 |
Push all downloads through a HTTP handler to properly track and report on usage. |
 |
Automate generating the MSI installer, uploading over FTP, PAD file, IL merging, posting release notes etc. |
Phew, that’s a big list…
Update: For more detail on milestones and the roadmap and also a better place to leave requests, check out the new Brutal Bug Tracker. I was always a fan of BugTracker.NET and setup a tracker here but I decided to go with BugNET because it's come a loooong way and is looking pretty good these days.
17d35ed2-76f8-4fc9-9873-404be2536bc7|1|5.0|96d5b379-7e1d-4dac-a6ba-1e50db561b04
Software
directory monitor, directory monitor 2, directory monitor roadmap