A change in a vendor's WinMo application forces me to jump through some hoops to avoid forcing my users to log in every time. This is highly inconvenient as A) my users are farmworkers who aren't highly sophisticated and B) the application is not sensitive in the sense that there is any meaningful data associated with running the app on their PDAs.
I admit that the security-wonk part of me trembles at the thought of bypassing login, but the needs of the customer override.
I've got a simple workaround in place that is missing one piece. I've written a wrapper using the OpenNETCF framework, (http://www.opennetcf.com/), that lets me start the vendor's app and feed it a password using SendKeys.Send (COOL!). The problem is that it takes some time (sometimes upwards of 15 seconds) before the app is fully initialized and I can't send the password to the app until it's fully displayed.
I'd like to know what the best way to determine that the application is waiting on the login screen? My initial though is to look at the topmost window caption. Is that the best way or is there something better?
Code snippets or a reference would be most helpful and appreciated.
Thanks!
Bo