How do I access 'Request' from a Library?

[Robert W.]

In one of my business objects I wanted to include a method like this:

public static void PageRedirect(string pageName)
{
Response.Redirect(Request.ApplicationPath + "/" + pageName);
}

The class is referencing 'System.Web' but yet I'm getting a compile error in
regard to "Request". How come this method works if sitting in the aspx.cs
file but not in the cs file in my business object?
--
Robert W.
Vancouver, BC
www.mwtech.com

[tedqn]

yep, encountered this problem yesterday. If not executed directly as a
page, need to use.

Imports System.Web

HttpContext.Current.Request.ApplicationPath

HttpContext.Current.Response.Redirect

[Robert W.]

Excellent. Thanks!!!

--
Robert W.
Vancouver, BC
www.mwtech.com

"te***@yahoo.com" wrote:

yep, encountered this problem yesterday. If not executed directly as a
page, need to use.

Imports System.Web

HttpContext.Current.Request.ApplicationPath

HttpContext.Current.Response.Redirect

[Joerg Jooss]

Thus wrote Robert W.,

In one of my business objects I wanted to include a method like this:

public static void PageRedirect(string pageName)
{
Response.Redirect(Request.ApplicationPath + "/" + pageName);
}
The class is referencing 'System.Web' but yet I'm getting a compile
error in regard to "Request". How come this method works if sitting
in the aspx.cs file but not in the cs file in my business object?

The reason you can easily access Request, Response and other intrinsic objects
is that these are properties of the Page class. If you want to use them in
a library, you'll have to pass them as method parameters.

Cheers,
--
Joerg Jooss
ne********@joergjooss.de

[Joerg Jooss]

Thus wrote Joerg,

The reason you can easily access Request, Response and other intrinsic
objects is that these are properties of the Page class. If you want to
use them in a library, you'll have to pass them as method parameters.

I shouldn't have said "have to" -- of course one can use HttpContext.Current
to grab the intrinsics, but I usually prefer to use rather explicit interfaces
and not rely on magic (i.e. runtime or host dependent) static members.

Cheers,
--
Joerg Jooss
ne********@joergjooss.de