Online Demos
Seeing a feature run is often the quickest way to decide whether it fits. The TX Text Control Technical Demos at demos.textcontrol.com show the Document Editor, the Document Viewer, PDF processing and server-side document processing at work in the browser, and each demo comes with the code that runs it. The site is an ASP.NET Core application on .NET 10 that uses the current packages of TX Text Control .NET Server with the Core engine; its header names the version it runs, 34.0 SP5 at the time of writing.
What a Demo Offers
Every demo has three tabs:
- Try it runs the example: an editor, a viewer or a form that creates a document on the server.
- Learn explains the concept: which problem the demo solves, which components and members it uses, how it works and the key code. Some link the blog article behind them.
- Code shows the files of the example, such as the controller, the Razor view, the JavaScript and the configuration, highlighted and in full. It's the code that runs the demo, not a simplified version.
The information panel of a demo also lists the NuGet packages it needs, each with a dotnet add package command. Every demo has a permanent URL for bookmarks and for sharing with a colleague or with support, and the search box of the navigation finds demos by name. No account or sign-in is needed.
The code is available on the demo pages only: the demos link no GitHub repository and offer no download. GitHub Examples lists complete projects that you can clone.
Sections of the Demo Site
The navigation groups the demos by product area. Each row links the first demo of a group:
| Example | What it shows | Where |
|---|---|---|
| Document Editor | The editor in an ASP.NET Core view: editing Word documents in the browser | Concept |
| Editing Features | Character and paragraph formatting, styles, sections, images, lists, links, tables, text frames, headers and footers, shapes, charts, barcodes and merge fields | Editing Features |
| Mail Merge in the editor | Designing templates: merge blocks, nested blocks, the Template Assistant, conditions and merging | Mail Merge |
| Advanced Features | Signature fields, footnotes, redaction, watermarks, comments, line numbering, form fields, tables of contents, tracked changes, formulas, spell checking and document protection | Advanced Features |
| Document Management | Loading documents from a view, a controller, JavaScript or the WebSocketHandler, and exporting PDF | Document Management |
| Customize | The ribbon and toolbars of the editor | Customize |
| Document Viewer | The viewer in an ASP.NET Core view | Concept |
| Viewer groups | Electronic signatures, PDF with PDF.js, form fields, annotations, tracked changes, search and the ways to load documents | E-Sign |
| PDF Processing | Creating PDF documents and ZUGFeRD invoices, fillable forms and form data, encryption and digital signatures | Creating PDFs |
| Server-side Processing | Mail merge with ServerTextControl, document conversion, document analysis and reporting structures such as merge blocks, conditions, barcodes and images | Mail Merge Concept |
| Interactive Coding | A guided lab in which you edit C# code that uses ServerTextControl and see the resulting pages: selections, paragraph formats, styles, fields, mail merge with JSON, headers and footers and tables | Selection |
The demos of each topic are listed on the other pages of this section, together with the GitHub projects of the same topic. The blog article Introducing the New TX Text Control Technical Demos describes the site, which Text Control rebuilt in August 2026. Articles and captured guides about the earlier demo site use links under /Chapter/Topic/, which now lead to the first demo of a section.
Run a Demo's Code Yourself
The code of a demo drops into an ASP.NET Core project that has the same packages:
- Create a project and install the packages that the demo lists, as Getting Started shows for each component. Licensed developers install them from the Text Control Private NuGet Feed; evaluators use the trial version, as Evaluating with the Trial Version describes.
- Copy the files from the Code tab into the corresponding folders of the project: controllers into Controllers, views into Views, scripts into wwwroot.
- Run the project and compare it with the demo.
The package versions that a demo lists can lag behind the current release; install the newest versions available to you. Package Overview describes what each package contains.
Find Demos by Topic
Next Steps
- GitHub Examples: complete sample projects to clone and run.
- Getting Started: build a first application with each component.
- Document Editor Examples: the demos and projects of the Document Editor.