Includes, code behind or user control ?????

[glycleric]

Okay - in classic asp - you shoved your db conenct stuff in a include file - nice and simple - what is the best way of doing this in ASP.NET<BR>Cheers<BR>I recently made this decision for some new applications and I decided to go with creating a namespace. I built a custom namespace and class that I use for creating db connections and checking user access. It works perfectly and is actually pretty easy to do.in my limited experience with asp.net, i've found that i like doing my own business objects in the form of code-behinds. it almost completely separates the logic and the interface which makes for well designed and easily manageable code. <BR><BR>i also love the idea of user controls because if you work for a client, it gives them the ability to manipulate the visual aspect through the use of control properties without touching a single line of code. very cool stuff...