We have completely rebuilt the TX Text Control technical demos to provide developers with a more modern, useful, and educational experience. The new demo platform is a modern ASP.NET Core application based on .NET 10 that uses the latest TX Text Control .NET Server for ASP.NET Core components. However, the changes extend beyond updating the underlying technology. Our goal is to transform the demos into a central location where developers can experiment with features, grasp their functionality, and observe their implementation. This is only the beginning. Over time, the demos will include significantly more educational content and become closely connected to the new TX Text Control documentation experience that we are currently developing. Built from the Ground Up with ASP.NET Core and .NET 10 The previous technical demos evolved over many years and several generations of web technologies. For the new platform, however, we started from scratch with a modern foundation. All demos now run as part of an ASP.NET Core application using .NET 10, adhering to current C# and ASP.NET Core development practices. More importantly, the examples are based on the latest TX Text Control Core version. The demo collection covers the major areas of the TX Text Control product family: Browser-based document editing Document viewing Electronic signatures PDF creation and processing Server-side document generation Mail Merge and reporting Annotations and document collaboration Document conversion and manipulation Each example focuses on a specific feature or implementation scenario. Rather than hiding functionality within a large sample application, the relevant Razor, JavaScript, JSON, and C# code is kept easily identifiable. Try It. Learn It. See the Code. One of the biggest changes is the way individual demos are structured. Every example is divided into three areas: Try it, Learn, and Code. Try It The "Try it" area contains an actual running example. Depending on the demo, developers can interact with the document editor, load documents into the document viewer, execute a mail merge process, manipulate PDFs, create signatures, or experiment with a specific TX Text Control feature directly in the browser. The goal is straightforward: before reading the documentation or source code, users can observe the feature in action. Learn The Learn section explains the concept behind each example. Rather than simply presenting a running application, we want the demos to answer questions such as: What problem does this feature solve? Which TX Text Control components are involved? Which API members are important? How does the document structure affect the result? Which implementation patterns should developers be aware of? Selected API calls and code snippets are included directly alongside the explanation. This is an area that we plan to expand considerably in the future. Our technical demos are evolving into more than just examples. They will increasingly provide educational content to help developers understand TX Text Control features and document processing concepts. Code The Code section displays the files used by the running example. Depending on the demo, this can include the following: C# Razor JavaScript JSON CSS Configuration files The code is syntax-highlighted and organized into expandable sections so developers can focus on the relevant part of the implementation. There is no separate, simplified pseudo-implementation. The code shown in the demo is the actual code behind the example. This establishes a direct link between the result visible in the browser and the necessary implementation. Making Complex Document Concepts Easier to Understand Document processing can quickly become complex. Mail Merge is a good example of this. While a basic merge field is easy to understand, real-world reporting applications often involve repeating blocks, nested data structures, master-detail relationships, conditional content, and dynamically generated tables. Simply showing the final document does not explain what happens behind the scenes or how the different parts of the process work together. The new demo platform gives us much more flexibility to visualize these concepts and provide additional context alongside working examples. For example, interactive illustrations can demonstrate how structured data maps to merge fields inside a template, how repeating blocks correspond to arrays and collections in the underlying data source, and how nested data structures translate into hierarchical document structures during the merge process. Your browser does not support the video tag. We plan to add more educational elements like these to the demo collection to make it easier for developers to understand the final result, the concepts, the data structures, and the processing steps that produce it. Our goal is to demonstrate not only that a feature exists and can be used but also how it works, why it works that way, and how developers can apply the same concepts in their own applications. Better Navigation and Feature Discovery TX Text Control has a comprehensive document processing API. Finding the right example shouldn't require knowing the exact name of a class or method. The new demo platform includes a structured, searchable navigation system to address this issue. Examples are grouped by product area and capability, making it easier to explore the following topics: Document editing Mail merge and reporting PDF processing Document viewing Electronic signatures Forms and form fields Annotations Document conversion Document management Each example also has its own permanent URL. This makes it easy to bookmark a specific implementation or share an exact example with another developer, customer, or the support team. Demos and Documentation Are Coming Together The new technical demos are an important part of a larger project. We are working on a new documentation experience for TX Text Control. Rather than treating documentation, API references, conceptual articles, and runnable demos as isolated resources, we aim to connect these elements much more closely. For example, a developer reading about a feature should be able to move naturally from the documentation to a working example. Likewise, someone discovering a feature through a demo should be able to access more detailed conceptual or API documentation directly. The new demo architecture has been designed with this integration in mind. Over time, the distinction between "documentation" and "demo" will become smaller. Developers should be able to learn about a concept, experiment with it, inspect its implementation, and transition to detailed reference material as part of one seamless workflow. Try the New TX Text Control Technical Demos We are excited to share the new TX Text Control technical demos with the developer community! Please explore the demos, try out the features, and provide us with your feedback. Visit the TX Text Control Technical Demos