Embed Validation folder in my project to prevent Standard.Licensing.dll from being replaced

[santiago-ribero]

Hi. I was wondering if by referencing the Standard.Licensing nuget package, it is possible for a "customer" to circumvent the licence validation by replacing the original Standard.Licensing.dll with a dummy version of it, that implements the same interfaces, classes and public methods but doesn't validate anything.
In order to make sure this doesn't happen, I consider including in my core project the classes that are in the Validation folder. Do you agree this is a good approach?

Thank you so much.

[CraigRichards]

Hey @santiago-ribero,
I'm reviewing this library as well. Thanks for your thoughts.

In regards to this

• Compiling Standard.Licencing into your project sounds like a good approach along with Obfuscation.
• You could also consider taking a checksum of the external dll and validate.

What do you think?