3
In Visual Studio when we create a web project it gives you the options to mark:
Webforms MVC Web API
When MVC + Web API frame the two are in the same project.
There is some advantage/performance in using MVC + Web API in it project or it is better to separate the MVC from the Web API into different projects within the same Solution?
0
I don’t see a problem with working together, and that won’t lead to poor performance. But everything in systems development has to be analyzed in depth, if it is a large MVC project with a diversity of code, can be better two projects, but, there has the drawback of publishing, would have to publish separately in a domain and a sub-domain, not to have that mess of applications (own experience).
Then, analyze the environment, the amount of connection, the work and effort that the server will have to do, if it is a medium-sized project, you can do without fear. Larger projects the division would be the most ideal.
0
There is. The complexity is less, the Scaffoldings and the context of data may be the same, avoiding large rework.
Separation shall occur only if one disrupts the functioning of the other, in cases such as:
Browser other questions tagged asp.net-mvc-5 asp.net-web-api
You are not signed in. Login or sign up in order to post.