CODEWITHSUNDEEP
asp.net-mvcasp.net-web-api
Hernan Demczuk
Hernan Demczuk

Reputation: 405

Adding Web API Controllers to an MVC Project vs Adding a whole new Web API Project

I have an MVC application that uses MVC Controllers to return views. Now I want to expose an API to other applications to consume, as well as returning JSON data types for some SPA features in the same MVC. What are the differences between adding Web API Controllers to my MVC Project vs adding a whole new Web API Project?

Upvotes: 0

Views: 69

Answers (2)

Win
Win

Reputation: 62300

returning JSON data types for some SPA features in the same MVC

For that case, I'll place Web API inside existing MVC. By doing so, you can share business logic, services and even models.

In my case, I have SPA silos using AngularJS, and both MVC and Web API live happily in the same web application, and share business logic and data access layers.

It is worth noting that you can share Authentication cookie if you keep MVC and Web API together. Otherwise, it is pain in the neck to authenticate in both places at the same time, because Web API is token based and MVC is cookie based by default.

FYI: In new ASP.Net MVC 5, there won't be separate MVC and Web API anymore.

Upvotes: 1

Aman Sharma
Aman Sharma

Reputation: 1990

The only difference between the two is reusability and good design practice. I highly recommend to use it in a separate project. Then, later on, you will be able to reuse it without much or any effort.

Another advantage to segregate is the impact on testing required for any changes made. If you keep the projects different then if later on you change anything, the domain for the re-testing efforts would also be just the second project.

Upvotes: 0

Related Questions