Hello,
This question is a reproduction of the question I made on stackoverflow: <a class="postlink" href="http://stackoverflow.com/questions/43900451/asp-net-boilerplate-application-layer-and-web-layer">http://stackoverflow.com/questions/4390 ... -web-layer</a>
<a class="postlink" href="http://stackoverflow.com/questions/43900451/asp-net-boilerplate-application-layer-and-web-layer">http://stackoverflow.com/questions/4390 ... -web-layer</a>
I am using the ASP.Net BoilerPlate, a starting point for new modern web applications using best practices and popular tools. I am making an MVC, Web API, single page web application.
But I have noticed that based on the documentation that the Nlayer is based like bellow:enter image description here where you can see it better on the link (<a class="postlink" href="https://aspnetboilerplate.com/Pages/Documents/NLayer-Architecture">https://aspnetboilerplate.com/Pages/Doc ... chitecture</a>)
What is strange for me is that the management of DTOs and DTO mappings are made on the Application layer, I tough it would be made on the Web Layer on the ASP.Net MVC Controller or on the Web API Controllers, that would call the Application Layer and from the Controller it would make the mapping of DTOs.
But it seems that the MVC Controllers are not even used according to it's example linked on the documentation (<a class="postlink" href="https://www.codeproject.com/Articles/1043326/A-Multi-Tenant-SaaS-Application-With-ASP-NET-MVC-A">https://www.codeproject.com/Articles/10 ... -NET-MVC-A</a>).
If I make the DTO mapping in the Controller and make the controller Application layer responsable only to call the Service and retrieve Entities is not a better practice ?
1 Answer(s)
-
0
Hi,
Thanks for your good explanation. Here what we think about it <a class="postlink" href="https://aspnetboilerplate.com/Pages/Documents/Data-Transfer-Objects">https://aspnetboilerplate.com/Pages/Doc ... er-Objects</a>.
Thanks.
