Last post Jan 15, 2018 06:49 AM by Edward Z
Jan 13, 2018 08:27 PM|NickCullen|LINK
First post here, so be gentle!
I am creating a service ticket application just to learn the ins & outs of ASP.NET Core, and I am thinking about how I would go about creating a set up process for when a user installs the system on their servers for the first time.
For those of you who have used systems like Jenkins, OpenProject and the like, when you first install it they have a setup process for creating an admin account, database connection settings etc. all configurable by the user. This process only runs ones
and doesn't appear again after the user has done it (i.e. the 'setup process' :) ).
How could I do such a thing with ASP.NET Core? Creating the forms etc. isn't the problem for me, just how would I
safely save these settings the user enters and how to check (and load) that I only run the process once?
Jan 15, 2018 06:49 AM|Edward Z|LINK
>> just to learn the ins & outs of ASP.NET Core
What do you mean by “ins & outs”?
>> how I would go about creating a set up process for when a user installs the system on their servers for the first time.
What do you mean by this user? In general, we develop Asp.net Core site, and then end user to access the content. But, for your scenario, it seems there is an Asp.net Core project, and you want to make it enable to publish automatically.
Do you mean you want to configure the publishing process for Asp.Net Core or you want to configure the settings before running the Asp.net Core?
In general, any code in Asp.net Core will not run until it has been published and run.
You will need to create a publish application which will write the configurable settings by modifying the appsetting.json.