Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a .Net console App which using a scheduled event will start, call a mweb service method and the close. This runs every hour/every day. Whilst there is nothing ‘wrong’ with the implementation I was wondering if there was any benefit to implementing this as a windows service.
Has anyone any views of what would be the best practice in this case?
I Find Windows services hard to debug so I tend to only use them when:
(A) What I am doing is quite complex or
(B) needs to be running all the time(Example: Monitoring something for changes)
I find most things can usually be accomplished with a Console App some command line args and the Windows Scheduler.