-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
Strong naming #148
Comments
Sorry, i've not noticed during publish that it failed. I have 2 certs now, and the script just failed to choose only one. I'll rerelease, but it will be with new cert. The other one is not valid anymore. |
That's great, I'm yet not planning to dig into the code. I'm only using the build assembly via nuget. what are your planned release cycles? or do you have some nightly builds which I can pick up? I'm currently evaluating a way to do some export in Word and because of dependencies with other strong named assemblies OfficeIMO has to be strong named too otherwise they wont work together.
Kind regards,
Uwe
… On 1 Jul 2023, at 09:59, Przemysław Kłys ***@***.***> wrote:
Sorry, i've not noticed during publish that it failed. I have 2 certs now, and the script just failed to choose only one. I'll rerelease, but it will be with new cert. The other one is not valid anymore.
—
Reply to this email directly, view it on GitHub <#148 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADB3JXAVQSLSHQZTKANZ2LDXN7DFTANCNFSM6AAAAAAZ2RHKSY>.
You are receiving this because you authored the thread.
|
I don't have planned release cycles - just releasing when I feel like it. It's fairly automated process, just don't have much safeguards in place. I've now released new version, which is hopefully signed. |
unfortunately Strong Name shows still false.
… On 3 Jul 2023, at 09:38, Przemysław Kłys ***@***.***> wrote:
I don't have planned release cycles - just releasing when I feel like it. It's fairly automated process, just don't have much safeguards in place. I've now released new version, which is hopefully signed.
—
Reply to this email directly, view it on GitHub <#148 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADB3JXBQYENVUA3IXJEIB5LXOJSERANCNFSM6AAAAAAZ2RHKSY>.
You are receiving this because you authored the thread.
|
I see. Well that makes it a bit complicated: |
If possible I would appreciate if you can use strong naming for the resulting assembly. Great work.
The text was updated successfully, but these errors were encountered: