Hello everyone,

I am having some problems with my application running wirelessly from a
network drive, and am wondering if anyone has any suggestions.

My situation is thus:

1) I am using a windows mobile 2003 device to run my application.
2) The application is a SmartDevice vb.net app, and lives on a shared
drive.
3) My device connects to the network wirelessly.
2) My application will be running in a company on multiple devices
simultaenously. It will also be updated regularly. Because of this, I
do not want to application (the exe) to live on the device, as
everytime I do an update I would have to go and manually copy the new
file into the device.

I have tried to get my application to run at startup on the device by
copying a shortcut into the startup folder for the PPC. However, this
fails and says file not found.

I have tried using Resco, Net Use etc to map network drives. If I enter
their program, or file explorer first, as I enter the program, there is
a long pause as it reconnects my shared drivers. However, my problems
would be all solved if the PPC automatically connected to the network
drive on startup, as a PC would.

Does anyone know any tricks, programs, etc to force this behaviour.
Alternatively, if I could deploy my application to all devices when an
update is made, without me having to go and manually copy it, this
would solve it too.

Many thanks for all help

"DanielNC" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Does anyone know any tricks, programs, etc to force this behaviour.
> Alternatively, if I could deploy my application to all devices when an
> update is made, without me having to go and manually copy it, this
> would solve it too.
>

Have a program that is executed on startup on the PPC that basically looks
for the file to execute in a looped fashion. Once the connection is
established the executable can then be found, and have the startup program
start the network executable after a brief delay to validate the connection
has settled. The main thing to note is that you will have to handle the
file not found error accordingly.

One more thing you could do is to have this startup program copy over the
executable and execute it locally. This would allow the PPCs to run the
program when they are away from the network, but only after the startup
executable times fails after x number of attempts. The next time the device
is in range of the network it would automatically update, then execute.

That is, if there is a practical need for the program to run away from the
network.

Good Luck