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

Feature: Sign 'WireMock.Net' #160

Closed
icraftsoftware opened this issue Jun 29, 2018 · 4 comments
Closed

Feature: Sign 'WireMock.Net' #160

icraftsoftware opened this issue Jun 29, 2018 · 4 comments
Assignees
Labels

Comments

@icraftsoftware
Copy link

Hello,

I have no choice, I am working on BizTalk Server integration solutions, and as you know, BTS requires the assemblies to be GACed and a fortiori signed. Because all my projects are signed, I can't use WireMock. Please, provide a signed version of your assembly; on nuget.org as well. It would help all of us that must use signed assemblies, and would not bother anyone else.

Thank you

François

@StefH StefH changed the title Referenced assembly 'WireMock.Net' does not have a strong name Feature: Sign 'WireMock.Net' Jun 29, 2018
@StefH StefH self-assigned this Jun 29, 2018
@StefH StefH added the feature label Jun 29, 2018
@StefH
Copy link
Collaborator

StefH commented Jun 30, 2018

At this moment WireMock.Net cannot be strong name signed because RestEase is not yet signed.

Maybe you can use this project https://github.com/dsplaisted/strongnamer ?

@icraftsoftware
Copy link
Author

Never heard of StrongNamer, but unfortunately it did not work. What did the trick was the following Stack Overflow solution, see the comment I made (incl. 4 other comments that show the command lines to use).

I also had to make sure that no two different versions of a given NuGet package were used; this was the case for Newtonsoft.Json.

The main downside is that I cannot blindly restore NuGet packages to build my solution anymore.

Could not you just provide an equivalent to what I've done on NuGet?

@StefH
Copy link
Collaborator

StefH commented Jun 30, 2018

I cannot create a signed version yet because restease does not support strong naming.

See canton7/RestEase#50

@StefH
Copy link
Collaborator

StefH commented May 16, 2019

#267

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

No branches or pull requests

2 participants