Multiple appsettings.json in .net core (Dev, QA, PROD) using appsettings variable

No video

Multiple appsettings.json in .net core (Dev, QA, PROD) using appsettings variable

Рет қаралды 27,041

Күн бұрын

In this video, I will show you how can you manage multiple appsettings.json files in .net core.
Check out the medium article : / multiple-appsettings-j...
Playlist about Websockets
• Video
Playlist about JWT
• JWT Token
Check out the playlist about RSA
• RSA
Amazon affiliate link for c# book: amzn.to/31q2sXV

Пікірлер: 19

@madruga2112 2 жыл бұрын

Thanks!! The only tutorial that worked for me!

@Nicetrycutiepie 7 ай бұрын

very clear and detailed explanation bro. have subscribed ur channel

@liveabhishekshukla 4 жыл бұрын

Nice and detailed video

@TechnoSaviour 4 жыл бұрын

Thanks

@HaribabuPasupathy Жыл бұрын

Love you buddy

@sukhpalsandhu6341 3 жыл бұрын

Good video to explain how it works, could have used the ASPNETCORE_ENVIRONMENT setting in launchSettings.json, already scaffolded.

@TechnoSaviour 3 жыл бұрын

But if you want to host multiple environment in same server but different ports then environment variable won't help

@TechnoSaviour 3 жыл бұрын

Also you need to have access to the server if you want to deploy another env like using dev server machine for QA

@TechnoSaviour 3 жыл бұрын

Plus if you have multiple servers it becomes a problem

@bobweiram6321 Жыл бұрын

Even worse, the Development, Production and Stage are overwritten.

@_hajiyevemin 2 жыл бұрын

From my point of view instead of seperate appsettings,json file, in one appsettings.json file we can create env, qa connectionstrings

@TechnoSaviour 2 жыл бұрын

Yes, this is needed when you have one server that hosts multiple environments and you are not using docker

@mmahon512 3 жыл бұрын

gotcha, very good job! How can you specify which app.settings file to load from the dotnet build cli? something like dotnet build -c qa

@TechnoSaviour 3 жыл бұрын

you can use the -c or -configuration to pass which configuration you need while building: Ex - dotnet build --configuration QA

@ItsmeRajivS 10 ай бұрын

Good video but how to use in release pipeline

@purplepanther4153 3 жыл бұрын

Love the video, thanks for your work. Would you have any reference to connect different database based on user selection from dropdown. let say I don't know what to user select as far as the database goes. How would I be able to pass the db connection to my web api on start up..

@vishalkeshri9695 11 ай бұрын

Wow amazing 😊.. and ho can do the same in dot net 6???

@puurusottamsaha8971 3 жыл бұрын

But still i need to remember the "env" while deploying the app.. suppose by mistake i make like this "env=QA" instead of PROD and i deploy the app to production.its a problem.is there any way to avoid this issue??? I understand we should not deploy the config file to prod ,there should be one static config file present in prod every time when we make a release..But for my application i need to add lots of key to config /setting.json file while making a releases ..so i am bound to push my local config file to prod every time when i make a release ..and sometimes i forget to change the connection string of DB..just wanted to know if i can have a way to automate these issue i amusing dot net code.thanks in advance