I'm writing a screensaver in C# which should launch an application and then terminate when the user presses the "A" key.
This currently does happen on Windows 7 when you double click the .scr file or wait until it launches. On Windows XP the external application launches normally only when you double click the .scr file. When the screensaver is launched by the OS, then pressing "A" does terminate the screensaver but the external application is launched momentarily then closes. The Task Manager shows that the external application closes a split second before the Screensaverso I would imagine that this terminates the external application too for some reason. This is the behaviour with whatever you set the external application to be.
Is there something internal that happens when a Screensaver is launched from the OS rather than double clicked by the user?
I'm using System.Diagnostics.Process.Start() to run the external application but using Process and ProcessStartInfo has the same effect.
I'm using .NET Framework 3.5