Have you tried to delete a directory programmatically in ASP.Net 2.0? Don’t try it; it can cause great problems to your site especially if you are using in-proc session. You will lose the entire session variable after deleting the directory and there is no way of getting those session variable back. This system is a change from asp.net 1.X.

I came to know about this the hard way. I was working on a project were project submission was a process of 6 pages (All in one page using the MultiView control). In the last stem I was supposed to delete the entire directory which was created during the process. Strangely I was loosing all the session values when the directories were deleted.

The problem gets bigger from the fact that the AppDomain will restart again on the first request to that application. So there is no way to restore the session after deleting the directory in the application domain. There is no problem in creating the directory but deleting will hurt the in-proc session.

What we can do not delete the folder and only delete the files in the folder. I.e. instead of

Directory.Delete(Server.MapPath(path), true);

Use

filedelete(Server.MapPath(path));

where filedelete() is, (I prefer creating these utilities into function so that I do not write the same code again and again)

private void filedelete(string path)
{
        string[] st;
        st = Directory.GetFiles(path);
        int i;
        for (i = 0; i < st.Length; i++)
        {
            try
            {
                File.Delete(st.GetValue(i).ToString());
            }
            catch { }
        }
    }

I never thought this File Change Notifications (FCN) can cause me so much of problem. So if you find yourself working with file system in DOT Net. Remember deleting a directory can be more than dangerous. So try not to delete any directory at the runtime.