Changes

*The service gets started*The service watches the work item directory for work itemsdetermines which action should be performed from its command line parameters.*The service detects that If the command is an action other than a 'work item' software update, the action is writtenperformed. (None are supported yet)*The service parses If the information from the work item filecommand is a software update then continue on... *The service verifies that the updater.exe, and the callback application is our files file (See section Signing builds below)*The service will execute the update with updater.exe under the context of its own session (session 0) using CreateProcess. *The path of updater.exe will be a copy of the updater.exe which exists inside the service directory. (A copy in case the original gets overwritten during the update).*The post update process (helper.exe) currently does i) system level stuff, and ii) user level stuff. This component will be executed twice. The system level stuff will also be executed under session 0 using CreateProcess. The user level stuff will be executed by the unelevated updater.exe with its own session ID.*The service sets a global named event to let the unelevated udpater.exe know stops itself when it is done workingthe operation.