launchsettings.json, appsettings.json, web.config

35
votes

I have a couple of confusions:

  1. I published an ASP.NET Core project and I do not see launchsettings.json in bin\Release\PublishOutput. If I use Octopus, how do I configure attributes based on server type?

  2. Is it possible to move launchsettings.json to the root folder instead of under properties?

  3. If I want to use only one json like appsettings.json, can I merge both in the root folder?

  4. Can web.config be used instead of launchsettings.json, and how?

1
asp.net-coreoctopus-deploy
launchSettings.json is only for Visual Studio. Other than that, it's not clear what you're trying to do. - Chris Pratt
In general, it is discouraged on Stack Overflow to put more that one question in one post, With your future questions please follow this guideline :) - Will Barnwell
@Chirs Pratt, I recently hosted asp core app on linux box and when I change the values of this launchSettings.json file of key applicationUrl, and hit dotnet run, hosting is configured to this value. So I think this file has its effects on dotnet run command also. If so, is this file read on CreateDefaultBuilder() method in Program.cs ? - XPD
When an app is launched with dotnet run: launchSettings.json is read if available. environmentVariables settings in launchSettings.json override environment variables. - Fish

1 Answers

38
votes

Answers to your questions:

  1. As Chris Pratt mentioned in comment, launchSettings.json is only used by Visual Studio. You can use Octopus variables in Octopus.
  2. Don't need launchSettings.json for publishing an app.
  3. If there are settings that your application needs to use, please store them in appsettings.json. This will make deployments easier, since Octopus recognizes this file by default.
  4. It depends on your requirements. web.config is used by IIS, not by your .NET Core application directly, hence IIS limitations to what you can configure might be applied.

Hints.

  • If you have some environment specific variables, you can store them in environment specific appsettings.json, e.g. appsettings.Release.json.
  • You can leave placeholders for Octopus variable substitution in your appsettings.json file, especially in environment specific one, e.g. appsettings.Release.json may contain a config value like "#{ConnectionString}" and during deployment Octopus would substitute this placeholder with the actual value from Octopus variables.