-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
PushSharp 3 is not strong signed. #607
Comments
I'd really prefer not to sign the assemblies, is there a particular reason you must use signed assemblies? If I do decide to sign them I'll most likely include the .snk file and password for it right in the source project so folks don't have issues compiling from source. |
Also, you can also pull the source, compile, and sign it yourself if you're really desperate :) |
Furthermore, there's a pretty good explanation of why strong naming assemblies is probably not necessary: octokit/octokit.net#405 (comment) |
Hi !
|
You can also use ILRepack or https://github.com/brutaldev/StrongNameSigner to accomplish signing. Can you elaborate on 2? I'm not familiar with what 'DLL to DLL' means exactly. |
as I know, I cant use non-signed DLL via other DLL on web project. I see a strange errors... |
Exception for example:
|
something strange. I removed NuGet package and signed DLL.s test application with nuget original - works.
|
Not sure why strong namer isn't working for you, but I'm going to confirm I do not intend to sign PushSharp 3. |
I was forced to upgrade as PushSharp 2 do not recognize my new keys.
Trying to upgrade from 2.x to 3 on a test Windows Application - works.
Trying to use it on the main app - can't, becase of the DLLs is not strong typed.
trying to manually sign the keys - failed, as one DLL depend other one and NuGet is overwriting these files.
What I can do? It can be fixed on the main branch ?
thanks
The text was updated successfully, but these errors were encountered: