feature or bug?

[Shel Blauman [MSFT]]

Forwarding to Aspnet and Aspnet.Security. They may have run across this
question before.

Shel

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
[url]http://www.microsoft.com/info/cpyright.htm[/url]


"Ademar Gonzalez" <ademar@isqsolutions.com> wrote in message
news:%23z3jikDYDHA.2572@TK2MSFTNGP09.phx.gbl...

> Thanks Shel for your promt answer ...... but it doesn't work for me.
>
> I'm talking about NTFS permissions not Access Code Permissions.
> Let me set the scenario.
>
> The described issue happens when you try to execute the code from ASP.NET.
> ASP.NET is configured to impersonate the IUSR_WHATEVER user (throug the
> machine.config).
> This IUSR_WHATEVER user have NTFS write permission on the folder
> D:\Websites\WHATEVER_WEBSITE
> but non on D:\.
>
> Directory.Create fails with : System.IO.DirectoryNotFoundException: Could
> not find a part of the path "D:\"
> Note that it is not an access denied error!
>
> The funny thing is that File.Create works! in this same enviroment.
>
> Now, if i add ListFolder permission for the IUSR_WHATEVER user to all the
> parent folders including D: ,
> then Directory.Create works.
>
> D: is a local drive NOT network mapped.
>
> Any ideas, workarounds ?
>
>
> Thanks .. and regards!
>
> Ademar Gonzalez
>
>
>
>
> "Shel Blauman [MSFT]" <sheldonb@online.microsoft.com> wrote in message
> news:umSYDtCYDHA.2352@TK2MSFTNGP12.phx.gbl...

> > I believe you only need read/write permission for the folder you are
> > creating the directory in. The following code works for me:
> >
> > FileIOPermission fIPerm = new

FileIOPermission(FileIOPermissionAccess.Read

> |

> >
> > FileIOPermissionAccess.Write, "C:\\temp");
> >
> > fIPerm.PermitOnly();
> >
> > DirectoryInfo di = Directory.CreateDirectory("C:\\temp\\newDirectory" );
> >
> >
> >
> > Shel
> >
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no

> rights.

> > Use of included script samples are subject to the terms specified at
> > [url]http://www.microsoft.com/info/cpyright.htm[/url]
> >
> >
> > "Ademar Gonzalez" <ademar@isqsolutions.com> wrote in message
> > news:%236PyHWqXDHA.2572@TK2MSFTNGP09.phx.gbl...

> > > Hi there.
> > >
> > > Why does "Directory.CreateDirectory" needs the impersonated user to

have

> > > access (at least ListFolder permission)
> > > to all the parent folders in the path structure. ?
> > >
> > > Why doesn't "File.Create" need it ?
> > >
> > > It doesn't make sense. Can somebody explain this behaviour.
> > > Is there any workaround for the Directory.CreateDirectory issue ?. I

> don't

> > > want users to have access to the root of the drive.
> > >
> > > Regards
> > >
> > > Ademar Gonzalez
> > > Programmer
> > >
> > >
> > >

> >
> >

>
>

[Shel Blauman [MSFT]]

Forwarding to Aspnet and Aspnet.Security. They may have run across this
question before.

Shel

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
[url]http://www.microsoft.com/info/cpyright.htm[/url]


"Ademar Gonzalez" <ademar@isqsolutions.com> wrote in message
news:%23z3jikDYDHA.2572@TK2MSFTNGP09.phx.gbl...

> Thanks Shel for your promt answer ...... but it doesn't work for me.
>
> I'm talking about NTFS permissions not Access Code Permissions.
> Let me set the scenario.
>
> The described issue happens when you try to execute the code from ASP.NET.
> ASP.NET is configured to impersonate the IUSR_WHATEVER user (throug the
> machine.config).
> This IUSR_WHATEVER user have NTFS write permission on the folder
> D:\Websites\WHATEVER_WEBSITE
> but non on D:\.
>
> Directory.Create fails with : System.IO.DirectoryNotFoundException: Could
> not find a part of the path "D:\"
> Note that it is not an access denied error!
>
> The funny thing is that File.Create works! in this same enviroment.
>
> Now, if i add ListFolder permission for the IUSR_WHATEVER user to all the
> parent folders including D: ,
> then Directory.Create works.
>
> D: is a local drive NOT network mapped.
>
> Any ideas, workarounds ?
>
>
> Thanks .. and regards!
>
> Ademar Gonzalez
>
>
>
>
> "Shel Blauman [MSFT]" <sheldonb@online.microsoft.com> wrote in message
> news:umSYDtCYDHA.2352@TK2MSFTNGP12.phx.gbl...

> > I believe you only need read/write permission for the folder you are
> > creating the directory in. The following code works for me:
> >
> > FileIOPermission fIPerm = new

FileIOPermission(FileIOPermissionAccess.Read

> |

> >
> > FileIOPermissionAccess.Write, "C:\\temp");
> >
> > fIPerm.PermitOnly();
> >
> > DirectoryInfo di = Directory.CreateDirectory("C:\\temp\\newDirectory" );
> >
> >
> >
> > Shel
> >
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no

> rights.

> > Use of included script samples are subject to the terms specified at
> > [url]http://www.microsoft.com/info/cpyright.htm[/url]
> >
> >
> > "Ademar Gonzalez" <ademar@isqsolutions.com> wrote in message
> > news:%236PyHWqXDHA.2572@TK2MSFTNGP09.phx.gbl...

> > > Hi there.
> > >
> > > Why does "Directory.CreateDirectory" needs the impersonated user to

have

> > > access (at least ListFolder permission)
> > > to all the parent folders in the path structure. ?
> > >
> > > Why doesn't "File.Create" need it ?
> > >
> > > It doesn't make sense. Can somebody explain this behaviour.
> > > Is there any workaround for the Directory.CreateDirectory issue ?. I

> don't

> > > want users to have access to the root of the drive.
> > >
> > > Regards
> > >
> > > Ademar Gonzalez
> > > Programmer
> > >
> > >
> > >

> >
> >

>
>