Please strong name key the Silverlight project

[aligneddev]

I just got JSON.Net for Silverlight from NuGet (version 4.5.5.14908), but I can't build because the dll isn't signed with a strong name. The net40 is (according to the command line sn.exe and http://james.newtonking.com/archive/2012/04/04/json-net-strong-naming-and-assembly-version-numbers.aspx).

I'll download the source and re-sign it myself for now.

Thanks,

Kevin

[davidfowl]

Silverlight doesn't support binding redirects, this makes signing a horrible idea since you can't use another library unless it works with the EXACT same version of Newtonsoft.Json.

This might be less of an issue since the versioning strategy has changed but i'll let James chime in.

[aligneddev]

Interesting. I didn't think about other library dependencies on Newtonsoft.Json or the difficulties that might cause. I signed my Silverlight assemblies to work with Assembly Caching according Tim Heuer's post: http://timheuer.com/blog/archive/2009/07/13/silverlight-3-cached-assembly-feature.aspx.

Thanks,
Kevin

[JamesNK]

The zip download from CodePlex contains a strong named build.