1

Closed

Strong-name signed assembly

description

This assembly cannot be consumed from other assembles that are strong-name signed.
Strong-name signing is easy to set up, and the key can be checked in so that anyone can still build the project.
Closed Aug 11, 2013 at 3:35 PM by alazan

comments

alazan wrote Aug 7, 2013 at 10:15 AM

Good feedback, I'll support this asap.

alazan wrote Aug 8, 2013 at 8:21 PM

I juste updated the nuget package. The WinRT (windows store app) assembly has now a strong name.

alazan wrote Aug 8, 2013 at 8:22 PM

** Closed by alazan 08/08/2013 1:22PM

AArnott wrote Aug 9, 2013 at 5:04 AM

Fantastic. thanks.

AArnott wrote Aug 10, 2013 at 2:52 PM

Actually the 0.1.1 NuGet package still doesn't contain a strongly named assembly. :(

AArnott wrote Aug 10, 2013 at 3:13 PM

Ah, the issue is probably because I need WP8BouncyCastle strong-name signed, but it looks like you only added a strong-name signing key to WinRTBouncyCastle.

VS2012 doesn't expose a way to add a strong-name key to a WP8 project in the UI, but it's supported in build authoring. I'll send a pull request that fixes the issue.

And hopefully you don't mind that I use the non-password protected .snk file format instead, so we can rebuild what your open source project has.

alazan wrote Aug 11, 2013 at 3:28 PM

Hi,

I just accepted and merged your pull request.
The nuget package is also updated.

Thanks,
Cyprien