FindWindow works fine for any window, hidden or not, so your code tehre is
likely flawed.
The reason an app may continue to run is that it's in a system wait state.
You can't terminate an app in that state until the wait is signalled and the
app gets scheduled again.
--
Chris Tacke, Embedded MVP
OpenNETCF Consulting
Managed Code in an Embedded World
www.OpenNETCF.com
"Pulkit" <Pul...@discussions.microsoft.com> wrote in message
news:3069C215-E72C-4EE1...@microsoft.com...
Incorrect. FindWindow can and does find hidden windows.
If you're having a problem using the API, then post a question with the code
that is failing. I simply corrected you the first time so that if someone
comes across this thread while searching the newsgroup archives they don't
go away with misinformation. Continuing to argue this is like arguing that
the sky isn't blue.
--
Chris Tacke, Embedded MVP
OpenNETCF Consulting
Managed Code in an Embedded World
www.OpenNETCF.com
"Pulkit" <Pul...@discussions.microsoft.com> wrote in message
news:E97DDB15-B0EA-4876...@microsoft.com...
Once again, I have to disagree. It has nothing to do with the CLR. It has
everything to do with something wrong in *your* code (which you've still not
posted). FindWindow can and does find hidden windows. Since you seem to
require proof, here it is:
http://blog.opennetcf.org/ctacke/PermaLink,guid,fcaf9bc2-2026-427b-b65e-95639de2d857.aspx