There is no such thing as " C directory from the remote machine". There even no such thing as "C directory", even on your local machine. And, just to dismiss the though completely, even on your local Windows system, event the
volume "C:" may or may not exist. The whole idea is wrong; this is not how things works.
Generally, with remote computer connected to a network, no computer has access to nothing except some network services. You can access only to some of those services, only if you have enough privileges. And the services can sever up files or not; it depends on the configuration of a remote computer.
With Windows, specifically, you can use its
file sharing service, which is always on by default:
Enable file and printer sharing[
^].
The file names, generally, have nothing to do with original remote computer's file system, they are UNC:
Uniform Naming Convention — Wikipedia, the free encyclopedia[
^].
The file names are set up when you set up file sharing properties for directories and files. They may or may not follow the original file system structure.
If you use Windows file sharing. You work with shared file
exactly in the same way as with local system files. The different story would be if you need to do network
discovery. One of the ways to do it is described in this CodeProject article:
Network Shares and UNC paths[
^].
On other OS… but why should I be concerned with other OS? Well, because you only tagged "C#"; you did not indicate that you only work on Windows and only with Windows. C# can be used in many OS, can't it? Well, in brief: this is a whole different story. For example, please see:
Common file systems and protocols — Wikipedia, the free encyclopedia[
^],
Samba (software) — Wikipedia, the free encyclopedia[
^],
Network File System — Wikipedia, the free encyclopedia[
^].
—SA
Submit an article or tip