title: No .NET Core 2.0 appsettings on a published console app
body: <p>I'm in the process of producing an automated build process for our team's first .NET Core app. Our process is to produce an artefact package (contains all the different types of apps, database migration scripts, etc.) on our build server, and then in a separate step deploy that package to the various environments that we have (dev, test, demo, training, live, etc.)</p>
  
  <p>In full .NET Framework apps, we use Slow Cheetah to perform config transforms on things like windows services and console apps so that when the app is installed on the target system it has the correct configuration.</p>
  
  <p>Now with the .NET Core 2.0 app we have I'm seeing two problems:</p>
  
  <ol>
  <li><p>The publish operation (which as far as I can see is the preferred way of getting some sort of artefact package for a single app) doesn't contain any appsettings files (except for ASP.NET Core apps).</p></li>
  <li><p>If I scripted the copy of the appsettings myself how does the deployed version know which appsettings..json to use? </p></li>
  </ol>
  
  <p>In fact, I'd rather not deploy anything other than the exact settings for that environment. It seems to me that deploying settings for all environments (or anything other than the exact configuration set for the target environment) is an accident waiting to happen. (<strong>EDIT: To emphasise that I would rather not be merging disparate sources of config at runtime because that would be a mess to debug if things aren't working right trying to figure out exactly which config element actually got applied.</strong>) So, how would I "merge" the environment specific items with the main appsettings.json file?</p>