NetMQ Version: 4.0.0.175-pre
Operating System: Windows 10
.NET Version: 4.6.1
Expected behaviour
AsyncIO dependency has proper versioning (0.1.40)
Actual behaviour
AsyncIO dependency has wrong versioning (0.0.0).
This dummy version is rejected by our strict deployment system.
This might be fixed via binding redirects (to a newer AsyncIO version) if we have control over which application we deploy to.
However, our software is distributed as libraries (a bunch of dlls), so this is out of our control.
Our current workaround is to use NetMQ 4.0.0.5-pre, an outdated version but it has proper versioned AsyncIO assemblies.
Steps to reproduce the behaviour
Install any NetMQ Nuget package from 4.0.0.83-pre to 4.0.0.175-pre
Is this possible to publish a new NuGet package version with another AsyncIO version that has proper assembly versioning? Thank you.
Environment
Expected behaviour
AsyncIO dependency has proper versioning (0.1.40)
Actual behaviour
AsyncIO dependency has wrong versioning (0.0.0). This dummy version is rejected by our strict deployment system.
This might be fixed via binding redirects (to a newer AsyncIO version) if we have control over which application we deploy to. However, our software is distributed as libraries (a bunch of dlls), so this is out of our control.
Our current workaround is to use NetMQ 4.0.0.5-pre, an outdated version but it has proper versioned AsyncIO assemblies.
Steps to reproduce the behaviour
Install any NetMQ Nuget package from 4.0.0.83-pre to 4.0.0.175-pre
Is this possible to publish a new NuGet package version with another AsyncIO version that has proper assembly versioning? Thank you.