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

Strong name #2

Open
DanAvni opened this issue Jun 27, 2017 · 3 comments
Open

Strong name #2

DanAvni opened this issue Jun 27, 2017 · 3 comments

Comments

@DanAvni
Copy link

DanAvni commented Jun 27, 2017

Hi,

Could you please add strong name to the assemblies?

@Yortw
Copy link
Owner

Yortw commented Jun 27, 2017

Hi,

I'm generally against strong naming but might be convinced to make a separate package that contains a strong named version. Why do you need this?

Have you considered using one the automatic signing tools (such as https://www.nuget.org/packages/Brutal.Dev.StrongNameSigner/) to sign packages yourself ?

@DanAvni
Copy link
Author

DanAvni commented Jun 27, 2017

Hi,

I wanted to use it in my project that is strongly names and as such cannot use assemblies without strong names. As of now and because I had a tight schedule I created my own implementation of a pool that will be replaced with a nuget at some point.

So no rush and feel free to decline if you think it should not be done

Thanks

@Yortw
Copy link
Owner

Yortw commented Jun 29, 2017

Hi,

Sorry, I was wondering why your project is strong-named? Is it using a click-once installer? Are assemblies loaded inside Sql Server or another host? Trying to determine if there is a real use case or if, as many other similar requests, this is a mistaken belief that strong naming adds 'security'.

Thanks.

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

No branches or pull requests

2 participants