Strong name signing WatsonWebserver

[bcalco]

I want to use Watson in and environment that requires strongly named assemblies but it seems that the NuGet packaged version does not have a public key. Is my only recourse to compile and sign it myself?

[jchristn]

Hi @bcalco at this point I don't have a financial incentive to do it (as far as I can tell, code signing certs aren't free), so it would be best for you to sign. Cheers, Joel

[bcalco]

I was referring to simply strong-naming with an SNK file. That's pretty easy and costs nothing.

I am going to code-sign my binaries and the installer with an actual EV cert. I was hoping to avoid extra work of downloading, compiling and using Watson directly, when everything otherwise works just using Nuget to keep it current.

[jchristn]

Applying strong naming to the subordinate packages, then will do Watson, give me a few mins

[jchristn]

Hi @bcalco I just uploaded v4.2.2.6, can you let me know if this does the trick? https://www.nuget.org/packages/Watson/4.2.2.6

[bcalco]

Will check it out and let you know. It may or may get rid of problem I was seeing trying to load it (may have a different root cause), but it should minimally get rid of the missing strong name warning. :)

[bcalco]

OK it gets rid of the warning, and it does seem I'm able to load the assembly in my app and call into it. Thanks!

[jchristn]

Thanks for the pointers and the nudge. Not sure how I'm going to navigate doing this on the rest of my packages lol :)