Oughtness, Isness and the world of systems management

Nice.  Makes me think this could/should refactor the meaning of what a Service is.  At a level a service is just a program.  If all programs now needed to support the notion or Stop/Pause/Start, then all programs could be Services with no special install or project type.  And management could start/stop/monitor any program on the system without any special handling of Service or normal app.  So I could write a standard console app that does XYZ.  Maybe I just want to use it as a "normal" app.  But maybe I want to use the *same app and have it be a service latter.  Now because I already had to support Stop/Start/Monitor, I can just drop it into a Services Dir on the computer and it just runs as a service.  Already debuged as normal console app, don't need to compile two different versions and figure out how to deploy it, etc.  It just works.  If something behaves badly as a service, maybe the system just stops it and reports the issue and removes it from Services dir until certain quality gate is passed (manually defined or other). 

Maybe also when I log from my app, important logs flow by proxy via MS log hosting to the Developer of app (via subscription).  Developer pays small fee for this hosting proxy.  Encrypt what is secure as needed and allow certain things public that may be helpful to MS such as Exception messages, etc.  This feedback loop can only help improve the platform for all.   Naturally, when this is in place, things like Registration, license fee, etc could just flow via the same method.   Cool stuff.