AssemblyFinder throw Exception in .Net5.0(RC2) SingleFile

[xljiulang]

Unhandled exception. System.NotSupportedException: CodeBase is not supported on assemblies loaded from a single-file bundle.
at System.Reflection.RuntimeAssembly.get_CodeBase()
at Microsoft.Extensions.DependencyModel.DependencyContextLoader.GetNormalizedCodeBasePath(Assembly assembly)
at Microsoft.Extensions.DependencyModel.DependencyContextLoader.GetDepsJsonPath(Assembly assembly)
at Microsoft.Extensions.DependencyModel.DependencyContextLoader.LoadAssemblyContext(Assembly assembly, IDependencyContextReader reader)
at Microsoft.Extensions.DependencyModel.DependencyContextLoader.Load(Assembly assembly)
at Microsoft.Extensions.DependencyModel.DependencyContext.Load(Assembly assembly)
at Microsoft.Extensions.DependencyModel.DependencyContext.LoadDefault()
at System.Lazy1.ViaFactory(LazyThreadSafetyMode mode) at System.Lazy1.ExecutionAndPublication(LazyHelper executionAndPublication, Boolean useDefaultConstructor)
at System.Lazy1.CreateValue() at System.Lazy1.get_Value()
at Microsoft.Extensions.DependencyModel.DependencyContext.get_Default()
at Serilog.Settings.Configuration.Assemblies.AssemblyFinder.Auto()
at Serilog.ConfigurationLoggerConfigurationExtensions.Configuration(LoggerSettingsConfiguration settingConfiguration, IConfiguration configuration, String sectionName, DependencyContext dependencyContext)
at Serilog.ConfigurationLoggerConfigurationExtensions.Configuration(LoggerSettingsConfiguration settingConfiguration, IConfiguration configuration, DependencyContext dependencyContext)
at HostApp.Program.<>c.b__1_2(WebHostBuilderContext hosting, LoggerConfiguration logger)
at Serilog.SerilogWebHostBuilderExtensions.<>c__DisplayClass1_0.b__0(WebHostBuilderContext context, IServiceCollection collection)
at Microsoft.AspNetCore.Hosting.GenericWebHostBuilder.<>c__DisplayClass11_0.b__0(HostBuilderContext context, IServiceCollection builder)
at Microsoft.Extensions.Hosting.HostBuilder.CreateServiceProvider()
at Microsoft.Extensions.Hosting.HostBuilder.Build()
at HostApp.Program.Main(String[] args)

[nblumhardt]

Thanks for letting us know 👍

[BalintBanyasz]

This seems to be related: dotnet/runtime#41265

@nblumhardt Do you think that it can be fixed in Serilog.Settings.Configuration? Currently this is the only thing preventing me from upgrading my SingleFile WinForms App from .NET Core 3.1 to .NET 5.0. Thanks!

[nblumhardt]

Hi @BalintBanyasz - thanks for the note. Yes, I'd guess there is some way to detect this situation and avoid a crash, here. I am short of time to investigate at the moment; if anyone encountering this has time to debug and propose a fix, that would be welcome.

[tsimbalar]

In the meantime, you can maybe provide your own implementation of DependencyContext in the call to ReadFrom.Configuration(...) as a workaround ?

[murugaratham]

tried implementing

var functionDependencyContext = DependencyContext.Load(typeof(Startup).Assembly);
...
.ReadFrom.Configuration(configuration, "Serilog", dependencyContext: functionDependencyContext)

but still getting hit with

Unhandled exception. System.NotSupportedException: CodeBase is not supported on assemblies loaded from a single-file bundle.
   at System.Reflection.RuntimeAssembly.get_CodeBase()
   at Microsoft.Extensions.DependencyModel.DependencyContextLoader.GetNormalizedCodeBasePath(Assembly assembly)
   at Microsoft.Extensions.DependencyModel.DependencyContextLoader.GetDepsJsonPath(Assembly assembly)
   at Microsoft.Extensions.DependencyModel.DependencyContextLoader.LoadAssemblyContext(Assembly assembly, IDependencyContextReader reader)
   at Microsoft.Extensions.DependencyModel.DependencyContextLoader.Load(Assembly assembly)
   at Microsoft.Extensions.DependencyModel.DependencyContext.Load(Assembly assembly)
   at xxxx.Api.Program.CreateSerilogLogger(IConfiguration configuration)
   at xxxx.Api.Program.Main(String[] args)

[skomis-mm]

Hi guys, the current workaround for Serilog.Settings.Configuraton 3.1.0 is to use

.ReadFrom.Configuration(configuration, ConfigurationAssemblySource.AlwaysScanDllFiles)

and place all external configuration assemblies to the Using section:

"Using": [ "Serilog.Sinks.Console", "Serilog.Enrichers.Thread", ... etc ],

I've added NotSupportedException handling in the PR and updated the documentation.

[murugaratham]

any workaround for .net 5?

[skomis-mm]

@murugaratham sorry, I meant Serilog.Settings.Configuration 3.1.0

[murugaratham]

@skomis-mm yea, i am on .net 5 and i've tried .ReadFrom.Configuration(configuration, ConfigurationAssemblySource.AlwaysScanDllFiles) and also specifying using

"Serilog": {
    "Using": [
      "Serilog.Sinks.Console",
      "Serilog.Sinks.File",
      "Serilog.Sinks.File"
    ]
...

but i still get same error

[skomis-mm]

@murugaratham , interesting. Do you have any DependencyContext usage left in the code?

at Microsoft.Extensions.DependencyModel.DependencyContext.Load(Assembly assembly)
at xxxx.Api.Program.CreateSerilogLogger(IConfiguration configuration)

Are the any stack frames between these 2 lines?

[murugaratham]

The stack trace pasted was pretty much it

[skomis-mm]

var functionDependencyContext = DependencyContext.Load(typeof(Startup).Assembly);
...
.ReadFrom.Configuration(configuration, "Serilog", dependencyContext: functionDependencyContext)

Is the DependencyContext.Load called from CreateSerilogLogger(..) ?

[murugaratham]

Yup, here's a screenshot of the source

Here's the log's after publishing as SingleFile & PublishTrimmed

[skomis-mm]

@murugaratham just remove this line
var functionDependencyContext = DependencyContext.Load(typeof(Startup).Assembly);

[murugaratham]

Seems working fine and I feel dumb

[eLPe21]

Not sure if this is related, but when I build to single file for Centos7 ( the build is done on Mac )
I get extra files that I have to send over to make the application working:

The files are added to the publish folder as soon as I add Serilog.Settings.Configuration on my net50 project.

../out50/System.Native.a			
../out50/System.Native.so			
../out50/System.Security.Cryptography.Native.so

[nathanpovo]

Another workaround is to set IncludeAllContentForSelfExtract to true when publishing. Setting this property to true changes the .NET 5.0 system of single-file apps to be backward compatible with the .NET Core 3.x system (as described here).

I have tested this with version 3.2.0-dev-00264 of Serilog.Settings.Configuration and it works; version 3.1.0 will not work.

Some additional info on the workaround can be found here - dotnet/runtime#44511 (comment)
Related issue - dotnet/runtime#42265

[sungam3r]

Would be nice to mention it in the readme.