Closed madisonleavo closed 5 years ago
Hey, the ci build “should” be automatically adding all the version numbers. I’ll have to check this wasn’t broken when i changed to using the tag version.
The signing (version number) looks good to me:
strange ...
@madisonleavo assembly version 1.0.0.0 is OK for this library IMO
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hello! I'm using your lib integrated with COM interop, registering in GAC, where all dependencies have to have StrongName (which i notice you just implemented signing--thanks!). But I'm having issue with the version of the assembly. In NuGET its version
6.1.0
but when NLog is trying to load, its looking forNLog.Targets.ElasticSearch, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3eb62cd298662c6a. File version: 1.0.0.0. Product version: 1.0.0
, and in my case, fails to find it. And due to integration, I can't really implement the Assembly redirects.There is a workaround as the error output suggests--I added the assembly to
..\SysWOW64
and it works.But to fix, and I may be incorrect as I'm still learning, I think all that needs to be done is add
<Version>6.1.0</Version>
in section: https://github.com/markmcdowell/NLog.Targets.ElasticSearch/blob/0318815b08e6ac25c3bc29152aa7d9fb0542633c/src/NLog.Targets.ElasticSearch/NLog.Targets.ElasticSearch.csproj#L14[Edit: backticks, not single quotes]