search

ritterim / automation-storage-emulator

MIT License
11 stars 3 forks source link

Strong name assemblies #14

Open niemyjski opened 6 years ago

niemyjski commented 6 years ago

Is there any chance you could strong name the project. We have strong naming in our project because others need it. The .net team recommends just strong naming it even if the key is in your github repo..

kendaleiv commented 6 years ago

We would accept a PR that implements this, provided the strong named package does not impact the existing package and doesn't complicate the repository too much.

Would this cause any issues with implementing .NET Standard per #9?

niemyjski commented 6 years ago

No it shouldn't cause any issues.

Thanks -Blake Niemyjski

On Tue, Oct 3, 2017 at 1:26 PM, Ken Dale notifications@github.com wrote:

We would accept a PR that implements this, provided the strong named package does not impact the existing package.

Would this cause any issues with implementing .NET Standard per #9 https://github.com/ritterim/automation-storage-emulator/issues/9?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ritterim/automation-storage-emulator/issues/14#issuecomment-333935387, or mute the thread https://github.com/notifications/unsubscribe-auth/AA-So74gLmu2ggTHmo1UsA5RLicAcX-Bks5sonxzgaJpZM4PpnpW .