Hi,

You can refer my blog post to add value in web.config.

https://world.episerver.com/blogs/ravindra-s--rathore/dates/2019/10/playing-with-episerver-webconfig-settings/

Hi Ravindra,

Thanks for your response.

Is there any other way by using only configs like any transform files or any specific that episerver will pick the config from another config file.

Because the change which I wanted to make should exist all the time and it is part of add-on, so I may not have the initial call with me.

Regards,

Manik

Then you can apply it using the tranform file using the visual studio slow cheetah extension.

As I am using it from add-on , I don't have that feasibility of updating using transforms. Because add-on once installed it will copy my dlls and config. So I won't have the access to the code base. What I am developing is a add-on and in that add-on I require changes in web.config.

Regards,

Manik

I think you can use Episerver initialization module in your add on and then write the logic in initialization module to update the values in web.config. I haven't tried this but I think it should work.

Refer my above blog post to update the property in web.config

Writing in web.config on runtime is simply and strongly not recommended, the reason is obvious that there will be an application to recycle all the time, think can go more complex if the site is in the cloud. Site visitors will face downtime. and will not be able to do any further action on AddOn also.

There are many ways to manage this depending on requirements, hope you would have already visitied https://world.episerver.com/documentation/developer-guides/CMS/add-ons/Developing-Add-ons/

/K

if add-on is not deterministic - you might get into infite restart loop (app starts -> addon writes to web.config -> app restarts -> addon writes to web.config -> repeat..)

please don't touch web.config -> it's not recommneded. 

if you need modify profile for example -> I would recommend to create web.config transform file (web.config.transform) where you can add your required changes. these changes will be applied during nuget package installation. more info - https://docs.microsoft.com/en-us/nuget/create-packages/source-and-config-file-transformations