We are very happy to announce the immediate availability of new Service Packs for the following Text Control products:
TX Text Control 32.0
- Service Pack 2 for TX Text Control .NET Server for ASP.NET 32.0
- Service Pack 2 for TX Text Control .NET for Windows Forms 32.0
- Service Pack 2 for TX Text Control .NET for WPF 32.0
- Service Pack 2 for TX Text Control ActiveX 32.0
Once you have taken a look at the fixed known issues, please download and install the service pack.
Important Changes
In Service Pack 2, we have made a number of significant changes and improvements in a variety of areas:
-
Licensing Mechanism
For .NET 6 and better: The licensing mechanism has been updated to be independent of .NET and existing licensing mechanisms. Version 32.0 no longer uses the .NET license compiler (lc.exe), so entries in the licenses.licx file are no longer required.
No changes are required. The NuGet package update removes the licenses.licx file and places a new license file that is used to compile the license into the assembly. Existing licenses are compatible and will continue to work after the update.
For .NET Framework: The licensing mechanism remains the same and is backward compatible.
Learn More
TX Text Control 32.0 SP2 has been released. This service pack includes a new licensing mechanism for all .NET based versions of TX Text Control. This article gives an overview of the changes and how to migrate existing applications to the new licensing mechanism.
-
NuGet Packages
The NuGet packages have been updated to be compatible with .NET 6 and better. The libraries in the package are now .NET 6 target libraries.
-
Licensing Entry Assembly
As of 32.0 SP2, TX Text Control can be used in class libraries and called from other unlicensed assemblies. In previous versions of TX Text Control, the license must have been compiled into the main calling assembly. The new static property EntryAssembly has been introduced to allow you to specify where the TX Text Control should look for the license.
The following code shows how a UserControl that contains the TX Text Control license can be called from other assemblies without a reference to TX Text Control and without a license.
Learn More
TX Text Control 32.0 SP2 has been released. This service pack includes a new licensing mechanism for all .NET based versions of TX Text Control. This article gives an overview of the changes and how to migrate existing applications to the new licensing mechanism.
-
Unit Testing
As a result of the changes described above, the TX Text Control can now be tested using unit tests such as NUnit and MSTest. Test frameworks such as NUnit and MSTest use precompiled calling assemblies that cannot be modified. Testing frameworks are now fully supported in version 32.0 SP2.
Learn More
Unit testing is a common practice in which code is tested in isolation. This article shows how to use TX Text Control .NET 32.0 in such environments, and in particular how to handle licensing.
Unit Testing with NUnit and MSTest and TX Text Control .NET 32.0
-
Azure DevOps - Build Servers
Based on licensing mechanism changes, Azure DevOps can now be used to compile applications using TX Text Control via CI/CD pipelines. Licenses no longer need to be precompiled, and NuGet packages can be easily downloaded and restored from DevOps Artifacts.
Learn More
Continuous integration is a common practice in which code is compiled on build servers at regular intervals for testing after commit or at specific stages of development. This article shows how to use TX Text Control .NET Server for ASP.NET 32.0 in such environments, and in particular how to handle licensing.
Azure Pipelines with TX Text Control .NET for ASP.NET 32.0 with Azure DevOps and Artifacts
Windows Forms .NET - VS Designer Support
Microsoft has made many changes to the Visual Studio Windows Forms designer for .NET (.NET 6, 7, and 8) applications. After many changes in TX Text Control 32.0 SP2, the full Visual Studio experience is now available again, including toolbox support, smart tags and NuGet package support.
Where to Download the Service Pack?
We have merged the full version and service pack setups into one unified setup. This setup automatically detects whether to patch an installed version with service pack files or to install a new version.
The full version setup files in your Text Control license management portal have been updated automatically. In order to apply the service pack, please login to your Text Control store account and download and install the latest version.
If you don't have access to the portal as an account owner, you should have received an e-mail with valid download link for the full version. Learn more here.
Update Strategy
A new service pack contains bug fixes and minor updates to a large number of components that may be a part of your Web application. It is highly recommended that you update your applications to the latest version.
We published a tutorial that helps to update an ASP.NET Web application that uses the Document Editor, Document Viewer and key libraries such as the ServerTextControl and MailMerge.
Service Pack Update Strategy for TX Text Control .NET Server for ASP.NET
The support department is ready to help you with all your questions about Text Control products.
