https://github.com/dnnsof...Platform/issues/3161
According to Andrew on "Issues Ready for Development" in Github link above we need to add support for Microsoft.Extensions.Logging and deprecate to remove current log4net Ilog in DNN 9. They need to co-exist for version 10 to allow removing for version 11.
Is anyone currently working on this? Seems like a top priority right now for an upcoming release.
Posted By Cody on 11 Mar 2020 12:18 PM awesome, I am going to really dive into the .NET Core conversions needed as well once I resolve about 2-3 more issues for DNN 9. Then I will be full steam ahead with .NET Core and hopefully make version 10 a blur of the past heading to version 11 at lightning speed. I have had a heavy load over past months but I do want to contribute towards this progress getting DNN to the latest core version so I can use Blazor :)
This is a little confusing, so I just wanted to clarify a bit for others perhaps reading/following this post (which is intended to be about logging). The journey to .NET Core is just that - a journey. There are no set-in-stone versions or set-in-stone dates for a full conversion to .NET Core. I just wanted to make it clear that the last statement about Blazor can be confusing. There is honestly nothing stopping anyone today from creating a Blazor module that runs on DNN Platform in its current state. We don't have to get to a full .NET Core implementation just to use Blazor (which is just a subset feature within .NET Core). Also, if Blazor is the end goal, there is another CMS project that is fully built on Blazor and that is oqtane, which is headed up by Shaun Walker, and leverages many of the key concepts in the original DotNetNuke. Feel free to check out this project too Cody.
These Forums are dedicated to the discussion of DNN Platform.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.