Skip to content
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

Generate strongly named assemblies by default #52

Closed
7 of 9 tasks
jariq opened this issue Jun 10, 2017 · 0 comments
Closed
7 of 9 tasks

Generate strongly named assemblies by default #52

jariq opened this issue Jun 10, 2017 · 0 comments
Assignees

Comments

@jariq
Copy link
Member

jariq commented Jun 10, 2017

As I currently see it there are three options when it comes to strong naming open source library:

OPTION 1: Generate single unsigned assembly/package:

  • works in projects that do not require strong naming
  • works in projects that require strong naming
  • easy to maintain

OPTION 2: Generate single signed assembly/package:

  • works in projects that do not require strong naming
  • works in projects that require strong naming
  • easy to maintain (with .snk publicly available in the repository)

OPTION 3: Generate two separate assemblies/packages, one signed and one unsigned:

  • works in projects that do not require strong naming
  • works in projects that require strong naming
  • easy to maintain (doubles the work and may cause issues in projects with complex dependencies)

Historically Pkcs11Interop up to the version 3.3.0 was using OPTION 1 but then in #41 I decided to switch to OPTION 3 because I considered that option to be the least harmful for existing users in that time. Now that we are approaching next major release I am going to switch to OPTION 2 on all platforms that support strong naming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant