Licensing Case, can Enigma Protector handle it? How?
Posted: Fri Jun 09, 2023 11:28 am
Hello,
I'm considering using Enigma Protector to license a software of mine, I looked through the documentation but I'm not sure if what I want to accomplish can be done.
Could you please give me an idea what approach to take in order to accomplish it or if I should consider other solutions?
Case:
I have separated my software into UI.exe, App1.dll, App2.dll. Both App1 and App2 are launched from UI.exe by clicking buttons. Also, check boxes and radio buttons in UI.exe are considered by App1 and App2.
I would like to have two separate license keys for App1 and App2, and I want to distribute UI.exe as a freeware but with some protection because it's .net application.
Do I have to create 3 EnigmaProtector projects?
- 1st - to protect UI.exe from easy seeing the source with ILSpy
- 2nd - to protect App1 to protect the source and request registration
- 3rd - to protect App2 to protect the source and request registration
I would also like to lock some of the functionalities of App1 and App2 for demo versions. Should that be separate application build or a separate EnigmaProtector project?
PS: Do you know if obfuscar works well with Enigma Protector?
Thanks in advance.
zooid
I'm considering using Enigma Protector to license a software of mine, I looked through the documentation but I'm not sure if what I want to accomplish can be done.
Could you please give me an idea what approach to take in order to accomplish it or if I should consider other solutions?
Case:
I have separated my software into UI.exe, App1.dll, App2.dll. Both App1 and App2 are launched from UI.exe by clicking buttons. Also, check boxes and radio buttons in UI.exe are considered by App1 and App2.
I would like to have two separate license keys for App1 and App2, and I want to distribute UI.exe as a freeware but with some protection because it's .net application.
Do I have to create 3 EnigmaProtector projects?
- 1st - to protect UI.exe from easy seeing the source with ILSpy
- 2nd - to protect App1 to protect the source and request registration
- 3rd - to protect App2 to protect the source and request registration
I would also like to lock some of the functionalities of App1 and App2 for demo versions. Should that be separate application build or a separate EnigmaProtector project?
PS: Do you know if obfuscar works well with Enigma Protector?
Thanks in advance.
zooid