One Problem

The solutions above assume your Git repository has only one project in it at the root level. This usually isn't the case and definitely isn't in our case, so we need, somehow, to specify which project to use (similar to how we chose the branch to deploy from) and where to find it in the repo. This can be accomplished by providing a configuration file for the automation tool that Azure uses to build and deploy our code.

The tool they use is called Kudu. There are several ways of customizing it, but the easiest is to provide a .deployment file at the root level of your project. In it you simply provide a line to specify the path to the ___.csproj file of the project to use.

Details can be found in the Kudu documentation here, and an example in the class repository in commit c38fcfa. Note that this is in the example2-nodb branch and it deploys the Example2 project. The deployed project can be found at cs461testintegration.azurewebsites.net