All my past projects have been fairly simply MVC web applications that used Entity Framework to interact with my SQL DB, in those apps I would break up the solution it up into 3 projects; WebUI, Domain, and Core. This worked fine but now as I am making a new web app that will interact with a new WebAPI so I can eventually build out mobile apps. My question is how best do I build a solution for this? Would it be all one solution that would be split into WebAPI, Domain, Core (Business logic), WebUI, WindowsApp, iOSApp, AndroidApp or should there be multiple solutions say 1 for the WebAPI, 1 for the Web App, and 1 for each Mobile App? With either way I do it where does the Entity Framework classes live to build out the Database? This is my first time building a structure for applications that interact with a WebAPI so I have no idea how to build out the structure for everything.
Just a note as well, these are personal projects that for the fordable feature I am also the only developer on the projects. I am using VS 2013 (looking at jumping into VS 2015 for this project as ASP.Net vNext looks very good for this project) as well as TFSOnline. I want to use Azure resources for everything as right now I am using Azure VMs but am looking into leveraging other Azure resources to make this a more capable app as it grows.