Asp.Net Program Architecture
Posted
by Pino
on Stack Overflow
See other posts from Stack Overflow
or by Pino
Published on 2010-05-26T20:34:57Z
Indexed on
2010/05/26
21:11 UTC
Read the original article
Hit count: 481
I've just taken on a new Asp.Net MVC application and after opening it up I find the following,
- [Project].Web
- [Project].Models
- [Project].BLL
- [Project].DAL
Now, something thats become clear is that there is the data has to do a hell of a lot before it makes it to the View (Database>DAL>Repo>BLL>ConvertToModel>Controller>View). The DAL is Subsonic, the repositorys in the DAL return the subsonic entities to the BLL which process them does crazy things and converts them into a Model (From the .Models) sometimes with classes that look like this
public DataModel GetDataModel(EntityObject Src)
{
var ReturnData = new DataModel():
ReturnData.ID = Src.ID;
ReturnDate.Name = Src.Name;
//etc etc
}
Now, the question is, "Is this complete overkill"? Ok the project is of a decent size and can only get bigger but is it worth carrying on with all this? I dont want to use AutoMapper as it just seems like it makes the complication worse. Can anyone shed any light on this?
© Stack Overflow or respective owner