Maxtocode is the most-secured .NET protection technology which utilizes a combination of deep obfuscation, strong encryption and a real-time technology that protects your software while it is being executed.
Assemblies encrypted with our Maxtocode trial version will only work for 15 days. Please DO NOT distribute it to your end users. If you decide to acquire a working copy from us, please order it from us and you will be able to download the original Maxtocode from your member panel.
A machine code is a unique identifier generated according to the combination of hardware parts in your computer. We need this machine code to generate a license key for you. To obtain this machine code, please start your unrestricted copy of Maxtocode (Note: not the trial version), click on “Help” -> “Register”.
Yes. Please give us your machine code after you make the changes to your computer hardware. We will generate a new license key for you free of charge.
If your software upgrade subscription has not expire yet, you could login to our client area and download the latest version of Maxtocode.
For applications running as windows services, please be sure to check “Encrypt Class Constructors” before executing Maxtocode protection. This will ensure your application to be setup as a Windows service correctly. During deployment, it is advised to deploy the Maxtocode Runtime under Windows\System32.
The reason is some virtual hosting space has limited rights to execute self-developed Windows dll files. A Maxtocode runtime comes with every Maxtocode-protected assemblies, this is a DLL that will be needed to run on your virtual hosting server, you will need to check with your hosting provider regarding this.
Maxtocode offers automatic entity renaming of your private entities in your assemblies. However if some of your entities use reflections, you would need to use manual renaming and manually check the entities that you want to leave out during entity renaming. Sometimes serialization also contain internal reflection, it is best-advised that manual renaming option is used for this scenario too. If you so decide to apply entity renaming to your public entities too, you would also need to use manual renaming.
There are a some possibilities that this will happen: 1. Assemblies are already protected by a tool from another vendor, if this is the case, use Maxtocode solely for your protection.
2. Maxtocode will inject a new class name into every of your assemblies, please make sure that the naming convention do not conflict with your existing class names.
3. Maxtocode does not support the environment that your assemblies run on, please contact us to confirm.
4. The Maxtocode runtime .dll filename conflicts with your existing assembly filenames, rename the Maxtocode runtime .dll filename.
5. Incorrectly-chosen obfuscation options during protection, rendering the protected-application to break, please contact us for assistance.
6. Try unchecking the “Encrypt Strings” and “Encrypt Class Constructors” and protect your assemblies once more.
7. If you tried all of the methods above and are still unable to make it to work , please contact us for assistance. We will get back to you with a workable solution.
Check this option if your assemblies consist of .EXE files and .DLL files. If there are only .DLL files in your assembly list, it is best-advised not to check this option.
Please direct all your questions to support@maxtocode.com we will make sure that we reply you in the quickest manner, normally within 24 hours.
If you can't find an answer here or in our Learn More page, you can always email support and we'll see what we can do to help.
Get to our Learn More page and learn how Maxtocode is different from other obfuscation and encryption tools out there.