Refactor NLog configuration in Startup.cs

Removed commented-out code for NLog setup and simplified
the handling of development environment logging. Retained
the use of the developer exception page while eliminating
unnecessary complexity related to loading different
NLog configuration files and hidden assemblies.

Author: StuartFerguson

TransactionProcessing.SchedulerService/TransactionProcessing.SchedulerService/Startup.cs

@@ -74,27 +74,7 @@ public void Configure(IApplicationBuilder app,
             ConfigurationReader.Initialise(Startup.Configuration);
 
             String nlogConfigFilename = "nlog.config";
-
-            //if (env.IsDevelopment())
-            //{
-            //    app.UseDeveloperExceptionPage();
-            //    string directoryPath = Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location);
-            //    LogManager.AddHiddenAssembly(Assembly.LoadFrom(Path.Combine(directoryPath, "Shared.dll")));
-
-            //    var developmentNlogConfigFilename = "nlog.development.config";
-            //    if (File.Exists(Path.Combine(env.ContentRootPath, developmentNlogConfigFilename)))
-            //    {
-            //        nlogConfigFilename = developmentNlogConfigFilename;
-            //    }
-            //}
-            //else
-            //{
-            //    LogManager.AddHiddenAssembly(Assembly.LoadFrom(Path.Combine(env.ContentRootPath, "Shared.dll")));
-            //}
-
-            //loggerFactory.ConfigureNLog(Path.Combine(env.ContentRootPath, nlogConfigFilename));
-            //loggerFactory.AddNLog();
-
+            
             if (env.IsDevelopment())
             {
                 app.UseDeveloperExceptionPage();