Software Potential 3.2.1928

To avail of the Runtime features included in this release you will need to update and download your current permutation

Sp.Agent

Performance Improvement

We have made improvements to the performance of Sp.Agent when running protected code.  In addition, when licensing is not required, it is now possible to significantly improve performance of protected code by using the [InternalFeature] attribute when selecting methods for protection. It is NOT possible to use this attribute if it is also intended to license the method i.e. require a license to execute the method.

Multiple core support

It is now possible to run protected code in multiple assemblies in a single hosted environment (e.g. single AppDomain Base) with each assembly protected by a different permutation.  For example this may arise in the case of a developer of a CRM Online solution that is aggregating via ILMerge components protected with different permutations so as to meet the CRM Online requirement to have a single DLL to deploy.

License Renewal/reactivation

Sp.Agent now supports license renewal (both in online and disconnected/manual modes).

FIPS Compliance

It is now possible to install code protected by Software Potential in environments where FIPS compliance policy is enforced i.e. on machines where the customer requires only FIPS compliant crypto.

Heretofore in these environments, typically in Government and Financial Services organisations, it had been necessary to disable this policy on machines where protected code needed to be installed.

Bug Fixes

Custom Tag License Locking

Software Potential offers a mechanism to ensure that a license can only be reactivated when the same Custom Tags are included in the subsequent activation as were included in the initial activation.  This can be used to lock a license to an aspect of the environment in which the license is to be activated e.g. to ensure a site license can only be activated in the same domain as it was originally activated.

There had been an issue where such locks

• Were not being maintained when a license was reissued
• Were not being correctly enforced in certain circumstances.

These issues have now been resolved.