Hello. I have problem with create and then remove directory on my site.
It works like this. My page
1) create directory
Directory.CreateDirectory(DirectoryPath);
2) put some files
3) Remove directory
Directory.Delete(DirectoryPath, true);

And I have problem here. For some strange reasons this directory because
read only and locked. I can't even open this until reopen my visial studio.
Why it happend? How I can create directory with full access and then remove
it with all files and subfolders inside?

Only when using VS.NET ? Also if the file is server by ASP.NET it is lokced
by default for a short period of time. Soa ccessing the site from a web
client could prevent deleting it immedately after.

Not sure what you are doing with those directories/files but my personal
preference would be to avoid this or perhaps to serve them direcdtly from an
aspx page (in whihc case IIS won't lock them).

Also double check of course that you are properly closing those file...

--
Patrice


"SushiSean" <(E-Mail Removed)> a écrit dans le message de
news: 562889C8-7774-4BBA-B56B-(E-Mail Removed)...
> Hello. I have problem with create and then remove directory on my site.
> It works like this. My page
> 1) create directory
> Directory.CreateDirectory(DirectoryPath);
> 2) put some files
> 3) Remove directory
> Directory.Delete(DirectoryPath, true);
>
> And I have problem here. For some strange reasons this directory because
> read only and locked. I can't even open this until reopen my visial
> studio.
> Why it happend? How I can create directory with full access and then
> remove
> it with all files and subfolders inside?

Thanks, what about derectory security?
I mean in function Directory.Create(DirName, Security)
exist Security param. How set up this to make dir with full access?

"Patrice" wrote:

> Only when using VS.NET ? Also if the file is server by ASP.NET it is lokced
> by default for a short period of time. Soa ccessing the site from a web
> client could prevent deleting it immedately after.
>
> Not sure what you are doing with those directories/files but my personal
> preference would be to avoid this or perhaps to serve them direcdtly from an
> aspx page (in whihc case IIS won't lock them).
>
> Also double check of course that you are properly closing those file...
>
> --
> Patrice