c# - Directory.Exist(...) fails because of some file system permissions -

I have a file system and a specific path structure on my system that is accessed by the cloned users.

There is no such thing that the user can not see the existence of their folders.

My folder structure is as follows.

  Base Path (Admin Only) + - & gt; User Profile (Admin only) + - & gt; User area (owner user and endin)  

as an example:

... \ path path \ John's profile \ John's area

John has only the right to access (NTFS permissions) on the file system (NTFS permissions) John's Area and me in the area of ​​John need to check the existence of the program

  directory. Axis ("... some other path part ... \ base path \ John profile \" area of ​​John); It is true if I impersonate the administrator, but if I impersonate John, then it misinterprets it  
 I thought John was in his file system Folders will be able to see the existence - even if it is the  base path - & gt; John's Profile In his / her area, he can go directly to the  ... \ base path \ John's profile \ John's Area . 
 
 What permission do they need to check the existence of that folder? Or do I remember what is something original? 
 

OK, it seems that this is an ASP.NET web- If the site is such a case, then your app is being hosted by the Internet Information Services , then you must ensure that the worker has the proper procedure for the process, the directory for the system. Without it, the I / O jobs will not succeed.

• IIS_IUsr I believe the user

You must remember that although it runs on the server inside IIS , it is not using a logged-in user IIS The underlying user is using .

If it is not hosted within IIS , then your impersonation approach should work. Make sure this account is properly cloned.

You can also do a test like this to verify:

  Valid Valid Valid Validation (string path) {try {if (Directory.Exist ( Path)) Truth back; Else {Directory.CreateDirectory (Path); }} Hold (ex before) {return false; }}  

Therefore, if it exists then it will return back to true ; If it is not, then it does not try to write the directory, then it will leave the exception if it fails to write, then returning the incorrect , you will know that It has failed.