Converting ASP.NET MVC to n-Tiered Architecture
Posted
by Jeff
on Stack Overflow
See other posts from Stack Overflow
or by Jeff
Published on 2010-01-05T06:26:05Z
Indexed on
2010/05/24
15:21 UTC
Read the original article
Hit count: 242
I just built an application using ASP.NET MVC. The programmers at my company want to build all future modules using n-Tiered (Presentation Layer, Business Logic Layer, Data Access Layer) architecture.
I am not the programmer and need to know why this makes sense? Do I have to completely rewrite the entire code or can it be converted?
We are building an HRIS system with Business Intelligence.
Somebody please explain why or why not this approach does or does not make sense.
© Stack Overflow or respective owner