The way the Process Blocker project is being (and going to be) developed is presented on this page. Probably it is not a real roadmap and more like a to-do list, but anyway it might be interesting for all concerned. The items themselves as well as their order are subject to change; the current position is marked with red.

Roadmap

  1. Creating a pilot version of the program
    Applications are killed by retrieving their names from a text file
  2. Launching a website
  3. Code signing
  4. Making a PAD file
  5. Submitting the program to download sites
  6. Creating an .MSI installer
    To simplify the installation process
  7. Copy-editing the website
  8. Adding a time bomb to the program
    To prevent using it two years after the release
  9. Improving the program’s behavior in a Terminal Services environment
  10. Adding an option to kill an application using its full path
  11. Creating a usable interface
  12. Adding an option to kill an application using its CRC
    To help prevent an application from running even if it is renamed
    Will also require the creation of an additional tool enabling the administrator to calculate CRCs
  13. Removing the time bomb. Fixing a few bugs
    A step towards the rethinking and reviving of the project
  14. Creating an .ADM file and writing an accompanying help document for it
    To enable domain administrators to manage the program using domain policies
  15. Adding a feature to record work process/error events to Windows Event Log
  16. Adding an option to run applications only from certain folders
    To allow users to run applications only from, for example, Program Files
  17. Changing process killing to process execution prevention
    A milestone step turning the beta version of the program into a full-fledged one
  18. Redesigning the website
    To make it look more professional
  19. Adding an option to export and import lists of prohibited applications (instant messengers, games and other time killers)
    To let customers easily exchange them
  20. Adding an option of remote control
    To allow administrators without a domain controller to configure the program remotely, and in batch