Modify configuration at runtime? about microsoft.extensions.logging.log4net.aspnetcore HOT 4 CLOSED

Hello, Thank you for your reply. I don’t think it is a good use of time to work on this issue: A user on StackOverflow pointed out this page: https://logging.apache.org/log4net/release/framework-support.html#Appenders The appender we’re trying to use isn’t supported by log4net when using .NetCore Standard 2.0! So we might be able to get this to work, perhaps with your help, but I think we need to find a new approach to how we do logging I don’t think I have a fork – I just cloned the repo so I could understand how to extend the code without changing it. (But I’m kind of a Github newbie). Thanks again for taking a look at this issue. Steve Gruverman | Application Developer II IDEXX Laboratories, Inc. | [email protected]<mailto:[email protected]> Phone: + 1 207 556 6981 Mobile: + 1 207 798 2893 From: Ángel García Santos [mailto:[email protected]] Sent: Wednesday, March 14, 2018 6:39 AM To: huorswords/Microsoft.Extensions.Logging.Log4Net.AspNetCore <Microsoft.Extensions.Logging.Log4Net.AspNetCore@noreply.github.com> Cc: Gruverman, Steven <[email protected]>; Mention <[email protected]> Subject: Re: [huorswords/Microsoft.Extensions.Logging.Log4Net.AspNetCore] Modify configuration at runtime? (#14) Hello @steven-gruverman<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_steven-2Dgruverman&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=RmIe1gmnt6yK0mEcsqffLM-n2yERkhj5v2w4_dNuka0&m=ap-VFuy5IHg4Gsg1xTjatKYKDLja5AI-SyNJLG88Ip0&s=4JW9rYSh6-9QIhKqZAGlm_LI0Bn1jSxlIMz2ORfQAVc&e=> , Thank you by your question. I will take a deeper look on your question as soon as possible, but I can tell you that, in my case, when I have to change the connection string for a given environment on the log4net.config file, as I have a CI/CD pipeline configured, I have an step that set up the proper connection string on the file when the application is on deployment process. I come back to you when I can check your fork (I think you have the whole code on there) and I will try to answer you. Thank you again. Regards — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_huorswords_Microsoft.Extensions.Logging.Log4Net.AspNetCore_issues_14-23issuecomment-2D372976908&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=RmIe1gmnt6yK0mEcsqffLM-n2yERkhj5v2w4_dNuka0&m=ap-VFuy5IHg4Gsg1xTjatKYKDLja5AI-SyNJLG88Ip0&s=3BcYdKP63S9jlTcYSCY5n0AHmnA_hXXd1ZEwzj4Gibc&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AM-5FwLjGGcDwJPTWe3e8-5Fl5r7LkZROULEks5tePNWgaJpZM4SnD0d&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=RmIe1gmnt6yK0mEcsqffLM-n2yERkhj5v2w4_dNuka0&m=ap-VFuy5IHg4Gsg1xTjatKYKDLja5AI-SyNJLG88Ip0&s=4Bdrip7zHwc1eGO84w-6z-4-mmDPFYWTSrh39t_UKi8&e=>.

Thank you for your suggestion and related information! Yes, fine if you close the issue. Steve Gruverman | Application Developer II IDEXX Laboratories, Inc. | [email protected]<mailto:[email protected]> Phone: + 1 207 556 6981 Mobile: + 1 207 798 2893 From: Ángel García Santos [mailto:[email protected]] Sent: Wednesday, March 14, 2018 11:05 AM To: huorswords/Microsoft.Extensions.Logging.Log4Net.AspNetCore <Microsoft.Extensions.Logging.Log4Net.AspNetCore@noreply.github.com> Cc: Gruverman, Steven <[email protected]>; Mention <[email protected]> Subject: Re: [huorswords/Microsoft.Extensions.Logging.Log4Net.AspNetCore] Modify configuration at runtime? (#14) Hi, Oh! I confuse your case with a fork that I see some days ago... Sorry for that. Maybe, if you want to do it, you can implement your own custom Log4Net appender using ADO or EF. You only need to inherit from AppenderSkeleton class and implement ActivateOptions, Append, Flush and OnClose methods. It is a little more complex that use an out of the box appender, but Log4Net is so flexible to allow you to create your custom appender from zero. Reference: https://jonhilton.net/2008/07/23/log4net-custom-appender/<https://urldefense.proofpoint.com/v2/url?u=https-3A__jonhilton.net_2008_07_23_log4net-2Dcustom-2Dappender_&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=RmIe1gmnt6yK0mEcsqffLM-n2yERkhj5v2w4_dNuka0&m=BmYheZIsyLowI_9otAq5ViSVeI6b-hBV7GJlOQblKuU&s=i2VR7K7WSQOAS-WemmpKs02vA2RuD1G4Zz_ZNlqs5BA&e=> I will close this issue if you don't have any inconvenient, then... Thank you again. Regards, — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_huorswords_Microsoft.Extensions.Logging.Log4Net.AspNetCore_issues_14-23issuecomment-2D373054006&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=RmIe1gmnt6yK0mEcsqffLM-n2yERkhj5v2w4_dNuka0&m=BmYheZIsyLowI_9otAq5ViSVeI6b-hBV7GJlOQblKuU&s=vCa0wp7l3PuakEt3tWwGcgbz7TXWKOLQHpQYRh6ARuI&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AM-5FwLpo3tTtMGx0DDNrmWJWMZTvlNiNsks5teTGJgaJpZM4SnD0d&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=RmIe1gmnt6yK0mEcsqffLM-n2yERkhj5v2w4_dNuka0&m=BmYheZIsyLowI_9otAq5ViSVeI6b-hBV7GJlOQblKuU&s=JW4mhPPhkro7NnVkb5nywBZ3r_mRTo5Pbujx-Y2BQFw&e=>.