AnsweredAssumed Answered

ArcGIS Toolkit in NuGet package is unsigned

Question asked by martinbrz on Dec 1, 2014

We are using ArcGIS Toolkit from a NuGet package.
It's working ok as long as we only place a ScaleLine control in xaml.
But as soon as we reference it in code behind, we get an "assembly not signed" error.

 

Our solution uses strong names throughout and therefore ArcGIS Toolkit should also be using one.
We have tried using ildasm and signing the Toolkit dll with our own key using ilasm.
This did not do the trick because we then get a runtime error:
"The located assembly's manifest definition does not match the assembly reference".

So there is still a reference to "Esri.ArcGISRuntime.Toolkit, PublicKeyToken=null"
somewhere (a manifest inside dll?)

 

The ground problem is that the NuGet package does not contain a signed assembly.
Will it do that in the future and is there anything we can do in the mean time?

(using a stand-alone dll instead of NuGet is not an option for many reasons)

 

(Esri.ArcGISRuntime.Toolkit ver 10.2.4.0)

Outcomes