Posted 26 July 2023, 8:14 am EST
- Updated 27 July 2023, 2:43 am EST
Hi Nitin,
Thank you for your prompt reply.
We are using GrapeCity in an ASP .Net Core Web App (.Net 7). I have added the assembly redirects to my Web.config as follows:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.web>
<compilation debug="true" />
<httpRuntime />
</system.web>
<appSettings>
</appSettings>
<runtime>
<assemblyBinding>
<dependentAssembly>
<assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-7.0.0.0" newVersion="7.0.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-7.0.0.0" newVersion="7.0.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Buffers" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-7.0.0.0" newVersion="7.0.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Numerics.Vectors" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-7.0.0.0" newVersion="7.0.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
Which still does not work.
Since we are using .Net 7, Mitchell’s solution is not entirely necessary. I am under the impression that assembly loading in .Net Core would fix this issue:
“.NET Core’s simplified assembly loading means it just works.” - https://nickcraver.com/blog/2020/02/11/binding-redirects/
Additionally, I have also tried adding:
<AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
Which still does not work.
Please do let me know if this issue is also persistent in newer versions of .Net and if so, is there a solution?
Sincerely,
Brett