Strong name error with EntityFrameworkCoreMock.Moq 2.0.0.107
See original GitHub issueHi, I have all the projects in my solution signed with a SNK, I installed the nuget version 2.0.0.107 so i can mock an exception during SavingChanges, but i got this error during build:
Referenced assembly 'EntityFrameworkCoreMock.Moq, Version=2.0.0.107, Culture=neutral, PublicKeyToken=null' does not have a strong name.
Do you have a nuget version with the packages signed?
Thanks a lot.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5
Top Results From Across the Web
Strong name error with EntityFrameworkCoreMock.Moq 2.0 ...
Hi, I have all the projects in my solution signed with a SNK, I installed the nuget version 2.0.0.107 so i can mock...
Read more >How to fix "Referenced assembly does not have a strong ...
If you don't find the .snk-file: Open the project properties (of the project using the project with the "strong name" error), tab Signing....
Read more >EntityFrameworkCoreMock.Moq 2.4.0
Easy Mock wrapper for mocking EntityFrameworkCore 5 (EFCore5) DbContext and DbSet using Moq.
Read more >How to: Disable the strong-name bypass feature | ...
Disable the strong-name bypass feature for all applications On 32-bit computers, in the system registry, create a DWORD entry with a value of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I will create a PR then.
Thanks for your time
@JuanZamudioGBM Finally had some time to get into strong naming and change the AppVeyor pipeline to GitHub actions.
As of version 2.1.0, this library should be signed.