Well, ASP.NET often has an HttpContext.Current, but note that
personally I find this a bit hacky. It also doesn't work for things
like WCF hosted in IIS. I generally prefer to use a provider model,
where-by those bits that depend on the architecture are abstracted
through an interface (with some mechanism to register and obtain the
provider); in the web app I register one provider (perhaps using an
HttpModule to configure via web.config), and in the client I register
another.

But I guess it depends on how big the change is...

Marc

Smithers,

   One way I know of is to set a reference to System.Web.dll and then check
the static Current poperty of the HttpContext class.  If this returns null,
then there is no HttpContext, and no ASP.NET.  Of course, this is only
applicable if you are actually processing a page.  Calling this outside of a
request pipeline in ASP.NET will still return null, so if you need this for
one-time initialization, you might have to look for another option.

You need to revisit your design.  Those "couple of things" likely either
don't belong in the library or need to be "passed" by the client at the time
of use.

-ralph

In the past I had always checked the current process image name.  If it was
"w3wp.exe" then I knew it was running under IIS.  I suggest you also check
against "WebDev.WebServer.Exe" since this is what VS 2005 uses during
development.  If I find either of these 2 I assume I'm running in a web
application - otherwise assume WinForms.

- Brian