You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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..
The text was updated successfully, but these errors were encountered:
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?
On Tue, Oct 3, 2017 at 1:26 PM, Ken Dale ***@***.***> 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
<#9>?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA-So74gLmu2ggTHmo1UsA5RLicAcX-Bks5sonxzgaJpZM4PpnpW>
.
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..
The text was updated successfully, but these errors were encountered: