How to access Network drive through windows sercices in c#

Question

I'm stuck while creating an application whose abstract work is to copy some file from host machine to network machines shared folder,

I'm doing something like this in c#

string lscmd = "robocopy "+ lsCurentWorkingDirectory+ " \\\\CPU219\\Test$ " + lsFileName;
ProcessStartInfo ProcessInfo;
ProcessInfo = new ProcessStartInfo("cmd.exe", "/c " + lcmd);
ProcessInfo.CreateNoWindow = true;
ProcessInfo.UseShellExecute = False;
process = Precess.Start(ProcessInfo);
process = Precess.Start(ProcessInfo);
ProcessInfo.CreateNoWindow = true;
ProcessInfo.UseShellExecute = False;
process = Precess.Start(ProcessInfo);
process.waitforExit();

When I'm runing this code through windows services its get stuck at process.WaitforExit(), and when I'm running this by normal console application, it works well.

plz help me

Vulpes · Answer

If you don't wait for the process to exit does it work then?

waqar ahmed imamuddin · Answer

yes Services geting access to comman prompt to run batch file from first batch file m creating zip_file and from second m trying to write it on remote machine i have all write privillage on remote machine still it shows me some kind of access problem. if m running second batch file by double clik its working fine and writng on remote machine.

Vulpes · Answer

So just to be clear are you saying that the service does allow you to use the command processor to run a batch file which creates the file but when you attempt to use the command processor to copy this file to the remote drive it hangs whilst waiting for the process to exit?

waqar ahmed imamuddin · Answer

before copy m runnig one batch file by same method to create file and then i'm trying to copy it on remot drive its creating file but m not geting access to write it on remot by services but i have given read/write permission to that folder on remote machine.

Vulpes · Answer

I suspect your problem here is that (from Vista onwards) Windows services are no longer allowed to interact with applications which have a user interface which would include even the command processor cmd.exe. So whilst you can start such an application from a windows service you can't then interact with it using the WaitForExit method. You could try handling the Exited event instead though I'm not confident that it will work either. If it doesn't work then your best bet might be to run it as a console application but hide the console window.