title: Deploy with Visual Studio Team Services from separate front-end/back-end repositories
body: <p>My team is doing a single-page application that is served from an ASP.NET application, which is deployed via Team Services (was Visual Studio Online).</p>
  
  <p>However, using the <strong>same</strong> Git repository for front-end and back-end code – with the standard <code>wwwroot</code> directory – poses some problems with tooling and project structure; it becomes messy.</p>
  
  <p>The team would have better separation of concerns, and not least would it allow for a more standardized repository structure, both for back-end and front-end code, if we had two separate repos.</p>
  
  <p>Is it possible to separate the front-end code out into its <strong>own repository</strong> (which would have a standard build setup, the result of which goes in <code>wwwroot</code>), but then deploy <strong>both</strong> repositories as a single application with Team Services?</p>
  
  <p>Is this a job for Git Submodule or Subtree?</p>
  
  <p>Or perhaps the front-end could be packaged as an NPM module that is pulled into the .NET repository on each version change?</p>