Strongly signed version of Machine.Specifications

[ivanz]

There used to be a strongly signed version on Nuget and still is, but the current build pipeline doesn't create nor publish a "-Signed" package.

Download numbers of the Signed packages are quite low.

[lwuckel]

Where can I find the "-Signed" package v0.11 ?
Or how can I build it for myself?

Regards, Lars

[JohannesHoppe]

Support for strong-name signing was dropped, back then in early 2014.
see #190

[BrunoJuchli]

@JohannesHoppe actually according to #190 that's not the Case.
In short:

Daniel Marbach asked whether there was a reason not to drop it - a reason why there should be a signed version, and it has been found:

(@ivanz this might be of interest to you, too:)

It's true when you have a signed assembly with an InternalsVisibleTo attribute to a specification assembly the specification assembly needs to be strong named too. I'm closing this issue.

NameOfTheDragon later found a specific workaround for his use-case - not signing non-release builds and hence testing non-release builds.

However, Daniel never said that signed-builds will be removed.

I personally have never used the signed version of machine.specifications - because i've never produced signed assemblies. So I'm not complaining that there's no signed version, just trying to set the record straight.