7

Closed

NuGet package DLLs are not strong signed

description

Hi
I've used your NuGet package to add a reference to your extension, but your DLLs are not signed.
So my project fails to build, as it's signed...
As a workaround I have to download the source and add my key to your DLLs manually.

Please update NuGet package with strong named DLLs.

Thanx and have a nice day,
Paolo
Closed Oct 3 at 10:22 AM by SeriousM

comments

SeriousM wrote Oct 19, 2012 at 8:30 PM

Hi paolo,

thanks for using our extension.
there was an issue like yours already:
http://wpflocalizeextension.codeplex.com/workitem/9260

in short: we wont signing it.

thanks, bernhard

** Closed by SeriousM 10/19/2012 12:30PM

nexbit wrote Oct 19, 2012 at 9:47 PM

Hi Bernhard,
the project is yours, and all the decisions is up to you and your contributors, obviously.

But please consider to provide in the future a signed package for the community to use, aligned with the latest public release. It has not to be a NuGet package, maybe only a zip with signed dlls.
If I was in Nuget devs, I'd have proposed not to accept unsigned assemblies at all in the public gallery...

thanks for your attention,
Paolo

SeriousM wrote Oct 23, 2012 at 12:32 PM

we plan to create automatic release publishings on codeplex including signed packages.

Phyxion wrote Feb 3 at 2:16 PM

"we plan to create automatic release publishings on codeplex including signed packages."

Can we get this going the next version, please?

MrCircuit wrote Feb 10 at 9:34 PM

YES! .... :-)

Phyxion wrote Jun 24 at 6:58 PM

Any updates on this? It's rather frustating now in VS2013 as it sometimes seems to revert back to the unsigned libraries from nuget (I replace the existing dlls in-place).