A reliable approach for copying or moving remote files from a .Net client?

Question

I have a Windows service that tracks remote resources for job management and output of result files, and also processes and moves files to archive folders.

My best solution so far is using the methods available in the System.IO namespace (e.g. Directory.Exists (), File.Move (), etc.) to access and move these files.

The problem with this approach is that if the remote computer is not in a domain (which is not), my service that performs these operations must be run under a user account that also exists on the remote computer (Windows), and accordingly should be Permissions are set for shared access and file system objects on both remote and local computers.

I am worried about problems that may arise in the future if the environment changes because people are not aware of these dependencies. I would rather build a more robust solution. Do you have any suggestions?

Answer 1

You would map the network path using NetUseAdd, WNetAddConnection2 is one of the options.

http://pinvoke.net/default.aspx/netapi32.NetUseAdd