Why would you believe there's a way to do this? Objects don't have the
notion of a "creator". You need to tell them about objects.

It's possible that there's some thread-static way to get to the
"current page" via HttpContext.Current.Request or something similar...
but there's no general solution.

If you want to give access to the reference, why don't you want to
change the constructor? You're really trying to add state without
adding state...

Hello Microsoft,

You can use the HttpContext.Current static variable. You can access both
the current page and the session from there.

--
Jesse Houwing
jesse.houwing at sogeti.n

Yes, you can do this, as Jesse has mentioned, by working through current
context.

There is also a good reason why this, as a rule, is not a good idea. You are
tightly coupling your class (or class library) to a web application. This
does a couple of things:

1. Makes it difficult, if not impossible, to unit test using unit testing
frameworks, as you have forced a dependency that cannot easily be injected,
if at all

2. Forces a complete redesign of your application if you ever move to
another type of library (web service, smart client, etc.)

You are best advised to grab the info you need off the page before you fire
off the library, as this leaves no circular dependencies.

*************************************************