could not load assembly esri.arcgisruntime.toolkit.wpf in release mode

[Fl0wC0de]

WPF could not load assembly esri.arcgisruntime.toolkit.wpf in release mode but it does work in debug mode.
esri.arcgisruntime.toolkit.wpf version 200.6.0.0 is set as reference in my project with Copy Local set to True.

[dotMorten]

esri.arcgisruntime.toolkit.wpf version 200.6.0.0 is set as reference in my project with Copy Local set to True.

How are you referencing it in your project? I assume you're using a PackageReference? Could you share a project that demonstrates the problem?

[Fl0wC0de]

The problem is that the toolkit does not have a strong name key

[Fl0wC0de]

Is there a way to get a version with a strong name key?

[dotMorten]

Strong name (or lack there of) shouldn't cause any issues. I can barely remember when we stopped strong naming assemblies, since it generally caused more problems than they helped (the assemblies are digitally signed though). How is your project set up? I'm confused about the "copy local" setting you refer to, since it doesn't apply to the nuget package that the toolkit is distributed in.
Could you also share the exact callstack and full error message you're getting?

[Fl0wC0de]

So basically, I have a solution with multiple projects, All the projects are set to be strong named. I have no problem with the toolkit when I run in debug mode but when I run in release mode or deploy the application on a server then I get the error as seen above. The error shows because I am trying to use the legend functionality. If I do not use that functionality then all is good. For whatever reason, it has no issues with the ARcGISRuntime amd ArcGISRuntime.WPF but only with the Toolkit.WPF. The only difference that I can see is that out of the 3, the toolkit.WPF does not have a strong named key. The callstack is not useful because of the error above and it jumps then to the loaded event and the class is bypassing instantiation of necessary properties.
Once again, this is happening only when running the application as Release mode in Visual studio or when deployed to a server. It works fine in debug mode.

[dotMorten]

None of the ArcGIS Runtime assemblies have strong keys.
@Fl0wC0de Could you share a small sample project that reproduces the issue? We verify the releases in release builds and didn't hit this.