This is probably a fringe case, but here’s the scenario. I have a site for a client that is actually broken down into several projects, but not in a single solution. The layout looks something like this:
- Root Folder
- index.html (basic home page with links to project roots)
By default, if you were to have your root folder checked into source control, and had Azure deploy from the root folder, you’d either have only Project A deployed on the site, or most likely, the deployment would fail with a message that it doesn’t know what project to deploy.
There was nothing I could do to get around this situation, but I did come up with a way to make it work.