Saturday August 1st

Friday July 31st

Thursday July 30th

Wednesday July 29th

3 comments

I have yet to have a valid use for Server.Execute(), so if anybody has any good examples, I'm all ears.

I still want to know why you wouldn't just use a Redirect. It seem to me that leaving the original URL in the browser via a Server.Transfer could be a huge PITA and have many un-intended consequences... like what happens if the user refreshes the page?

DotNetKicks uses it in the Global.asax file, to handle error pages, you might want to check it out. About what happens when the user refreshes the page, nothing weird, the url in the address bar is requested again and the logic of the page begins from scratch, reissueing eventual Transfers or Executes.

Commenting on Stories is limited for now and will open up to those recommended by the community. Learn how
Loading DotNetKicks...
brought to you by the Kicks Network