Skip to content

System.Memory and assembly version conflict #894

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

Closed
lukebakken opened this issue Jul 6, 2020 · 3 comments
Closed

System.Memory and assembly version conflict #894

lukebakken opened this issue Jul 6, 2020 · 3 comments
Assignees

Comments

@lukebakken
Copy link
Collaborator

In this rabbitmq-users message the user shows that there is an issue with System.Memory, and also reported the problem here.

It turns out they are using the RabbitMQ .NET client in an environment that has a different version of System.Memory.dll present. I believe this is the scenario that @bording pointed out in this comment.

At this point there's not much we can do but what should my guidance be in this scenario if it comes up again?

@stebet
Copy link
Contributor

stebet commented Jul 6, 2020

Binding Redirects in the web.config or app.config should take care of these:
https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/redirect-assembly-versions
and
https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/how-to-enable-and-disable-automatic-binding-redirection

@lukebakken
Copy link
Collaborator Author

Great, thank you.

michaelklishin added a commit to rabbitmq/rabbitmq-website that referenced this issue Jul 7, 2020
@michaelklishin
Copy link
Contributor

michaelklishin commented Jul 7, 2020

Added a short doc section

michaelklishin added a commit to rabbitmq/rabbitmq-website that referenced this issue Jul 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants