Hello folks.
I have a project to work on where I need to develop an application that will run on Windows Mobile devices. The objective is that the program will start up on device startup/wake-up and run infinitely with no visual interface other than a settings area where users can modify the program settings. Behind the scenes, the program will compare settings to results retrieve from what I believe will be a web service, and then takes action.
WM is a new area for me, and I have checked out numerous hits on google, msdn, etc, and I am still confused as to where to actually begin. Much of the code samples I have seen as well sort of flew over my head as well. I am under the impression that the ‘running behind the scenes’ part requires the ‘console application’ part, but the area that the users access the settings is in ‘device application’ using windows forms. This will be done with VS 2008, using C#.
Would anyone have tips to help point me in the right direction?
Thanks
Beau Adams
I was expecting changes within a few months as has been a common trend I’ve seen. :-/
For right now, this project is actually a prototype to demonstrate the client’s idea can be implemented.
Update:
I just got the console app set up, calling a new instance of the form, and going from there. I am looking to dig into adding the console app to startup then going from there to have settings stored on the device. I believe the settings will be stored in a file, or maybe registry setting? Would anyone have suggestions on this choice?
Thanks folks
Beau Adams
Your needs sound as if you are seeking to put a windows service on a mobile device. While I do not know if this is possible, is it wise? You would basically have a constantly running task on a battery driven device. Your end users will be running out of batteries in no time.
I take it the emulators aren’t worth a hoot? Currently that is what I’m working with, and I do believe we have a windows mobile device laying around somewhere. Beyond this, I also need to work on a Blackberry Pearl program that does the same thing this Windows Mobile one does. :-/
I’m glad these are prototypes, but not quite so glad the time is short. At least in this environment, it is far more developer friendly than my former job. J
Thanks for the tips on the MyMobiler. I’ll snag it.
Thank You
Beau Adams
From:
bs...@googlegroups.com [mailto:bs...@googlegroups.com] On Behalf Of Chris
Brandsma
Sent: Friday, October 23, 2009 10:22 AM
To: bs...@googlegroups.com
Subject: [BSDG] Re: Windows Mobile Development
I would be worried about that if I was doing C++, not so much if you are using C#.
“Don't store things in the Registry unless there is NO OTHER POSSIBLE WAY.”
Does that include application startup when the device turns on or wakes up? I believe the other way is via a .lnk in a startup folder.. that is actually my preferred method. Personally the only time I ever like to dig into registry is if I’m hellbent on destruction, and/or trying to fish out programs that shouldn’t be starting up. :-/
Thank You
Beau Adams
Yeah I agree. My first objective in the design of this thing is to ensure that it has next to 0 footprint, and does what it needs to do. More or less this will be tracking rate of movement and then doing stuff.
Beau Adams
From:
bs...@googlegroups.com [mailto:bs...@googlegroups.com] On Behalf Of David
Evans
Sent: Friday, October 23, 2009 10:25 AM
To: bs...@googlegroups.com
Subject: [BSDG] Re: Windows Mobile Development
Your needs sound as if you are seeking to put a windows service on a mobile device. While I do not know if this is possible, is it wise? You would basically have a constantly running task on a battery driven device. Your end users will be running out of batteries in no time.
Since WM apps stay in memory, would an app running in the background simply checking a local settings value to a GPS value every 250 or 500 milliseconds eat up memory?
From what little I know, I am thinking it would be something like on app start, if myApp thread doesn’t exist, create it. Then in the infinite loop put the thread to sleep for 250 or 500 seconds (whatever it is). Does this idea sound like the right path to efficient memory use without chewing up resources for other apps or the os?
Thanks
Beau Adams
Hrm.. the things I learn!
Ok backing up…. The program needs to get the speed at which a device is moving, and then perform an action based on that result. I hate to seem cryptic, I just don’t want to violate confidentiality agreements.
The program needs to get the speed at which a device is moving, and then perform an action based on that result.
It’s good to know that would be overkill.
While being in the beginning stages of this deal, there is a bloody lot I still need to learn about it. J So far the climb has been fun and challenging to say the least.
Thank You
Beau Adams
From:
bs...@googlegroups.com [mailto:bs...@googlegroups.com] On Behalf Of Jacob
Munson
Sent: Friday, October 23, 2009 11:10 AM
To: bs...@googlegroups.com
Subject: [BSDG] Re: Windows Mobile Development
The program needs to get the speed at which a device is moving, and then perform an action based on that result.
Aren't most GPS systems only accurate down to 10-20 yards? It seems like unless you are on an airplane, checking more frequently than every few seconds is overkill.The program needs to get the speed at which a device is moving, and then perform an action based on that result.
Is the programmability of gps set by users, or can they be set by programs (say the one I build)? Based on the requirements in this project, I believe the gps will have to be set to accuracy within 100 feet perhaps? Maybe more or less I’m not sure just yet. But anyhow, the checks will probably need to be every couple of seconds or so, since the action to be performed is the key to the success of the program in general.
Thank You
Beau Adams
From:
bs...@googlegroups.com [mailto:bs...@googlegroups.com] On Behalf Of Chris
Brandsma
Sent: Friday, October 23, 2009 11:17 AM
To: bs...@googlegroups.com
Subject: [BSDG] Re: Windows Mobile Development
With most programmable gps devices you can set how accurate the gps is. The less accurate you go, the faster the gps track. For instance, at the least accurate setting, the gps device will acknowledge you are in fact standing somewhere in North America.
also, if you are talking about something indoors...give up altogether. GPS receivers on mobile devices are not strong enough to make it through building walls.
Na, I voting for a stealth method of tracking employees for the state….. That or a way of tracking truckers as they drive through the state.
From:
bs...@googlegroups.com [mailto:bs...@googlegroups.com] On Behalf Of Jacob
Munson
Sent: Friday, October 23, 2009 12:21 PM
To: bs...@googlegroups.com
Subject: [BSDG] Re: Windows Mobile Development
also, if you are talking about something indoors...give up altogether. GPS receivers on mobile devices are not strong enough to make it through building walls.
“Maybe he's working on a secret government contract, using satellites and receivers accurate up to 1 millimeter, capable of signal penetration through 10 yards of concrete. ;)”
Not a bad guess. It is actually going to be 15 yards of concrete, 2 yards of brass, and 5 yards of that plastic Electromagnetic shielding that prevents EM interferance. :D
Thank You
Beau Adams
From: bs...@googlegroups.com
[mailto:bs...@googlegroups.com] On Behalf Of Jacob Munson
Sent: Friday, October 23, 2009 11:21 AM
To: bs...@googlegroups.com
Subject: [BSDG] Re: Windows Mobile Development
also, if you are talking about something indoors...give up altogether. GPS receivers on mobile devices are not strong enough to make it through building walls.
Heh.. a friend of mine down in Nampa was recently caught in an affair scandal. I know of one person for sure who would buy the trucker tracker idea, his wife. :-/