That's a .NET thing, not something with our software. .NET applications 'shut down' after they've sat idle for a while, and have to start back up the next time they're hit. Once they start up, they...