Skip to content
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

NetMQ build and AsyncIO #472

Closed
gtemgoua opened this issue Feb 5, 2016 · 5 comments
Closed

NetMQ build and AsyncIO #472

gtemgoua opened this issue Feb 5, 2016 · 5 comments
Labels

Comments

@gtemgoua
Copy link

gtemgoua commented Feb 5, 2016

Not sure if this has been raised before but when you pick up the latest stable release of NetMQ 3.3.2.2, it does come with AsyncIO.dll ver 1.18 but then somthing really weird has to happen before everything works on VS 2012 projects
this snippet can be auto generated when nuget installs the package in your app.config file or you can add it yourself:
<runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="AsyncIO" publicKeyToken="44a94435bd6f33f8" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-0.1.18.0" newVersion="0.1.18.0" /> </dependentAssembly> </assemblyBinding> </runtime>

I clearly do not understand the necessity of that redirect, but that is not where it gets juicy. Thing is my build server is not actually packaging all that config in the final .msi - build package when executed. therefore when i deploy this, i have to edit all the config files with that snippet above.
Thoughts ?

@Sn3b
Copy link

Sn3b commented Feb 6, 2016

Indeed, I've just updated too and my winforms form now needs to have this piece of xml in the config, my problem is that it's meant to be a config file free app :/
If I just delete the config file it complains it cannot find the assembly version 0.1.17.0... :/

System.IO.FileLoadException : Could not load file or assembly 'AsyncIO, Version=0.1.17.0, Culture=neutral, PublicKeyToken=44a94435bd6f33f8' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

@somdoron
Copy link
Member

somdoron commented Feb 7, 2016

We will fix this in next stable release.

@rvlieshout
Copy link

rvlieshout commented Jan 2, 2018

I too seem to be having this issue, it looks for AsyncIO v0.1.25.0 (!?!) however I installed 0.1.40.0 (the nuget package requires >= 0.1.26.0). Somehow all is messed up and my application fails with the message:

Could not load file or assembly 'AsyncIO, Version=0.1.25.0, Culture=neutral, PublicKeyToken=44a94435bd6f33f8' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Last stable release is 4.0.0.1? (22 Jan. 2017)

Edit:

.net 4.6.1

@SMishin
Copy link

SMishin commented Jul 18, 2018

Hi @rvlieshout
See here: somdoron/AsyncIO#21

@stale
Copy link

stale bot commented May 14, 2020

This issue has been automatically marked as stale because it has not had activity for 365 days. It will be closed if no further activity occurs within 56 days. Thank you for your contributions.

@stale stale bot added the stale label May 14, 2020
@stale stale bot closed this as completed Jul 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants