In my classic ASP app I have over 30 subroutines and functions that handle UI events. I have these seperated from my main asp page using 3 server-side include files. With ASP.NET should I maintain this structure or create a code-behind page? If I did make a code-behind page would all 30 subroutines and functions have to sit in the same page? This would be a draw-back because at present they are grouped together based on similar functionality and roles, which makes it easy to find things. What is the difference between code-behind and server-side include?<BR><BR>Thanks,<BR><BR>masmithnow, I haven't seen your app, but that sounds like something I would put into class objects. A code behind page usually just pertains to a particular page, but class objects can be used across the entire app. Go take a look at IBuySpyStore.com and look in the docs. Notice all of their data layer stuff is in classes. This way you just call it when you need it, it's always "included" without sacrificing any performance since it's just hanging around in the DLL waiting to be called. With server-side includes I used to have a LIB.ASP file that contained all my logic, I just included it on every page. A problem with that is that it had to get parsed with every page that included it, including the functions/subs that were never called for that page. I don't know if that helps, but there you go...I'll look into that, thank you 