Hello.

Assembly redirections are normal when combining multiple NuGet packages. The tooling, however, should generate them automatically and correctly, so normally you may not even notice it.

It would be weird if it was not happening. If that is the case, it would be necessary to have the project that reproduces the issue for analysis here.

Not sure if this is your case, but be aware that

1) It is generally impossible to create a usable assembly out of a class library for general consumption (outside of your Visual Studio solution), if the class library references NuGet packages. What you have to build is a NuGet package again. This is because the information about admissible assembly versions needs to go with your assembly, and only NuGet package has this information - not the assembly in itself.

2) If you want to do something like dynamic library loading (package model) with libraries built with NuGet packages, there is a ton of extra considerations and work to be done in the code in order to get the assembly redirections also done dynamically.

Regards
 

I want to use the EasyUAClient inside my class library project, when I create an instance of the object as follows
 _uaClient = new EasyUAClient();
I get an exception stating that it could not load System.Memory due to a version mismatch. When I add an assembly redirect it works.

why is this happening..??