licence.ValidateSettingsFile Failed
I'm evaluating your product to protect our application developed with .NET Framework 4.8.
When LicenseValidator class runs ValidateSettingsFile check if fails with the following error message :
"Could not load type 'System.Security.AccessControl.CryptoKeyAccessRule' from assembly 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'."
Is it missing a assembly refference to mscorlib or is something wrong with my SettingsFile?
Could you help me please?
-
Official comment
Hi jordi,
We'll need a bit more information to diagnose this.
Are you using the QLM NuGet package in your application or did you add an explicit reference to QlmLicenseLib.dll?
Regards,
John
Comment actions -
Hi jordi,
You said "When LicenseValidator class runs ValidateSettingsFile check if fails with the following error message"
Can you please provide more context for the error?
Is your application a desktop application?
Does it compile and build properly?
Does the error occur at runtime?
When you look at the references in your application, are there any warning signs?
Please send me a screenshot of your project's settings in Visual Studio showing the .NET target version.
John
-
My app is working as a plugin for Rhinoceros 8.0 (WIP). Rhinoceros is a 3D modelling desktop application able to load plugins (.dll). More info here.
My plugin compiles and builds correctly.
The error occurs when Rhinoceros is trying to load the plugin that is the moment when the license validation occurs.
Rhinoceros 8.0 WIP is linked to framework.NET 4.8 and my plugin too. I tried 4.8 and 4.8.1.
Jordi
-
Hi Jordi,
The QlmLicenseLib.dll is a .NET Framework 4.52 assembly which should work if .NET 4.8 is installed on the target system.
However, it appears that Rhino is using the .NET Mono Framework implementation of .NET 4.8.
My guess is that the .NET Mono implementation does not include by default the assembly:System.Security.AccessControl.CryptoKeyAccessRule
I found this article online but I'm not sure it's up-to-date. Perhaps there are Mono NuGet packages that you can download to install the missing assembly.
Please sign in to leave a comment.
Comments
7 comments