1
Vote

Cannot recompile source and generate with same public key token as binaries

description

When recompiling the source code I cannot generate dlls with the same public key token as the dlls from the binaries. This causes a problem when I am trying to roll my own fix on a silverlight app for which I don't have the source code to other dlls that reference the silverlight toolkit.

A potential workaround would be to decompile every 3rd party assembly with ildasm and manually update the public key token but this is incredibly tedious and not guaranteed to work.

I can understand the security reasoning behind this but it makes my scenario impossible/very difficult workaround? Is there any chance that we can get the same strong name key that is used to sign the binaries so that we can compile our own fixes/changes?

comments

BachratyGergely wrote Aug 27, 2014 at 1:01 PM

That signing key is used for lots of stuff besides Silverlight including Windows system components and .net framework library code. The only chance you can get your updated toolkit with the same snk is to convince Microsoft to compile it for you. Reassembling 3rd party components is easier.

bperkins24 wrote Aug 27, 2014 at 2:23 PM

Well, that wasn't entirely unexpected and it makes sense from a security perspective but it isn't truly open source...Unfortunately I will have to live with the shortcomings of this toolkit and use the source code to implement workarounds in my code that references the toolkit. There are too many 3rd party dlls to decompile, modify and recompile and I'm not even sure it would work. Taking updates from the 3rd party would also become a hassle.

Thank you for your response.