Tag Info

New answers tagged

-1

You definitely should design your application with discrete layers - data access, business logic, UI etc. However, I'm going to go against the trend and advise you not to use Entity Framework for your data access layer. An ORM should be purely a mapper between database and POCO classes. In my eyes, EF breaks the single responsibility principle by trying to ...


1

What I think you want is domain driven design, In simple terms separation of concerns. Read about it and you are good to go. To keep it simple since you say yo new, Just have User Interface layer in its own project, a service / logic layer in its own project. a data access layer in its own project and other layers depending on the project. For the data ...


0

I think that answer to behavior extension cannot be abstracted itself - it depends on concrete problem. If we assume that pulling sledge is unusual dog behaviour* (encapsulate what varies) another level of abstraction would be the answer, but it would be different in case of pulling-sledge-contest-app where a dog can pull sledge in generall, but some are to ...



Top 50 recent answers are included