Continuous Azure website deployment always picks the wrong design

Question

I have the following folder structure in my TFS online:

Folder names also match the project names in the solution.

Legend:

• green dot: web api 2.0 project
• red dot: class library
• blue dot: the console application is added as a web application to the web project.
• gray dot: the console application is used only for testing

Working folders for defining an assembly:

The build definition was created automatically by connecting Azure to TFS online, and I just changed the folder, so instead of the Team Project root folder, it points to the folder of this branch containing the solution file and the folders in the first image.

(This indicates the folder containing the solution files, as well as all subfolders from the first image.

Problem: When I run the assembly, it always selects the ExpiringRateCardsWorker project (even now the Web project has been renamed (both the directory and the project file) to start with underscore, so it will be the first in alphabetical order.

Successful deployment is what I see in Monaco:

How can I pick up a web project?

Edit: The question has been closed to be a duplicate of this . Since then, I tried the solution there, but the /site/deployments folder is empty on FTP, it does not contain deploy.cmd , so my question still did not answer unsuccessfully.

Answer 1

I had a similar problem deploying a MVC application for Azure using a CD in VSO. This issue is somehow related to the WebJob publishing mechanism.

At the moment, I have not been able to deploy my entire solution using WebJob at one time, but when I removed all the webjob * .json and Microsoft WebJobs Publish files from the NuGet package from my solution, I was able to deploy my MVC application as usual.

I think I will have to deploy these parts of the application separately, for now.