Replace NLog methods that are now obsoletes

[jtkech]

No description provided.

[snakefoot]

Instead of depending on assembly-scanning, then it could nice if just doing registration of the single custom LayoutRenderer:

var fileName = Path.Combine(env.ContentRootPath, configFileRelativePath);
LogManager.Setup().SetupLogFactory(factory => factory.AddCallSiteHiddenAssembly(typeof(AspNetExtensions).GetTypeInfo().Assembly))
          .SetupExtensions(ext => {
                ext.RegisterLayoutRenderer<TenantLayoutRenderer>(TenantLayoutRenderer.LayoutRendererName);
                ext.RegisterNLogWeb();
          })
          .LoadConfigurationFromFile(fileName);
return LogManager.Configuration;

[snakefoot]

Notice that builder.UseNLog() with NLog.Web.AspNetCore v5, will automatically load nlog.config from the env.ContentRootPath.

So ConfigureAppConfiguration could be changed to just:

builder.ConfigureAppConfiguration((context, _) =>
{
   var environment = context.HostingEnvironment;
   LogManager.Configuration.Variables["configDir"] = environment.ContentRootPath;
}

[snakefoot]

Notice that builder.UseNLog() with NLog.Web.AspNetCore v5, will automatically load nlog.config from the env.ContentRootPath.

So ConfigureAppConfiguration could be changed to just:

builder.ConfigureAppConfiguration((context, _) =>
{
   var environment = context.HostingEnvironment;
   LogManager.Configuration.Variables["configDir"] = environment.ContentRootPath;
}

[jtkech]

@snakefoot I did the changes, thanks for the feedback!

[snakefoot]

Happy that you approved my suggestions :)