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 ).
Software Potential Service
- Programatic License Deactivation: - With this release of the Software Potential service it is now possible to programmatically deactivate a license for a specified Device. Prior to this release a license could only be deactivated manually via the Software Potential web portal. To deactivate a license for a given device call DeactivateDevice(string deviceId, string licenseId) on the License Management web service; the license must be identified by its LicenseId not its Activation Key.
Please note that, as with manual deactivation via the web portal, this mechanism does not remove/delete the license file installed on the target device but does allow the license to be activated on a replacement machine if required. However you can implement your own mechanism to ensure the license is deleted before or after the license is deactivated on the Software Potential service.
- Configurable Device Label: - In addition to the DeviceID a Device Label is displayed in the SP portal pages to make it easier to identify devices on which activations have taken place. By default the device label is set to the device MachineName. With this release it is now possible to configure the SpAgent Activation process to create a custom Device Label. Use the SetDeviceLabelPolicy() extension method in the SpAgent.ProductCustomizations (C# or VB) code spit to set the DeviceLabel. In the web service API a DeviceLabel filter property has also been added to the GetActivationsByFilter method.
- VS2015 and MSBuild 14 Support Added: - A problem with processing PDB files that prevented protection/licensing of debug releases of applications developed using MSBuild 14 has now been fixed with this release of the runtime. As VS2015 uses MSBuild 14 by default some customers may have experienced this issue when using pre-GTM release of Visual Studio but it can affect any build environment that uses MSBuild 14.