title: Service Fabric Deployment Error: ServiceManifest.xml is missing for service
body: <p>I have added a Stateless Service Fabric project to my solution and set it up as a Web Api self host.
  I have touched nothing in any of the files added by Visual Studio. The only thing that went slightly wrong was a Git merge error on the solution file, causing me to have to add the projects again manually.</p>
  
  <p>Projects are named as follows:</p>
  
  <ul>
  <li>Project name/sfproj: ClientCore.CommandStackApi.Deploy</li>
  <li>Service name/csproj: ClientCore.CommandStackApi</li>
  </ul>
  
  <p>When I try to deploy, I get the following error:</p>
  
  <blockquote>
    <p>The BuildLayout of the application in
    C:\SfDevCluster\Data\ImageBuilderProxy\AppType\ClientCore.CommandStackApi.DeployType
    is invalid. ServiceManifest.xml is missing for service 
    ClientCore.CommandStackApiPkg.</p>
  </blockquote>
  
  <p>When I compare files, and all the project settings I can think off, with my other Service Fabric projects everything looks fine, but it keeps complaining that the Service Manifest is missing. The only thing I noticed, was the SF project missing a dependency to the CommandStackApi project, but this didn't change anything.</p>
  
  <p>I've tried on two different computers, the last of which had a fresh install of the Service Fabric SDK etc.</p>
  
  <p>I'm guessing it would work if I remove all projects and set everything up again, but this also happened earlier, when I tried to construct the deploy package and powershell script exactly from the MSDN guide, so I would really like some insight into what I might be doing wrong. If this happens to a more mature project, I won't have the option to recreate the solution from scratch and tap into the Visual Studio blackbox magic setup, that it must be doing behind the scenes. Any ideas, for what might be wrong, would be appreciated.</p>