Add optional Strong-named NuGet packages
Add optional Strong-named Server and Client NuGet packages so they can be added in the GAC and used inside Enterprise products requiring signed dlls.
Could you add the swagger package to the list ?
Herdy Handoko commented
This will be especially useful for SharePoint :)
Yep I'm thinking about only having 2 separate NuGet packages with signed versions, e.g:
Which will be separate packages that contain a collection for dlls you would use on the Client / or Server with ServiceStack. The one place which might have to be signed is the impl-free 'ServiceStack.Interfaces' so signed clients can talk to unsigned Servers (when DTO dll is signed/shared), but we should be able to mitigate any pain by keeping it always at v18.104.22.168 so updates aren't breaking changes, it also helps that SS.Interfaces is impl-free and very rarely updated.
Chris Mcvittie commented
As long as this is strictly opt-in!