Is it a good idea to add WebAPI into an existing ASP.NET MVC project? -


we have existing asp.net mvc 5 project. want use webapi too.

is idea install webapi mvc project using nuget? or better create new project in same vs solution webapi? if latter, how routing done?

i gather having mvc , webapi in same project can cause issues dependency injection. true?

you can put in same project, install nuget package , add startup classes (you can see how in template).

i can't speak dependency resolver issues though.

however ask myself first why want mvc + web api, in many cases can use mvc job, , stay 1 framework.

i'd consider web api if want use content negotiation, odata or if have lot of ready made web api code want port.


Comments

Popular posts from this blog

How to access named pipes using JavaScript in Firefox add-on? -

multithreading - OPAL (Open Phone Abstraction Library) Transport not terminated when reattaching thread? -

node.js - req param returns an empty array -