Why have the api in the same project as the web?

Apr 4, 2014 at 6:56 PM
I like the idea of having the api in the same project as the web, but I'm used to the api being in a separate project. What are your thoughts on this?

Long: Totally up to you, most teams start in having them in one project, and end up splitting the two when the time comes (scaling, separation of concerns, etc.). Most cases they do this so they don't have to deal with Identity management between the mvc app for presentation layer and the mvc app for web api (ADFS, UAG, Azure AD, etc.) or simply put KIS (Keep it simple) until they cross the bridge where they need to segregate the two.
Marked as answer by lelong37 on 4/6/2014 at 5:55 PM