«

"Mark Rae [MVP]" <> wrote in news:OLyCPYpRKHA.1268
@TK2MSFTNGP04.phx.gbl:

> HttpContext.Current.User.Identity.Name

The only potential issue I see here is you end up tightly coupling the
library to web applications only. This may not be a big issue, but my
preference is to pull identity and feed to the library to avoid the
coupling.

Peace and Grace,

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************

"Mark Rae [MVP]" <> wrote in news:eJF#JQuRKHA.5108
@TK2MSFTNGP02.phx.gbl:

> True, if the class needs to be reusable across project types...

I tend to assume this direction first and then adjust based on other
factors. I have yet to come up with a case where I felt tightly coupling to
the UI was the proper decision. i am not saying that someone cannot come up
with a case, however, as I have not worked through all types of problems.

Peace and Grace,

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************