-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assembly for released version 0.1.40 is marked as 0.0.0 #21
Comments
Indeed, and causes also strange redirection bindings... |
I ran into the same issue too. When upgrading from 1.25.0 to 1.40.0, it automatically added an assembly binding redirect into app.config:
When I ran the project, it threw an exception:
To fix ,I had to manually adjust the binding redirect, so all versions are redirected to version 0.0.0.0:
|
Currently, I cannot upgrade NetMQ.ReactiveExtensions to use AsyncIO v1.40. The problem is that the default assembly language binding redirect that Visual Studio adds to app.config is:
... which has to be hand-edited to this, or else it will throw an exception on startup:
|
@sharpe5 can you send a pull request? |
Sure, happy to help! What new version do you want - 0.1.40.1 or 0.1.42.0?
The former is technically correct, and the latter will hopefully encourage
people to upgrade.
…On 14 Dec 2017 8:12 a.m., "Doron Somech" ***@***.***> wrote:
@sharpe5 <https://github.com/sharpe5> can you send a pull request?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABOypGhV2TKsJ1eTJviRBZoQRC96wGsuks5tANgwgaJpZM4Qojgq>
.
|
Created a pull request, please let me know if anything needs changing. This was a really good exercise for me. I will copy the structure of your project when I upgrade NetMQ.ReactiveExtensions to the newer .csproj file format. Thank you again for your excellent work! |
Any update on this work. I'm running into the same problem. |
Pull request for issue #21: Assembly for released version 0.1.40 is marked as 0.0.0
Same problem today, May 2018. Although github appears to be at version 0.1.42, nuget delivers 0.1.40 and it's internal version number is still 0.0.0.0. |
Deploying the latest version 0.1.42.0 to NuGet would fix the issue, as this issue was fixed in pull request #22. |
Hi Doron,
It seems that the released version on nuget has no version set. This is then causing a compilation warning with NetMQ.
The text was updated successfully, but these errors were encountered: