-
-
Notifications
You must be signed in to change notification settings - Fork 95
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 name signing of Buildalyzer? #51
Comments
I've been thinking about this and I've decided not to strong name Buildalyzer. Here's the thinking:
Sorry - that's probably not what you wanted to hear. I'm still super-interested in helping you get Buildalyzer working in SpecFlow so let me know if there's anything else I can do to help! |
@daveaglick I understand your decision, if SpecFlow wasn't already strong name signed, I wouldn't add it now. Thanks for your offer to help, but we recognized we can get everything we need on information with our MSBuild task and so we have no need anymore to read the project files. |
Hi
I am one of the maintainer of SpecFlow (https://github.com/techtalk/SpecFlow) and we want to use Buildalyzer to add .NET Standard/Core 2.0 to SpecFlow.
Our project is used by a lot of enterprises and they somehow like strong name signing. So we are signing our stuff also with a strong name.
Buildalyzer is currently not strong named signed. So that we can use it, we would need Buildalayzer strong named signed.
Would this be possible? If we provide a PR for that, would it be merged?
The text was updated successfully, but these errors were encountered: