Comments by Ed Guzman (Top 20 by date)

While deploying it you do not stop the Application object on the server site.
The application object is destroyed only when you stop WWW service, stop IIS, stop your website through IIS, application crashes, or you just change your web.config, telling your application to collect the changes.
There are some more events, i just don't remember on the top on my mind.

it means that you have to add:
using System.Web.Security;

I looked through your code. The outcome is the same as mine, it handles post-backs through changing the "action" property of the form. I liked the way you handle: through form.browser rather than through basepage. I never used the form.browser before, need to try :-)
Good job.

Very neat idea. I will try it too

I am not sure about master page rendering. The master page is just a wrapper around a page, but it worth trying.
Let me know if you get it working. I agree that using a base page just for this purpose is a bit too much. Fortunately, I have a lot of different useful things in the base page. Let me know if how you handle this.

I wrote a piece of code to handle this. I will place it into the different answer.

:-) ok. One of the simplest implementation of delegates:
you want to use one variable and dynamically changed its behavior based on the logic of your program.
This variable has not value, it has functionality. And you can change the functionality on the fly, just re-assigning different function into this variable.
Good luck.

The one I referenced makes the transfer rather then redirect. You will never see the underlined URL. I could send you a dll and a sample of web.config. Let me know and good luck.

Then you have to drill down what happens when you change from one theme to another, what settings are changed and when. There are too many unknowns for making any decisions. If you want to change a theme when reloading a page then the PreInit event is the right place to do it. Actually the only place to do it.

Look at the aspx page and add the code I gave you into it, not into .vb

GridView Par = (GridView)e.Row.FindControl("ParamGV");
Par.SelectedIndexChanged += new EventHandler(ParamGV_SelectedIndexChanged);

void ParamGV_SelectedIndexChanged(object sender, EventArgs e)
{
}

I agree, this sounds strange. If you tried already place the file onto the root directory it definitely should have the access, but just double check. Let me know if it works.

What I am trying to say is that your private delegate
void CopyFileDelegate(string srcDir,string DesDir)
has the signature that accepts 2 parameters and you use this delegate in BeginInvoke method of a textbox. Which is incorrect, because according to Microsoft this Delegate should be parameter-less. Definitely there is a way to pass parameters but not the way you tried. That is why your code was not compiled at the first.

Actually the first parameter of the TextBox.BeginInvoke method is System.Delegate, and according to Microsoft this is a delegate to a method that takes no parameters.

Correct, when you instantiate a delegate (using new keyword), you just point to the name of the function without parameters
Please read my article
<a href="http://www.codeproject.com/KB/cs/delegatespart1.aspx">http://www.codeproject.com/KB/cs/delegatespart1.aspx</a>