#dotnet api

In the latest release of document conversion API for .NET version 18.8, numerous updates including new features, enhancements and bug fixes have been introduced. A new class, PdfFormattingOptions is added, allowing users to set formatting preferences while converting files to PDF format. With this release, you can implement specific options in your dotnet applications when transforming Text TXT documents. Image to PDF conversion is upgraded, obsolete constructors and properties are removed and a few important security improvements are also added.

How you can seamlessly eSign your documents? Whether it is manual or automated procedure? There are no hard and fast rules, individuals can add e-Signatures into their files manually or, there could be an automated approach for batch processing. If you are a programmer and would like to code an app on .NET platform which lets you digitally sign numerous types of files, you can consider using GroupDocs.Signature for .NET API. It supports adding text, image, digital, barcode, QR-code and metadata type signatures into PDF, Microsoft Word, Excel, PowerPoint, Text, JPEG and TIFF files proficiently.

Do you frequently send or receive documents electronically? If so, you will be familiar with the importance of protecting sensitive information contained within digitally processed documents. Text encryption, hiding or even removing specific types of information from the documents are few different ways of securing your files.

A question, why would you need to protect this type of information anyways? What’s the big deal? Well, everyone may have his own reasons, depending upon the kind of documents and data in question, key principle stays the same; to be sure that the information being transferred electronically is safe, it isn’t manipulated in any wrong or harmful way.

So, in conclusion, we want to transfer documents over the internet, but we want to be able to protect document contents by any means feasible. Considering it could be cumbersome processing a bunch of files manually, we can use an API which lets us develop apps for hiding or removing sensitive document data and automate the whole process. If you are working on .NET platform, you can leverage the newly launched GroupDocs.Redaction for .NET API. It is a feature rich document redaction API which helps you obscure classified text, metadata or tabular data from document contents, comments and annotations inside your PDF, Microsoft Word, Excel and PowerPoint files. Learn more – http://bit.ly/redact-documents

Editing different types of documents programmatically on different development platforms is almost a given when talking about document manipulation in general. Most basic requirement is to modify file contents, then re-convert the file to original or even a different format too. Add to it some other perks like multiple sources for loading documents, securing the resultant documents and so on.

So, an API offering document editing features plus the document we wish to edit is all we need to get started. If .NET platform is your forte, you can try GroupDocs.Editor for .NET API, which is a feature rich file editor helping you in developing simple, scalable C# and ASP.NET apps which integrate with different HTML based editors to modify your Microsoft Word, Excel, OpenDocument, Text, HTML and other types of documents.

Latest release of this .NET API supports a refined set of lists and paragraphs to use in HTML editors. Additionally, you have access to a more stable multi-threading environment thus allowing you to further enhance your document editing experience. Try free today – http://bit.ly/2DZY99S

GroupDocs Newsletter February 2019 edition brings you latest news and updates related to all recent API releases plus much more. In the spot light is GroupDocs.Signature Product Family, which is an extensive collection of .NET and Java document e-signing APIs, allowing programmers to digitally sign their multi-format documents by adding various types of e-signatures including text, image, barcode, QR code and metadata signatures.

In other product news, GroupDocs.Search APIs for .NET and Java platforms now support blended characters and wildcard character search functionality to further enhance your indexing apps. While e-signing Image files within your .NET apps, you can add or search metadata with the help of GroupDocs.Signature for .NET API.

There are a few notable code examples also highlighted in this newsletter; you can render filtered messages from Microsoft Outlook data files OST & PST on .NET platform. Seamlessly convert your Java based IGS, PLT and CGM file formats, or, programmatically change page orientation (portrait, landscape) of your documents within any type of Java apps.

Continue reading at the newsletter blog – http://bit.ly/groupdocs-newsletter-february-2019

If you are a software developer, and you are looking to programmatically incorporate document automation functionality into your applications on .NET platform, there are not many APIs which offer you the convenience of use bundled with a proven feature set and seamless processing. Of the few APIs you could trust, GroupDocs.Assembly for .NET is surely one to consider.

It envelops a range of very useful functions giving you the edge when assembling various types of commonly used documents formats, from different data sources such as database, JSON, XML, OData and Custom .NET Objects. An important feature of this automation API is the ability to dynamically assemble external documents. This feature is currently available for Microsoft Word and Email formats.

If you are looking for a text search API offering you a diverse set of features to build search and indexing applications on .NET platform proficiently while working with Microsoft Office, OpenOffice, PDF, ZIP archives and different other types of documents, look no further than GroupDocs.Search for .NET. 

One of the notable features of this .NET API is the use of blended characters within your apps. These characters help you reduce search terms and when indexed, blended characters get simultaneously interpreted as valid letters as well as separators.