Using MVC.NET 5 with Entity Framework for Developing a REST API

Question

I am considering using MVC.NET 5 with Entity Framework for the development of a REST API to serve up data for consumption by a few Websites. Is there any compelling reason to wait for MVC.NET 6 or is there a best practice/more common framework for developing REST APIs. The reason I am focused to MVC is so I can enter/edit data via forms that reflect my database to more easily manage my REST data, but I am open to other options if there are more common pursuits.

My front end development is heavily focused towards HTML5 and a few JS libraries such as Angular and Backbone due to the design patterns.

Taiseer Joudeh · Accepted Answer · 2014-09-12 01:26:24Z

1

My recommendation is to built a stand alone Web API without mixing it with MVC 5, if you want to do it the right way use OWIN middle ware and add the components needed to build the API. For the front end and if you are going to build SPA, start new empty project which will hold only your SPA, and this project will talk to your RESTful API. For sure you need to allow CORS on the back-end API so it will accept calls coming from your SPA. You can read more about how you structure this on this post. http://bitoftech.net/2014/06/09/angularjs-token-authentication-using-asp-net-web-api-2-owin-asp-net-identity/

answered Sep 12, 2014 at 1:26

Taiseer Joudeh

9,0731 gold badge44 silver badges45 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Using MVC.NET 5 with Entity Framework for Developing a REST API

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related