Not logged in▾
Log In Register
Forgot Password Resend Validation E-mail
In This Article

Converting to v25.1

All of the breaking changes are detailed or linked below.

We've introduced the new TrustedCodeService class in v25.1.2 as part of our secure-by-design initiative to protect your applications from potential security vulnerabilities related to dynamic type loading. This service implements a secure-by-default model where types or their containing assemblies must be explicitly marked as trusted before they can be dynamically resolved or instantiated from string type names. This prevents untrusted or malicious code from being loaded into your application through deserialization, configuration files, or other string-based type references. This kind of dynamic type loading is used sparingly and only as needed in our products.

Warning

This is an important change that may require action on your part. If your application uses features that dynamically create types from string names, you may encounter SecurityException errors until you configure the TrustedCodeService appropriately per the instructions in the Security topic.

We recommend configuring the service during application startup to ensure seamless operation while maintaining robust security protections.

Features that may use dynamic type loading are:

  • Bars - Deserialization of complete bar layouts when custom BarCommand classes are used.
  • SyntaxEditor - Deserialization of macros when custom edit action classes are used.

New Targets

All NuGet packages include a new target for .NET 8.

NuGet packages for the SyntaxEditor Text assemblies have been moved from .NET 6 to .NET 8. Those who still need to support older versions of .NET can use the .NET Standard 2.0 targets.

NuGet packages no longer include the legacy .NET Core 3.1 target. This target was previously used to support .NET Core 3.1 and .NET 5, neither of which are still supported by Microsoft. Projects that target .NET should be moved to .NET 6 or greater.

The .NET Framework configurations are unchanged.

Visual Studio 2019 Support Removed

Visual Studio 2019 does not support .NET 6 or higher, so it can no longer be used to build .NET applications that use Actipro components. Applications that target .NET Framework should continue to work, but compatibility is no longer verified with new releases.

SyntaxEditor Intra-Text Adornment Placement Updates

This version enhances the Intra-Text Adornments feature with the ability to position the intra-text adornment after the tagged text range instead of before. This option is handy for scenarios such as when AI suggestions should be displayed at the end of a line, after the last character.

The IsSpacerBefore property was added to the IIntraTextSpacerTag interface to support this new option. Any classes implementing this interface should return true for this property to retain prior version functionality where the adornment appears before the tagged range.