Re: ProcessStartInfo.WorkingDirectory and Mapped Network Drives

b) Assume the service goes to sleep for some period of time (seconds,
minutes...it doesn't matter). This will eliminate Luc's suspicion that
the
drive has not successfully mapped by the time Start() is called on the
Process object.

That is not what I said. I just said that if your start a process with a
command 'net use w:..." you cannot set its default directory (before the
create) to w:
I know you can map drives in services as I do that too :-)

For your last post, I am not sure your drive mappings are automatically
inherited to processes you create with a bare CreateProcess from your
service. What does a process created like you do (as a sub-process of your
service) shows when you pass a simple 'net use' command to show what it
knows about mapped drives...

/LM


.