title: Is Adding System.Web on other projects than a web page a bad practice?
body: <p>I'm building an archetype of web project for my company, the idea is to have like a template to start building a new project with everything necessary already done, security, IoC, Logging, etc...</p>
  
  <p>I'm working on the security side of the template... and at the beggining I wanted to make a custom security provider... but then I realized, that Microsoft already did that with Membership... if any project would need a different provider... they would only need to change the web.config and that's it....</p>
  
  <p>But then it comes to my problem... If I want the different layers to be able to get users information... like the services layer (business services... not web services), I would need to include the System.Web and System.Web.ApplicationServices to that Class Library.</p>
  
  <p>Is that a bad practice? I don't want to re-invent the wheel and the Microsoft Membership model is enough for my scenario.</p>
  
  <p>Thanks!</p>