Ok, ok, i know this should be a scheduled service, but its got too much UI. I want an app to execute a proc from 9-5pm, but be running all the time so it starts every day at 9 and stops and 5pm.
If i use Thread.Sleep(10mins) say, and check the time in a loop would that be ok in terms of reliability (e.g the thread won't get aborted by the runtime if it gets bored) and system resouces? (although aren't extremely limited but it shouldn't soak up as much than if it was performing higher maths calcs to fill time for example, shouldn't it?)
What other/better way is there?