Why? Does it work completely differently in the unit test class than in the
web application? If so, why? Because you want to focus on the unit only?
Okay, are you using mock objects and injecting them? If not, why not?
The point I am getting to is there is no reason a class should operate
differently under test than live, except perhaps having mocks for
dependencies to avoid actually calling a database, fvor example.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
*************************************************
Think outside of the box!
*************************************************
<br************@hotmail.comwrote in message
news:11**********************@k70g2000cwa.googlegr oups.com...
>I have a DLL that is sometimes used in a ASP.NET 2.0 web app, sometimes
it is used by a console app (unit test). How can I determine if the
current instance (it's not a static class) is definitely running inside
ASP.NET?