What's New in DS Server 1.0

DS Server 1.0 was the first release of the product: a server you install yourself that provides the Document Editor, the Document Viewer and the DocumentProcessing Web API to web applications, secured with OAuth. Version 1.1 extended the Web API with PDF and barcode endpoints and added client packages. Read on for what the two releases contained and how they were installed; neither archive has a change log.

Releases

The TX Text Control version is the product version of TXTextControl.dll in each archive, and the .NET version is the target framework in TXTextControl.DocumentServices.runtimeconfig.json.

DS Server

• Three services. DS Server 1.0 provides the Document Editor, which edits documents in the browser, the Document Viewer, which displays documents and adds annotations and electronic signatures, and the DocumentProcessing Web API, which merges JSON data into templates and converts documents, for example to PDF. Introduction describes what each service does.
• OAuth security profiles. Applications access DS Server through security profiles, which hold the OAuth client ID and client secret of an application. See Creating Security Profiles.
• Admin portal. The admin portal is where you sign in as the administrator, register the license with a serial number and manage the security profiles. See Default Admin Password and Licensing.
• Trial tokens. Besides the downloadable trial version, a trial token gives access to a DS Server hosted by Text Control without an installation. See Trial Token.
• Installation on IIS. Version 1.0 ran on Windows in IIS with the WebSocket feature, and needed the ASP.NET Core Runtime 3.1 and the Visual C++ Redistributable Packages for Visual Studio 2013 and 2015 (x64).

Web API (1.1.0)

• PDF endpoints. A new group of endpoints handles PDF documents. POST documentprocessing/pdf/create creates a PDF document from a document in any supported format, with its encryption, digital signature and embedded files. POST documentprocessing/pdf/embeddedfiles returns the files embedded in a PDF document, POST documentprocessing/pdf/metadata its metadata, and POST documentprocessing/pdf/acroforms/fields its AcroForm fields. See PDF Documents and PDF Form Fields.
• Barcode endpoints. POST documentprocessing/barcodes/create creates a barcode image from a text. Four more endpoints return the default text, the maximum text length and the minimum text length of a barcode type, and check whether a text is valid for it. See Barcodes.

Client Packages

• 1.0.0. NuGet packages for ASP.NET Core connect the Document Editor, the Document Viewer and DocumentProcessing to DS Server, and npm packages for Angular the Document Editor and the Document Viewer. The packages request OAuth tokens themselves. The React packages @txtextcontrol/tx-react-ds-document-editor and @txtextcontrol/tx-react-ds-document-viewer followed on February 25, 2021.
• Admin package (1.1.0). The NuGet package TXTextControl.DocumentServices.Admin registers and licenses DS Server installations and manages security profiles from code. See the .NET API reference.
• Angular DocumentProcessing (1.1.0). The npm package @txtextcontrol/tx-ng-ds-document-processing creates documents from Angular applications.
• Versions (1.1.0). The NuGet and Angular packages were released as version 1.1.0 and the React Document Editor package as version 2.0.0, all compatible with DS Server 1.1.

Client-Side Libraries describes the current packages.

Related Pages

• DS Server Released: On-Premise Document Services: the release article of 1.0.
• What's New in DS Server 1.1: the release page on dsserver.io.
• DS Server 1.1 Released: PDF and Barcodes: the release article of 1.1, with the new endpoints and package versions.
• Version 2.0: the next major version.