Timeline for Windows Console App vs Service
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2015 at 7:41 | comment | added | Saeed Neamati | All of the benefits you mentioned would be easily applicable to Console Applications. The only benefit that is there is for a user to be logged in. | |
| Feb 4, 2015 at 19:48 | history | edited | Nathan | CC BY-SA 3.0 |
corrected grammar
|
| Nov 20, 2013 at 21:57 | comment | added | Wyatt Barnett | "A service can can easily be configured to run in the context of a high-authority accounts such as Network Service or Local System." -- not quite, I can schedule tasks to have console apps run as all of these pretty easily. I wouldn't call Network Service high authority either. | |
| Nov 20, 2013 at 19:57 | history | edited | Nathan | CC BY-SA 3.0 |
added 138 characters in body
|
| Nov 20, 2013 at 19:57 | comment | added | Nathan | Excellent point, added to main post. | |
| Nov 20, 2013 at 3:39 | comment | added | Martin Beckett | A service doesn't have an attached console, it can't print anything to stdout but has to use system logging instead | |
| Nov 20, 2013 at 3:17 | review | First posts | |||
| Nov 20, 2013 at 6:41 | |||||
| Nov 20, 2013 at 3:02 | history | answered | Nathan | CC BY-SA 3.0 |