Best practices for how to Layer a ASP.NET/C# web app
<p>I have been working on an ASP.NET/C# web app for some time and its size has gotten way to large for how it is being programmed. It has become very hard to maintain and getting harder quickly, something that used to take an 1hr to update now takes about 3-4hrs. </p>

<p>I believe that reworking the app to use different layers would help solve many of these problems. However the more I read the more it seems that everyone does it differently, but achieve mostly the same goals.</p>

<p>I have seen layers such as Presentation/UI, DB, Business, Services, ect. It appears that a 3 layer may be the best but I am unsure.</p>

<p><strong>What layers should I have in a web app and what should each include or be limited to?</strong></p>

<p>Words from previous experience are most appreciated. </p>
