Issue 119 in noda-time: Nuget assemblies not signed

[noda...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 119 by UncleTha...@gmail.com: Nuget assemblies not signed
http://code.google.com/p/noda-time/issues/detail?id=119

What steps will reproduce the problem?
1. Try compiling a project that is strongly named (has a key) after
importing the official Noda-Time Nuget (beta2)

What is the expected output? What do you see instead?
I expect a nice clean build with no errors, warnings or even messages
(cause I'm that anal).

I get:
"Assembly generation failed -- Referenced assembly 'NodaTime' does not have
a strong name"

Which creates a sad face :(

What version of the product are you using? On what operating system?
1.0.0-beta2 (Prerelease)

Please provide any additional information below.
This is easy to fix (in fact until you fix it I'll have to build the code
and publish my own NuGet to our internal repo which is a PITA) by going
into the Project properties and ticking 'sign the assembly'.

In .NET strongly named/signed assemblies (pretty much all production code
has to be strongly signed - particularly in future if you're doing anything
on Win 8) cannot reference non-signed assemblies - though the vice versa is
possible (as the .NET assemblies are strongly named and you can obviously
include them).

People forgetting to sign assemblies they push to NuGet is the bane of the
poor .NET developer :(

[noda...@googlecode.com]

Updates:
Status: Duplicate
Mergedinto: 35

Comment #1 on issue 119 by jonathan.skeet: Nuget assemblies not signed
http://code.google.com/p/noda-time/issues/detail?id=119

(No comment was entered for this change.)