Hi Svennebanan, thanks you for the respect
Back to your question, it is correct, markers can't be used in .NET applications. For .NET I always recommend to combine multiple protection features.
For example:
- you can emulate working of RegCrypt markers. There is Enigma API function EP_RegKeyInformation, it returns also an array of the sections that current registration key unlocks. Depending on the result of this function and sections array, you can run specific functionality
- another advice, more difficult to implement. You can carry some functionality from .NET managed code, to external unmanaged DLL, and you can use any markers inside this DLL. This dll should be protected with the same project file as a main executable.
- it is a good recommendation if you divide your software on two versions - DEMO (with restricted functionality) and FULL (full functional, but it can run only if you have valid registration key), same scheme is made for Enigma Protector. FULL version should be protected with the option Registration Features - Common - Encrypt with Encryption Constant. This will mean that code of application will be encrypted with the special constant which exists only in registration key. In case your full version will be leaked, nobody will be able to run (and crack it) without valid registration key.
- very good advice - use more different Enigma API fucntions for most integration of protection inside application. For example, some strings you may carry out from application and place into protection using Protection Features - Protected Strings. If cracker will try to bypass protection, executable will not work due to absent of protected strings and protection itself.
- then also try a Virtual Box feature - very interesting and I hope you can find it useful.
)?