Most of the software is distributed as trial or evaluation versions. Nonetheless, weak and vulnerable protection mechanisms may jeopardize the security of your source code and enable competitors or hackers get access to the full functionality of your application, thus stultifying your efforts and time invested into development. Development of a commercial application never stops when the last line of code has been written. Delivering the product to potential clients is very important as well. The choice of the right protection utility that will satisfy your specific needs may be anything but easy. If you are looking for a rock-stable, reliable and elegant code protection solution, make sure not to miss "Spices.Fortress".

Among the advantages are:

- use of only native (but characteristic of C#) means;
- the Key is not checked but is used to restore the protected functionality;
- protection of .NET applications, not their obfuscation;
- protection of the data needed to run the application, not the code itself;
- no external processing of C#-produced protected executables;
- each Key contains personal data, therefore each Key may be easily identified.
- the protected executable is natively compiled by C# (hence no compatibility problems);

    Spices.Fortress is an intuitive, elegant and affordable product for developers seeking a better way to guard their products from unwanted intrusion and willing to have a simple, yet efficient mechanism of limiting the functionality of trial and evaluation versions of their software. When applied, Spices.Fortress changes the source code of the form in such a manner that after re-compiling each event guarded by Spices.Fortress has no event handler assigned. When a protected application is started, the trial event handlers are assigned to corresponding events. If a valid Fortress Key is found, registered event handlers replace the trial ones. The protected application does not use any checking routines to choose which set of event handlers to use. Instead, it uses the information stored in the Fortress Resource and the Fortress Key to assign registered event handlers to corresponding events. To be guarded by Spices.Fortress, a C# form must contain components that have events with assigned event handlers.
The personal data stored in each Fortress Key allows to easily identify each valid Fortress Key.

    Spices.Fortress guards the forms of C# projects on the source level, which means that Spices. Fortress temporarily changes the source code and then, after recompilation, the application is safe. When protecting applications, Spices.Fortress uses only native C# means, i.e. no external processing of C#-produced executables takes place. It is important that it is not the code, but the information required to run the application is protected. In .NET Windows Forms applications data is a link between events and event handlers. The difference between the trial and the registered versions is based on the use of different event handlers for trial and registered versions of the protected application. The trial version uses one set of event handlers, whereas the registered version uses another one.

For more information visit http://www.9rays.net/products/Spices.Fortress.