vendredi 6 janvier 2017

VIsual Studio solution structure

I'm working on a personal project. This project is a simple system for take table orders in a restaurant and manage the menu courses. I'm want to use this technologies:

  • SQL Server
  • Entity Framework
  • ASP.NET MVC Web API
  • AngularJS

I started to create the Visual Studio solution and the various projects:

Libraries: This project is used only for download the third parties libraries as EntityFramework and AutoMapper.

enter image description here

Domain: This project is used to store EntityFramework edmx and its classes.

enter image description here

DataAccessLayer: This is the only project that uses directly EntityFramework objects and provides methods for get entities from database but doesn't return them, returns DTO objects with same properties of the entities. I use AutoMapper for re-map entities to DTO and reverse.

enter image description here

BusinessLogicLayer: This project is used to do business operations before call Repository methods, for example log the requested operation. This project passes to Repository methods only DTO objects that after will be mapped in EntityFramwork objects

enter image description here

Common: Stores classes, methods, variables, constants and any other stuff that have been used across all other projects.

enter image description here

WebAPI: This project exposes Business Logic methods to be consumend by user interface.

enter image description here

I've not already created the web project it will be a simple ASP.NET Web Application.

OK, this is all I did at the moment. I wish to have some opinions about this project structure, usually at work other decides solution structure and it's always the same anytime, so I started this project alone. I read something in internet but I'm still sure wich is the best way.

Thank you very much for your time and opinions.

Aucun commentaire:

Enregistrer un commentaire