> I'm not seeing this. When I attempt to launch my application a second
> time,
> the already-running instance is brought to the foreground. No calls are
> made
> to Main.
That is correct. I consider it a major problem with the CF implementation
in WM (CE doesn't have this problem), but that's just me. To get it to
behave, you have to rename the class of the parked form that the CF is
looking for and handle the second instance manually. Alex Feinman posted
about how to do this way back in CF 1.0 days. I believe the class name
changed in CF 2.0, but the general idea is the same.
> I understand that if you re-launch an application before the first
> instance
> is up and running, you can get a second instance (which means you have to
> supply mutex code); however, that's not the case here. The OS or CF seems
> to
> be bringing the already-running instance to the foreground.
It's the CF - not the OS. And the fact that you can still get a second
instance is proof that the idea of what they were trying to achieve is
broken.

Signature
Chris Tacke, Embedded MVP
OpenNETCF Consulting
Managed Code in an Embedded World
www.OpenNETCF.com