Pitfalls of using a Global Response.Redirect

[spamfurnace]

Hello.

I have a common area of a website that sales agents use. I got sick and
tired of typing response.redirect(path)
so i implemented a shared function in Global that i can call and all i have
to do is pass an AgentService enum to it and global will response.redirect
for me.

So instead of typing

Response.Redirect(Global.GetApplicationPath &
"Agents/Pages/Agent_Profile.apsx?aaid=45" etc etc)

I just type

Global.GotoAgentService(Me.response, AgentService.MessageCenter)

With intellisense filling in most of it for me.

Are there any pitfalls to redirecting from Global...given that it's such
special file. I dont want to get caught out by some invisible hand.

TIA
Richard

[Alvin Bruney [MVP]]

No, this is ok. I don't know how much time you saved with this approach
since you could have accomplished the same by
Response.Redirect((string)AgentService.MessageCent er)
but if it pays the bills then it pays the bills...

--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok
"spamfurnace" <sp*********@intermension.com> wrote in message
news:ey**************@TK2MSFTNGP12.phx.gbl...

Hello.

I have a common area of a website that sales agents use. I got sick and
tired of typing response.redirect(path)
so i implemented a shared function in Global that i can call and all i
have
to do is pass an AgentService enum to it and global will response.redirect
for me.

So instead of typing

Response.Redirect(Global.GetApplicationPath &
"Agents/Pages/Agent_Profile.apsx?aaid=45" etc etc)

I just type

Global.GotoAgentService(Me.response, AgentService.MessageCenter)

With intellisense filling in most of it for me.

Are there any pitfalls to redirecting from Global...given that it's such
special file. I dont want to get caught out by some invisible hand.

TIA
Richard