#If DEBUG and Response.Redire ct

[Dot net work]

I have noticed that this:

Response.Redire ct("/MyLocalDirector y/MyPage.aspx")

seems to be a lot quicker than this:

Response.Redire ct(sDirectorySt ring & "MyPage.asp x")
In local development mode, I need to have sDirectoryStrin g equal to my
local folder structure, but when I upload the project to a webserver,
the sDirectoryStrin g needs to contain a value equal to the webserver
folder structure.

Rather than have the sDirectoryStrin g variable scenario above which
seems to really slow the Redirect operation down, would this be a much
better approach:

#If DEBUG Then
Response.Redire ct("/MyLocalDirector y/MyPage.aspx")
#Else
Response.Redire ct("/MyServerDirecto ry/MyPage.aspx")
#End If

Thanks a lot, from dnw.

[Karl Seguin]

Don't like.

(a) the first shouldn't be "a lot" quicker than the second...it shouldn't be
noticable by any means
(b) You shoulnd't hard code paths into the application...w hat if you have a
3rd server, like a testing one, you'll add another compilation constant and
#else if that?

My suggestion is to stick with the 2nd one and figure out why it's so much
slower. Also, sDirectoryStrin g should be fed from a config file (web.config
is fine) so that it can easily be changed.

Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
"Dot net work" <do***@hotmail. com> wrote in message
news:77******** *************** ***@posting.goo gle.com...

I have noticed that this:

Response.Redire ct("/MyLocalDirector y/MyPage.aspx")

seems to be a lot quicker than this:

Response.Redire ct(sDirectorySt ring & "MyPage.asp x")
In local development mode, I need to have sDirectoryStrin g equal to my
local folder structure, but when I upload the project to a webserver,
the sDirectoryStrin g needs to contain a value equal to the webserver
folder structure.

Rather than have the sDirectoryStrin g variable scenario above which
seems to really slow the Redirect operation down, would this be a much
better approach:

#If DEBUG Then
Response.Redire ct("/MyLocalDirector y/MyPage.aspx")
#Else
Response.Redire ct("/MyServerDirecto ry/MyPage.aspx")
#End If

Thanks a lot, from dnw.

[Hans Kesting]

Dot net work wrote:

I have noticed that this:

Response.Redire ct("/MyLocalDirector y/MyPage.aspx")

seems to be a lot quicker than this:

Response.Redire ct(sDirectorySt ring & "MyPage.asp x")
In local development mode, I need to have sDirectoryStrin g equal to my
local folder structure, but when I upload the project to a webserver,
the sDirectoryStrin g needs to contain a value equal to the webserver
folder structure.

Rather than have the sDirectoryStrin g variable scenario above which
seems to really slow the Redirect operation down, would this be a much
better approach:

#If DEBUG Then
Response.Redire ct("/MyLocalDirector y/MyPage.aspx")
#Else
Response.Redire ct("/MyServerDirecto ry/MyPage.aspx")
#End If

Thanks a lot, from dnw.

If a path is processed by asp.net (as with Response.Redire ct) you can use a
"hidden" feature: When you start the path with a ~, then that will be replaced
by the application path. So you can just say:

Response.Redire ct("~/MyPage.aspx")

and it works both on your dev-machine and your live server.

Hans Kesting

[Dot net work]

Thanks for your suggestion.

"Karl Seguin" <karl REMOVE @ REMOVE openmymind REMOVEMETOO . ANDME net> wrote in message news:<ui******* ******@TK2MSFTN GP11.phx.gbl>.. .

Don't like.

(a) the first shouldn't be "a lot" quicker than the second...it shouldn't be
noticable by any means
(b) You shoulnd't hard code paths into the application...w hat if you have a
3rd server, like a testing one, you'll add another compilation constant and
#else if that?

My suggestion is to stick with the 2nd one and figure out why it's so much
slower. Also, sDirectoryStrin g should be fed from a config file (web.config
is fine) so that it can easily be changed.

Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
"Dot net work" <do***@hotmail. com> wrote in message
news:77******** *************** ***@posting.goo gle.com...

I have noticed that this:

Response.Redire ct("/MyLocalDirector y/MyPage.aspx")

seems to be a lot quicker than this:

Response.Redire ct(sDirectorySt ring & "MyPage.asp x")
In local development mode, I need to have sDirectoryStrin g equal to my
local folder structure, but when I upload the project to a webserver,
the sDirectoryStrin g needs to contain a value equal to the webserver
folder structure.

Rather than have the sDirectoryStrin g variable scenario above which
seems to really slow the Redirect operation down, would this be a much
better approach:

#If DEBUG Then
Response.Redire ct("/MyLocalDirector y/MyPage.aspx")
#Else
Response.Redire ct("/MyServerDirecto ry/MyPage.aspx")
#End If

Thanks a lot, from dnw.

[Dot net work]

That's cool, thanks.

I have found a nice overall solution for my dilemna.

I now have the following folder structure inside my project:

ASPXs/Home 'Home page just goes in here for neatness.
ASPXs/Authentication
ASPXs/NonAuthenticati on

When I need to move about, all I need to do is:

Response.Redire ct("../<one of the three folders
above>/MyChosenPage.as px

This will work on any machine with the easy-to-create folder structure
above.

(Previously, I had the Default.aspx sitting in a different sub folder
level in my project, and it was causing all sorts of "path access type
problems".)
"Hans Kesting" <ne***********@ spamgourmet.com > wrote in message news:<e0******* *******@TK2MSFT NGP12.phx.gbl>. ..

Dot net work wrote:

I have noticed that this:

Response.Redire ct("/MyLocalDirector y/MyPage.aspx")

seems to be a lot quicker than this:

Response.Redire ct(sDirectorySt ring & "MyPage.asp x")
In local development mode, I need to have sDirectoryStrin g equal to my
local folder structure, but when I upload the project to a webserver,
the sDirectoryStrin g needs to contain a value equal to the webserver
folder structure.

Rather than have the sDirectoryStrin g variable scenario above which
seems to really slow the Redirect operation down, would this be a much
better approach:

#If DEBUG Then
Response.Redire ct("/MyLocalDirector y/MyPage.aspx")
#Else
Response.Redire ct("/MyServerDirecto ry/MyPage.aspx")
#End If

Thanks a lot, from dnw.

If a path is processed by asp.net (as with Response.Redire ct) you can use a
"hidden" feature: When you start the path with a ~, then that will be replaced
by the application path. So you can just say:

Response.Redire ct("~/MyPage.aspx")

and it works both on your dev-machine and your live server.

Hans Kesting