Let's say I write an add-in that is loaded into the tabs of the console. What happens if the user doesn't have the console loaded? Will the code still fire that is in the console? (i.e., is it always running even if the user isn't logged into it?) Pardon me if this question is "dumb" but I'm still trying to get my head around how WHS works.
Let me expand on this. Let's say I want to send a pop-up to all clients on the WHS network when an event happens. Over on WHS Console I have a tab where the user types in their ZIP and it connects up to traffic data streams on the web.
Do I need to write a SERVICE that runs on WHS in Windows Services that is constantly running to query the web service on another machine -- or can I simply stick all that logic into the WHS tab code?
Do I put the logic for the pop-ups in the WHS tab code or in the Windows Service code? Inquiring minds want to know!
www.robertstinnett.com
Edited byRobert L. StinnettFriday, June 5, 2009 7:42 PMupdated with more info
You've got the right idea, though. Long-running stuff needs to go in a Windows Service (or maybe a Scheduled Task if you just need to fire it on a schedule). The console does continue to run after the user launches it for the first time, even if they "close" it, but you can't guarantee how long it'll run for.Tentacle Blog: http://www.tentaclesoftware.com/blog/
WHS Disk Management: http://www.tentaclesoftware.com/WHSDiskManagement/