Software Potential 3.2.1989 - Released 15/04/2016

To avail of the Code Protector or Runtime features/fixes included in this release you will need to update your current permutation and either a) install/update the appropriate NuGet packages for SpAgent or b) download & install Code Protector and Permutation (if using older Microsoft.Licensing SDK ).

Distributor

• Named User License for Distributor: - With this release of Distributor there is an option to issue Distributor licenses that may only be accessed by users that have been assigned to the license in the Distributor server by an administrator. Named users are assigned by the Distributor administrator without having to involve the vendor i.e. the administrator in the customer organization can add/remove user assignments where the minimum duration of the assignment is controlled by the vendor. Please see Getting Started With Named User Licenses guide for more details.

Software Potential Service

• Resident License SKUs Deprecated: - It is no loger possible to either create new SKUs for Resident Licenses or to update existing SKUs for Resident Licenses. It will still be possible to issue Resident Licenses from existing SKUs and to issue individual Resident Licenses using the Issue Resident License page in the Software Potential portal. Resident Licenses are supported in the Microsoft.Licensing runtime but are NOT supported in the newer SpAgent runtime.
  
  
• Standalone Unrestricted License Deprecated: - While it is still possible to issue a Standalone Unrestricted license for use with the older Microsoft.Licensing runtime a warning has been added in the License Issue page to indicate that such licenses are now deprecated.  While these licenses will continue to be supported in the Microsoft.Licensing runtime they are not supported in the SpAgent runtime. Vendors should cease issuing such licenses to customers.

Fixes

• Trigger protection automatically when using MS Build 12 or 14: - With this release the Slps.Protector.Targets file required to trigger automatic code protection during the build process is now added correctly to the MSBuild 12 and MSBuild 14 folders, on installation of the Code Protector SDK. (Prior to this, to correctly configure automatic code protection/licensing during the build process when using MSBuild 12 or MS Build 14, as a workaround it was necessary to copy the targets file manually to the correct location in the appropriate MS Build directory.)