TX Text Control Blog

ReportingCloud: Reference implementation of TX Text Control X14 (24.0)

Björn Meyer

Blogged by Björn Meyer on December 9, 2016 and tagged with release, reportingcloud, mvc.


Text Control ReportingCloud brings the complete reporting functionality into the Cloud and makes it accessible for all platforms and programming languages using a highly available RESTful Web API.

The portal interface allows you to manage, upload, download and create templates and JSON data source excerpts. It implements the current version of TX Text Control .NET Server for ASP.NET and the included HTML5-based document editor TXTextControl.Web in it's ASP.NET MVC version.

The template editor within ReportingCloud is a kind of reference implementation of what's possible using this MVC control. This article gives an overview of key features of this implementation and how to implement them.

After a document has been selected from the list of available templates, you can choose a data source which is then loaded into the editor to fill the merge field drop-down lists.

ReportingCloud: Reference implementation of TX Text Control X14 (24.0)

In the Reports ribbon tab, the selected data source is used to provide the usable merge fields and merge blocks:

ReportingCloud: Reference implementation of TX Text Control X14 (24.0)

The following code shows the MVC HTML Helper of TX Text Control. It defines the service address (the rendering is calculated on different cloud servers) and the image file directory. Additionally, the JSON data source is loaded directly in the view using the LoadDataFromJson method. The template is loaded from a model property using the LoadText method:

The editor implements a dirty flag that determines whether the document needs to be saved or not. The file ribbon menu has been removed and a Save template button has been added to a bar at the top of the page. If the user is changing the document, the button get's enabled and the document can be saved:

ReportingCloud: Reference implementation of TX Text Control X14 (24.0)

The dirtyFlag will be changed on the new event textControlChanged and the save button will be enabled. On saving, the dirty flag will be set back to false.

If the user is clicking the Back button to get back to the template overview and the document has not been saved (dirty flag), a pop-up is displayed asking the user to save the document.

ReportingCloud: Reference implementation of TX Text Control X14 (24.0)

You can test this reference implementation by creating a free ReportingCloud account:

http://portal.reporting.cloud

Updating your TXTextControl.Web ASP.NET project from version X13 to X14 (24.0)

Björn Meyer

Blogged by Björn Meyer on December 2, 2016 and tagged with release, asp.net.


We just released version X14 of TX Text Control .NET Server for ASP.NET. Existing projects using the web control TXTextControl.Web can be easily updated.

ASP.NET Web Forms (AJAX)

In order to update an ASP.NET Web Forms project from TX Text Control X13 to X14, the following steps are required:

  • In the Solution Explorer, find the reference TXTextControl.Web, select it and remove it by clicking Remove from the Edit main menu.

    Updating your TXTextControl.Web ASP.NET project from version X13 to X14 (24.0)
  • Choose Add Reference... from the Project main menu. In the opened dialog, search for TXTextControl.ASP.NET, check version 24.0.400.500 and confirm with OK.

  • Find the web.config file in the Solution Explorer and open it. In the node configuration -> system.web -> compilation -> assemblies, find the entry for the assembly TXTextControl.Web. Change the version number from 23.0.400.500 to 24.0.400.500.

  • In the node configuration -> system.webServer -> handlers, find the handler entry for TXWebSocketHandler and change the version number from 23.0.300.500 to 24.0.400.500. Repeat the same for the handler TXPrintHandler.

  • Now, open the ASPX page that uses the TXTextControl.Web control and find the following Register script:

    Replace the version number from 24.0.400.500 to 24.0.400.500. Repeat this step for all ASPX pages that use TXTextControl.Web.

ASP.NET MVC

In order to update an ASP.NET MVC project from TX Text Control X13 to X14, the following steps are required:

  • Select Manage NuGet Packages... from the Project main menu to open the NuGet Package Manager. Find TXTextControl.Web in the installed packages and update to the latest stable version.

    Manage NuGet Packages

If the new NuGet package has been installed successfully, your project is already updated.

Updating ServerTextControl and DocumentServer

If your project uses the class ServerTextControl and the DocumentServer classes (MailMerge), you will need to update these references as well.

  • In the Solution Explorer, find the references TXDocumentServer, TXTextControl and TXTextControl.Server, select them and remove them by choosing Remove from the Edit main menu.

    Updating ServerTextControl and DocumentServer
  • Select your project in the Solution Explorer and choose Add Reference... from the Project main menu. In the opened Reference Manager, browse for most current versions of the TXTextControl.dll, TXTextControl.Server.dll and the TXDocumentServer.dll. Check these references and confirm with OK.

  • Find the licenses.licx file in your project and update the version numbers to the most current version numbers. You can also remove the version number completely, so that the license compiler uses the license of the referenced versions:

Enjoy version X14!

TX Text Control X14 for Windows Forms, WPF, ASP.NET and ActiveX released

Björn Meyer

Blogged by Björn Meyer on November 30, 2016 and tagged with release, asp.net, windows forms, wpf.


TX Text Control X14 released

We are more than happy to announce the immediate availability of TX Text Control X14. Inspired by the feedback of thousands of developers, we built a new version of TX Text Control that combines innovation and consistency. Read more about what's new in the following products:

ASP.NET

Windows Forms

WPF

ActiveX

Download Updated Trial Versions

If you would like to try out the new features of TX Text Control X14, please download one of the updated trial versions. The trial versions are fully featured and valid for 30 days.

Download trial version

Free Technical Support for Subscription Customers

The team of Text Control support engineers is waiting to assist you with every aspect of TX Text Control X14. Remember, technical support is unlimited and entirely free of charge for subscription customers.

Using TX Text Control .NET with Visual Studio Team Services (VSTS)

Björn Meyer

Blogged by Björn Meyer on November 28, 2016 and tagged with vsts, build server.


With Visual Studio Team Services (VSTS), Microsoft offers services for teams to share code and track their work. A major feature is the continuous integration support for projects. Hosted build agents can build the projects immediately or based on your specifications. Continuous Integration (CI) is a development practice where each check-in is verified by an automated build which enables teams to detect problems at an early stage.

Using TX Text Control .NET with Visual Studio Team Services (VSTS)

Visual Studio Team Services implement hosted build agents that can be used, in case the solution doesn't have other dependencies than these packages.

Text Control products are licensed on a per-developer basis. Each developer who uses our products must have their own, assigned license. If you are using a build server, all developers that check-in code, that uses TX Text Control classes, need their own license.

On hosted build machines provided by Visual Studio Team Services, no third-party software can be installed.

In order to use VSTS hosted build agents, the license must be compiled manually and the TX Text Control references must be copied to the BIN folder. On a local developer machine, the TX Text Control setup must be installed in order to compile the projects. The licenses are compiled automatically into the project assembly.

In order to prepare a project for Visual Studio Team Services, the license must be compiled manually. Generate the license resource file using following Visual Studio command line:

"%Compiler Path%\lc.exe" /target:MyApplication.exe /complist:licenses.licx /i:"%Assembly Path%\TXTextControl.Windows.Forms.dll"

  • %Compiler Path% is a path to the lc.exe tool (for example, C:\Program Files\Microsoft.NET\SDK\v2.0\Bin).
  • MyApplication.exe is name of the executable project assembly.
  • licenses.licx is a text file in the project folder.
  • %Assembly Path% is the TX Text Control installation Assembly folder.

The licenses.licx must contain one of the following license entries (learn more here):

AssemblyEntry
TXTextControl.WPF.TextControlTXTextControl.WPF.TextControl, TXTextControl.WPF
TXTextControl.TextControlTXTextControl.TextControl, TXTextControl.Windows.Forms
TXTextControl.ServerTextControlTXTextControl.ServerTextControl, TXTextControl.Server

The license compiler will generate the 'MyApplication.exe.licenses' resource file. Add this file to your project as an embedded resource and remove the licenses.licx from the project.

Additionally, add the used TX Text Control assemblies to your project and set the Copy to Output Directory to Copy always.

Using TX Text Control .NET with Visual Studio Team Services (VSTS)

If you start build processes in Visual Studio Team Services now, they will pass without license or dependency errors.

X14 preview: New integrated reporting dialog boxes

Björn Meyer

Blogged by Björn Meyer on November 24, 2016 and tagged with release, windows forms, wpf, reporting.


The new Reporting ribbon tab is based on the new public class DataSourceManager that encapsulates the complete handling, logic and ready-to-use dialog boxes for the reporting template creation task.

The dialog boxes help to build your own template designer to create templates compatible with the DocumentServer reporting framework MailMerge. The new set of dialog boxes includes the following:

  • DatabaseConnectionDialog (Windows Forms only)
  • DataSourceExtractionDialog (Windows Forms only)
  • EditDataRelationsDialog
  • InsertMergeBlockDialog
  • EditMergeBlocksDialog

DatabaseConnectionDialog

The DatabaseConnectionDialog class allows the user to build connection strings and to connect to specific data sources. This dialog is more a type of a wizard that navigates the user through a variety of dialog pages to build the connection string. The first page helps to select the data source type:

DatabaseConnectionDialog

When the data source is selected, the second page helps to define the server name or database file and to specify the user credentials to access the database. Additionally, the database name can be selected.

DatabaseConnectionDialog

DataSourceExtractionDialog

The DataSourceExtractionDialog class allows the user to save an excerpt from the currently loaded data source. The user needs to select the root table, the number of data rows for preview purposes and the file name:

DataSourceExtractionDialog

EditDataRelationsDialog

The EditDataRelationsDialog class allows the user to add or remove data relations to or from the current data source. The first dialog of this series provides an overview of data relations and allows the user to add and to remove relations:

EditDataRelationsDialog

The second dialog is the relation editor to create new relations between a parent (main) and a child table:

EditDataRelationsDialog

The relations are used by MailMerge for hierarchical data structures in merge blocks and nested merge blocks.

InsertMergeBlockDialog

The InsertMergeBlockDialog class allows the user to design and insert a merge block based on the currently selected master table in the DataSourceManager.

InsertMergeBlockDialog

This dialog inserts a pre-designed merge block or a nested merge block into the connected TextControl at the current input position.

EditMergeBlocksDialog

The EditMergeBlocksDialog class allows the user to remove or rename merge blocks contained in the current document. The dialog can be also used to navigate to a specific merge block.

InsertMergeBlockDialog

All of the above dialog boxes were part of the demo TX Text Control Words and are now available through the API as public dialog boxes.

Stay tuned for more details about TX Text Control X14!

Older blog entries

 
 
Call us: +1 704-544-7445 (United States)
 
 

Products

Support

Downloads

Corporate

Buy Now

About Text Control

Founded in 1991, Text Control is an award-winning Visual Studio Industry Partner and leading vendor of word processing and reporting components for Microsoft development technologies. The products help thousands of developers add comprehensive word processing functionality to their applications. Text Control is 100% self-owned and independent of all investor decisions. Customers benefit from these years of experience, large user-base, and at the same time, appreciate developing with a mature, reliable product.

SD Times 100SD Times 100SD Times 100SD Times 100SD Times 100SD Times 100Visual Studio 2015 Launch PartnerVisual Studio 2013 Launch PartnerVisual Studio 2012 Launch PartnerVisual Studio Partner