- Mark as New
- Subscribe
- Mute
- Permalink
- Email to a Friend
- Report Inappropriate Content
Jul 23, 2021
10:42 AM
I have been using FlexNet Embedded 2018 R2 DotNet client and have in a wrapper library that I have been using for a while in couple of our applications. One of our applications that uses it, I updated to .NET 5. I now get the following error when running the application:
Exception: Strong name validation for the assembly 'FlxLicensingClient' failed. Assembly not strong-named or is tampered. Verification via API failed.
I have verified this is still the case with a simple console application.
Is this a known issue? Do you have any workaround suggestions? Should I be using the DotNet Core client instead?
- Tags:
- .Net 5
- Strong Name
1 Solution
- Mark as New
- Subscribe
- Mute
- Permalink
- Email to a Friend
- Report Inappropriate Content
Aug 04, 2021
10:05 AM
2 Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Email to a Friend
- Report Inappropriate Content
Aug 04, 2021
09:21 AM
Any word on this, has anyone been able to test and verify?
- Mark as New
- Subscribe
- Mute
- Permalink
- Email to a Friend
- Report Inappropriate Content
Aug 04, 2021
10:05 AM
