Git CI/CD w/ Default Build Process Template does not build all Projects in Solution?

Question

Good evening,
I have a VSO hosted git based project that hosts a Azure Cloud Service, particularly one VS solution (.sln) that contains the Azure Cloud Service project (.ccproj), the Web Role .csproj, some auxiliary projects (again .csproj) and one (MS)Test project (again
.csproj). All these .csproj are enabled to be build in both Release and Debug configs (everything's Any CPU).
Now inside Azure I did link the corresponding Azure Cloud Service to that VSO project, Azure/Vso did prepare the _CI (or was it _CD?) build definition with the
GitContinuousDeploymentTemplate12.xaml selected and in general deployment works perfectly fine
BUT
.. but the problem is that I really don't know how to solve after hours of fiddling - the *.Tests is not built and therefore no tests are fond and run.. and I wonder why. More precisely, none of the projects that are not referenced by the Cloud Service's Web
Role (it's the only role atm for the CS) are actually built.
Not sure whether this is a Cloud Service build thing or one of the Git Build Template, but how and where can I make sure all projects inside the selected .sln (see screenshot) ARE actually built as defined in the selected/defined Solution config? What's going
on here?
Thanks,
-Jörg
Here's my local view in combination with the build / process definition. As you can see the .tests.dll IS built as part of Release & AnyCpu for the .sln, but when running the build on VSO (& downloading the drop folder), it is NOT included/built..
looking at the logs also reveals that the *.tests.csproj is NOT built.

Answer 1

Good Morning!
thanks for the reply but unfortunately I cannot reference the Test Project from the CS Web Role as this is the very same project the Test Project actually contains tests for and circular dependencies (Test > Web Role Project and > back to the Test
Project is not possible).
The logs themselves just reflect the observed behaviour: they do not mention or contain the .Tests.csproj at all (or the other projects not referenced directly by the Web Role) and even though the selected solution does contain these projects, strangely
the first few lines in the msbuild log are:
Build started 1/7/2015 12:03:49 AM.Project "C:\a\src\Sources\Backend\Backend.sln" on node 1 (MyProject_Backend:Publish target(s)).
ValidateSolutionConfiguration:
Building solution configuration "Release|Any CPU".
Project "C:\a\src\Sources\Backend\Backend.sln" (1) is building "C:\a\src\Sources\Backend\MyProject.Backend\MyProject.Backend.ccproj" (2) on node 1 (Publish target(s)).
..so why is it only or specifically picking up the Azure Cloud Service .ccproj / project as the only buildable target & why not what's specified in the Solution? What's the whole point of tests if they are for some odd reason dropped?
Strangely enough, this only appears to be happening with the GIT template - I had this project originally in TFVC and did the same thing - linked from Azure to that TFVC project (same solution) and with that particular build template it
did build & run the tests.
Any ideas / suggestions or if you need any more specifics, please let me know.
Thanks!
-Jörg