Strong name?


I think the NuGet package objectflow.core.dll assembly should have a strong name. Some of us require strong names (I'm doing COM interop, for example, and have to strongly name my assemblies). I have a workaround, but it's very hackish.


djnz_gea wrote Apr 7, 2014 at 7:57 AM

I agree that ideally the framework would be code signed. The reason it isn't is simply I haven't got round to purchasing a code signing certificate or change the build to sign the files.

Time and money I'm afraid.

bslatner wrote Apr 7, 2014 at 4:21 PM

I understand. I'm not 100% sure how other projects manage this. I just use a .snk generated by the sn.exe utility and sign everything with that. But I've never had to deal with a .snk file in a public repository before and I'm not sure what all the ramifications are.