-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assembly signing #11
Comments
Hi, Is there any update on whether this could be supported? I ask mainly because I have released my framework but omitted cron support temporarily until it's determined whether a signed version will become available. If it won't be possible I'll look into alternative libraries. Thanks |
I need to have a signed version as well. |
I second that, would like to see progress on getting a signed version as they is blocking other projects from implementing signing hence reduces audience. |
FWIW, you can always fork and sign it yourselves and use a github action cron to keep it up to date with upstream |
That only works if you are directly taking the dependency on Cronos. If it is being brought in by another package such as Elsa you would also need to be maintaining a fork of Elsa etc hence better if it is provided by the base library.
|
Hi there,
I wanted to know whether there was the possibility of having a signed version of the assembly distributed to NuGet? I was thinking of using this framework as a dependency of one of my own (WIP) frameworks, but unfortunately mine is signed and won't build as this package doesn't have a strong name.
Thanks
The text was updated successfully, but these errors were encountered: