Assembly does not have a strong name about jwt HOT 11 CLOSED

Microsoft are no longer Strong Naming assemblies in ASP.NET 5. Their guidance has changed regarding strong naming.
http://stackoverflow.com/questions/28352756/microsoft-aspnet-http-does-not-have-a-strong-name

from jwt.

Oh wow, that I didn't know! I wonder if that means that you'll be able to
GAC things that aren't signed in v.Next. Anyway, we were able to work
around the limitation. We now ilmerge the binaries we need into one
assembly, and then sign that. Thanks for getting back to me!

On Tue, Mar 10, 2015 at 7:56 PM, Darrel [email protected] wrote:

Microsoft are no longer Strong Naming assemblies in ASP.NET 5. Their
guidance has changed regarding strong naming.

http://stackoverflow.com/questions/28352756/microsoft-aspnet-http-does-not-have-a-strong-name

—
Reply to this email directly or view it on GitHub
#14 (comment).

from jwt.

For ASP.NET Core CLR there is no more GAC, for the full desktop CLR there is a GAC and I recall the signing rules are different, but I don't know the details off hand.

from jwt.

Thanks for chiming in, @darrelmiller. I'm closing this out for now. If anybody's blocked by this, feel free to holler and we can revisit.

from jwt.

I am using an assembly https://github.com/salesforce-marketingcloud/FuelSDK-CSharp that's dependent on JWT. If the assembly is not signed I am not able to deploy the dll to GAC. The FuelSDK is also not signed and the team has agreed to release it out next week. The StackOverflow post mentioned above has been updated and the assemblies are signed in ASP.NET 5 now. Ref: salesforce-marketingcloud/FuelSDK-CSharp#70 Please reconsider opening this issue. I can download the code and recompile but I have to download the others using this and compile that too. If you guys sign in I will just rely on the NuGet packages and will be easy to maintain.

from jwt.

hi, was Jwt.Net ever signed? No, to my knowledge. And I don't see FuelSDK-CSharpSDK depends on Jwt.Net.

from jwt.

from jwt.

Please submit a PR to sign it and bump the version to 6.0.0-beta1.

from jwt.

@balajikandasamy ping. Please contribute if you'd like to see this happen.

from jwt.

from jwt.

The StackOverflow post mentioned above has been updated and the assemblies are signed in ASP.NET 5. I am submitting a pull request to provide a strong name for all assemblies.

from jwt.