Closed igorskys closed 7 years ago
Thanks for the report. It sounds like the NuGet package install process may not have created the required assembly binding redirects; do the instructions at: https://weblog.west-wind.com/posts/2014/Nov/29/Updating-Assembly-Redirects-with-NuGet help?
Thanks for the reply. It helped. I was asked to downgrade Serilog to 2.3.0 and for somereason SerilogWeb.Classic returned be to the same issue. The hint doesn't help.
Thanks for the follow-up, good to hear it's working.
Actually it is not working in my specific case. We have sharepoint application. This application doesn't use app.config, it uses custom config path. I added assembly redirect to my custom config, but it didn't help.
Here is failure log.
Thank you!
Thanks for the update.
Serilog 2 has been out for a long time; I'd be happy if we updated this package to depend directly on Serilog 2.5, and bumped its major version.
Is anyone interested in PRing this? Cheers!
It would be nice to have 👍
Closed via #42.
I'm not sure, but I believe there are still traces of older versions of Serilog :-/
I see
<dependencies>
<dependency id="Serilog" version="1.5.7" />
</dependencies>
in file https://github.com/serilog-web/classic/blob/master/src/SerilogWeb.Classic/SerilogWeb.Classic.nuspec
And the last published NuGet package declares Serilog v1.5.7+ as a dependency : https://www.nuget.org/packages/SerilogWeb.Classic/3.0.19
I believe there should be no <dependencies>
node in the .nuspec
file, as nuget pack projectPath
will already generate it for you, looking at the project's packages.config
file.
Hello,
I updated my projects with latest serilog. Cleaned packages and after that I started getting Serilog 1.5.0.0 dependency not found exception. Is there workaround for latest version of Serilog?
Thanks!