Publish on NuGet

[pardeike]

Publish on NuGet

[wasabii]

I got NuGet package support added. But the author will have to publish it.

I also picked the package name "Harmony". And it appears this package name is already taken.

@pardeike Any preference on what you might pick?

[antiufo]

If I have multiple projects are those signed with the same identity

That's how things are usually done, but even if you use different keys, it will still work.

What if, two users use two different signed Harmony versions because they build from source themselves

You can either:

• Add the .snk to the repository (that's what I personally do for my open source projects, and what I think most people do)
• Let users sign with a "fake key" (but I don't know much about this option)

Harmony was designed from the start with a multi-user perspective and can co-exist with other versions of itself

That won't change. If you are able to load different versions of the assembly now, it will still be possible after you add a strong name.

In order to set a strong name for your .csprojs, go to the project settings page in Visual Studio and create the .snk from there. Then you can reuse it in other csprojs.

Note that all the assemblies that a strong named assembly uses must also be strong named. (But assemblies that use your strong named assembly don't have to be strong named)

[pardeike]

I see. I upload it as soon as 1.1.1 is released.

[pardeike]

Now available as Lib.Harmony

[wasabii]

No ya don't. You just create an account, and upload a package.

[Kittyfisto]

Not sure if this should be a different issue, but I would also prefer it if the published version were strong name signed (not that I'm a fan of SNS, but my stuff is used in applications which use SNS).

[pardeike]

I’ll look into adding signing. Thanks.

[Hooch180]

Do you need any help with signing and publishing NuGet?

[pardeike]

I would like to do it but hadn't had the time to find a good article about signing. If I have multiple projects, are those signed with the same identity? What if, two users use two different signed Harmony versions because they build from source themselves? Lots of questions. Harmony was designed from the start with a multi-user perspective and can co-exist with other versions of itself. But signing (beside the basics) is new to me.

[pardeike]

Just checked: In order to publish on nuget you need a signing certificate that is produced by a microsoft known CA (Symantec etc). These cost money so I rather not want to go that way. Also, Microsoft states that self signed certificates are not accepted.

[antiufo]

@pardeike That's a different kind of signature, unrelated to .NET strong names.