<div>
<div class="content wysiwyg-content">
When building n-tier application, in DAL and BLL, if there is any changes in the future, do we modify those classes we create earlier, or do we use inheritance? Also, when building asp.net project, would you recommend to use n-tier? It looks like you have to make a lot of effort to this.<br />
<br />
<a href="http://www.mindstick.com/Articles/d36ceb0f-018c-4979-b2f5-a4a1e616cb5b/?N-Tier%20Architecture%20in%20ASP.NET" rel="ugc">http://www.mindstick.com/Articles/d36ceb0f-018c-4979-b2f5-a4a1e616cb5b/?N-Tier%20Architecture%20in%20ASP.NET</a>
</div>
</div>


When building n-tier application, in DAL and BLL, if there is any changes in the future, do we modify those classes we create earlier, or do we use inheritance? Also, when building asp.net project, would you recommend to use n-tier? It looks like you have to make a lot of effort to this.

http://www.mindstick.com/Articles/d36ceb0f-018c-4979-b2f5-a4a1e616cb5b/?N-Tier%20Architecture%20in%20ASP.NET

N-Tier Architecture in ASP.NET

The successor to Active Server Pages, ASP.NET websites utilize the .NET framework to produce dynamic, data and content-driven web applications and services. ASP.NET code can be written using any .NET supported language. As of 2009, ASP.NET can also apply the Model-View-Controller (MVC) pattern to web applications