C# Demo Project of an ASP.NET PDF Viewer Built Based on the GroupDocs.Viewer for .NET Library

GroupDocs.Viewer for .NET

Building a simple ASP.NET PDF viewer is quite a trivial task. There are tens of different open source projects across the web that offer a quick and free solution to display PDF documents in both ASP.NET MVC and Web Forms. Often a simple implementation of a PDF viewer is all you actually need. But things become a lot more complicated when the viewer needs to meet your customer’s business requirements. The most common are:

1. Security. This obvious business demand creates great challenges for developers when implementing a PDF viewer. Businesses demand uncompromised security for their confidential documents. You need to prevent any access to source PDFs from the client-side and limit or totally restrict viewers from being able to download, print or copy the shared PDF documents.

2. Cross-Platform Compatibility. Businesses require being able to share PDFs with customers, partners and team members without worrying about whether they have the software needed to open the documents. Hence, you need to be sure that end users can access and view the shared PDF documents from any web-enabled device and regardless of the browser used.

3. Usability. Finally, businesses want to have tools delivered by standard office software, such as Adobe Reader, to be able to seamlessly browse and collaborate on PDF documents from a web-browser.

If you’ve been looking for an ASP.NET PDF viewer that meets all the mentioned requirements, you may be interested to try out this C# demo which is built based on the GroupDocs.Viewer for .NET library. The demo helps you quickly setup, configure and explore key features and functionality of the out-of-the-box PDF viewer for ASP.NET.

Before proceeding, I’d like to clarify that the GroupDocs.Viewer for .NET is a commercial library and is not free or open source. The C# demo includes a free evaluation copy of the library that has several functional restrictions. However, I’d strongly encourage you to contact GroupDocs support for a free 30-day license to be able to test the ASP.NET PDF viewer without any restrictions.

So, here we go. First, let’s look into how the library works:


GroupDocs.Viewer for .NET is a downloadable library (DLL) that allows you to display different types of documents (including PDF) on the web. What makes it stand out from other web-based PDF viewers is its client-server (or “thin client”) architecture.

Unlike client-based viewers, GroupDocs.Viewer for .NET doesn’t download source PDFs to end user machines. Instead, the library converts original documents stored on the server into a set of HTML markup, CSS and images. Once converted, a web-compatible copy of the PDF document is streamed to clients and rendered in web-browsers just like a regular web-page. Web copies look exactly like the original PDFs. Layouts are retained and fonts are sharp.

Such “thin client” architecture allows you to build an ASP.NET PDF viewer that meets both of the two core business requirements – security and cross-platform compatibility. End users can view PDF documents using a standard web-browser and without having to install Adobe Reader, Flash or any other plugins. For sure, PDF documents can be properly displayed in Chrome, Mozilla Firefox, Safari5+, Opera and, what is important, in commonly used by large organizations – Internet Explorer 8+.

The original PDF files are not downloaded to user machines during view sessions, but stay secure on your server and behind your firewalls. Combined with the in-built Digital Rights Management (DRM) features, this allows businesses to share PDF documents in a “read-only” mode. DRM controls all document copy options available in a web-browser, including downloading, printing and text copy/pasting. It allows users to decide on their own which PDFs to share in the “read-only” mode and which – with full access rights.

When displaying PDF documents in a web-browser there is another potential security flaw, called “Print Screen”. This is where even DRM won’t help. To deal with the issue, we’ve implemented a capability to add watermarks over the displayed PDF documents. The watermarks are only rendered as a separate layer on top of the displayed documents, so that your original PDFs are not altered.

Now, what about usability?


GroupDocs.Viewer for .NET comes with an out-of-the-box GUI which can be seamlessly white-labeled and integrated into any ASP.NET site. The GUI provides end users with tools needed for convenient viewing and navigation of PDF documents in a browser. Our sample PDF viewer for ASP.NET provides all the most commonly used UI controls available in native Adobe Reader’s plugin, including:

  • Scroll view, one page in a row, two pages in a row view, double page flipping
  • Page rotation and zooming
  • Page thumbnails
  • Text selection and copying to the clipboard
  • Text search with different match types
  • Document downloading and printing

The GUI can be seamlessly customized and embedded straight to your ASP.NET site. Alternatively, you can build your own GUI from scratch to meet your customer’s requirements.

But enough with words – let’s take a look how this works. Below is an example of how your ASP.NET PDF viewer built based on the GroupDocs.Viewer for .NET library may look:


  • Being a “thin client” solution, GroupDocs.Viewer for .NET doesn’t require any downloads or installations on the client side. End users can view PDF documents from any standard web-browser, including IE8+, Mozilla Firefox, Chrome, Opera, Safari5+ and their mobile versions.
  • To deploy and properly configure the sample on the server, you will need a .NET Framework version 4.0+ and a “.NET-compatible” web-server: IIS, IIS Express or ASP.NET Development Server (Cassini).
  • The viewer works with both ASP.NET Web Forms and ASP.NET MVC version 3+ frameworks.

Running the Sample

To help you setup and run the ASP.NET PDF viewer quickly, we’ve prepared a quick start guide. Please refer to this page for further instructions, as well as to download the C# demo itself.

For more details on the GroupDocs.Viewer for .NET library and the list of all supported file formats, please go to the products homepage.

GroupDocs Customer Newsletter – March 2015

GroupDocs logo Monthly Newsletter
March, 2015

GroupDocs.Viewer: Burn in Watermarks to Protect the Documents You Share

Not a long time ago, we’ve implemented an ability to share documents in a PDF format. When enabled, viewers can download only a PDF copy of your original document. Today, we’re pleased to announce an enhancement to this feature.

Starting from version 2.8.0, you can set GroupDocs.Viewer for .NET to burn in custom watermarks to PDF copies of shared documents, while your original documents stored on the server stay intact.

Find Out More >>>

Product News
New and Coming Soon to GroupDocs.Signature for .NET

In the latest release we've implemented a capability of verifying unique reference IDs applied to signed documents. This allows you to control whether a document was actually signed using the GroupDocs.Signature interface / library, or via some other application or tool. Here is how this works:

1. A unique reference ID is generated automatically upon signing a document. The ID is burned into the signed document as metadata and also streamed to your server using the sign method, so that you can save it.

2. Once you receive a signed document, you can verify whether the document was signed using the GroupDocs.Signature interface by checking your saved reference IDs with one in the document’s metadata.

As you may already know, GroupDocs.Signature can be used either programmatically, as a document e-signature engine, or in conjunction with an out-of-the-box UI that comes with the library. In case you use it as a pure engine, the reference ID is returned by the sign method. And when using the library along with the in-built UI, the reference ID is also saved to a database for the corresponding document. Grab the latest GroupDocs.Signature for .NET release from here.

New and Coming Soon to GroupDocs.Conversion for .NET

In this months release we've added resize functionality for document page images, when the input is from a file or an input stream. Also we've added new Image Save Options to allow users to define the output image resolution, and new Html Conversion Options which give users 2 different rendering engine options when converting HTML files to other file formats. Grab the latest GroupDocs.Conversion for .NET release from here.

From The Library
GroupDocs.Viewer for .NET Library Version 2.8.0 – Discover New Features and Enhancements in this Release

This month we've implemented several new useful features in the GroupDocs.Viewer for .NET libary, including: faster and smoother page scrolling when viewing large documents (>100 pages); Italian localization support and new document page layouts, optimized for books - learn more.

Improved API and New Features in the GroupDocs.Viewer for Java Library Version 2.7.0

In this release, we've updated the InputDataHandler interface which makes the process of handling documents from custom storage sources a breeze. We've also added the ability to rotate document pages in the image-based rendering mode. A detailed description for all new features implemented in this release along with download URLs for the latest sample projects can be found here.

How Can We Help You?

Do you have ideas for what you'd like to see us do in 2015? Take a minute to tell us.

Product Releases And Updates
GroupDocs.Total for .NET – The latest versions of our .NET products packaged into one product suite. GroupDocs.Total for Java – The latest versions of our Java products packaged into one product suite.
GroupDocs.Viewer for .NET 2.8.0 - Intellisense XML documentation, new double page layout, Italian localization, improved scrolling for large documents, improved printing of PDF's. GroupDocs.Annotation for Java 1.8.2 - Search improvements, along with numerous small updates and bug fixes.
GroupDocs.Conversion for .NET 1.8.0 - Resize document page images, job progress notifications, image conversion resolution options, security enhancements and more.  

GroupDocs.Viewer for .NET Library Version 2.8.0 – New Page Layout, Smoother Scrolling and Enhanced Document Sharing Security

GroupDocs.Viewer for .NETRecently we’ve updated our GroupDocs.Viewer for .NET library up to the version 2.8.0. In this post I’d like to discover some of the most remarkable updates implemented in this latest version:

New Page Layout Options

So far, when viewing documents, you had the following page layout options:

  • Scroll view – pages are placed in a continuous chain, one after another.
  • One page in a row – one page fit to client’s screen. No page turn animation.
  • Double page flip – two adjacent pages fit to client’s screen, plus flipping page animation (available in the image-based rendering mode only).

Starting with this new version, you have a choice between two more options:

  • Two pages in a row - two adjacent pages fit to client’s screen. No flipping page animation. This layout is available in both the images-based and the HTML-based rendering modes. This layout is especially useful when viewing documents on a widescreen display, as it allows users to cover unused screen space appearing when viewing documents with the scroll view or one page in a row layout.
  • One more layout added in this release is actually a modification of the above one – a cover and then two pages in a row. This is useful when reading books, as the cover page can be placed apart from the subsequent adjacent pages.

All the options can be configured by end users on their own, straight from the viewer’s GUI. You can also set a default layout using the Layout method from the GroupDocs.Viewer widget. This method accepts a Groupdocs.Web.UI.ViewerMode enumeration, which has the following values: ScrollView, DoublePageFlip, OnePageInRow, TwoPagesInRow, CoverThenTwoPagesInRow.

Italian Localization

The geography of clients using the viewer grows rapidly. This time we have good news for our customers from Italy – an Italian GUI localization has been finally added in this build. The following are all GUI localizations currently available:

  • ar-AE - Arabic (U.A.E.)
  • en-US - American English, the default
  • es-ES - Spanish
  • it-IT - Italian (Standard)
  • nb-NO - Norwegian
  • pl-PL - Polish
  • pt-PT - Portuguese
  • ru-RU – Russian

The default localization is en-US. You can change it to any other from the list above by using the Locale method from the GroupDocs.Viewer widget. There are two overloads of this method: the first one accepts the needed locale as a string code, while the second one accepts an enumeration value. They are completely equal, so you can use any of them.

Virtual Scrolling

The new virtual scrolling feature improves page scrolling speed in client browsers. This is useful when displaying large documents of more than 1k pages. When enabled, the viewer streams to the DOM tree only the pages that are currently visible in the browser. New pages are added to the DOM only when the document is actually scrolled to those exact pages. This way, instead of rendering all document pages, the viewer needs to handle only a few pages at a time.

An accompanying effect of this feature is the ability to get rid of the "Script hanging" message, which occasionally appears when opening or closing large documents (>1k pages). The message was caused by the JavaScript code used to render wrappers for each individual page within a document, or when deleting the wrappers upon switching to another document.

To enable the virtual scrolling feature, you should apply the true Boolean value for the UseVirtualScrolling method in the GroupDocs.Viewer widget. When set to false, the virtual scrolling feature is off.

Faster Word Documents Rendering

A new parameter has been added – embedImagesIntoHtmlForWordFiles – to the UseHtmlBasedEngine method. When set to true, it forces the viewer to convert documents to HTML with SVG or raster images embedded straight into the HTML markup as Base64. Otherwise, images are stored as external files. Embedding images into the HTML markup significantly increases browsers’ rendering speed of Word documents that have a lot of images in them. Naturally, this parameter is available only in the HTML-based rendering mode.

Share Documents with Watermarks

Now you can let viewers to print or download a PDF copy of the original documents you share, along with watermarks burned in. This is useful when you want to prevent users from copying your content, while still need to share it with others. When enabled, viewers can print or download only a PDF copy of your original document with your custom watermarks in them. While viewers get a PDF copy with watermarks, your original documents stored on the server stay intact.

In order to enable this feature, you should apply watermarks, using the Watermark method from the GroupDocs.Viewer widget, and set the true value for the last parameter - printWithWatermark. Please note that this feature is disabled by default! You need to set it explicitly.

Other Enhancements

  • Added an XML documentation file (called Groupdocs.Viewer.XML) into installers to enable IntelliSense in Visual Studio.
  • A new SupportListOfContentControls option added. It allows you to display content controls with their headers, similar to what Microsoft Word does. Currently this option is available only in the HTML-based rendering mode.
  • Numerous code optimizations and bug fixes.

The new version of the GroupDocs.Viewer for .NET library is already available in our files archive, so you are welcome to download it, test it and report any issues or suggestions in our forum.

Add Microsoft Office Files, PDF and Image Annotation Functionality to Your Concrete5 Website

GroupDocs.Annotation for .NET Library logoGroupDocs.Annotation for .NET is a downloadable library that allows developers to add cross-platform, multi-format document annotation functionality to any web-based app or site. Recently we’ve created an add-on specifically for Concrete5 users to make it easy to integrate the library into their websites. The add-on has been approved by Concrete5 admins and is now available for download from the official Concrete5 marketplace.

How can Concrete5 site owners and developers benefit from this release?
With the GroupDocs.Annotation for .NET library integrated into your site, you can seamlessly embed over 50 document and image types along with an annotation widget to any page within your website. Supported file formats include: PDF and Microsoft Word documents, Excel spreadsheets, PowerPoint presentations, Visio diagrams, CAD drawings, raster images and a lot more. End users can view and annotate documents on your website using any standard web-browser and without having to install any office software.

GroupDocs.Annotation can significantly enhance your document collaboration workflows as it allows multiple users to annotate the same document at time. Moreover, users can access and annotate documents from anywhere, anytime and using any web-enabled device.

Another benefit – is the ability to share documents in a “read-only” mode. Original documents are not downloaded to user machines during view/annotation sessions. And thanks to the Digital Fights Management (DRM) feature, you can prevent users from printing, downloading and copy/pasting the documents you share.

This new integration is the second GroupDocs.Annotation add-on released for Concrete5. Earlier we’ve published an add-on that allows you to integrate the cloud-based version of the annotator. So, if you prefer a SaaS deployment option, please refer to this page, and if you are interested in the downloadable .NET version, please visit this page for further details on the integration and to download the add-on.

Improved API and New Features in the GroupDocs.Viewer for Java Library – Version 2.7.0

GroupDocs.Viewer for JavaGreetings!
Recently we’ve released a new version – 2.7.0 – of the GroupDocs.Viewer for Java library and in this post I’d like to share details about the most important enhancements we made in this latest version.

Among a number of code optimizations and improvements, we’ve added the ability to rotate document pages in the image-based rendering mode, added support to relative license paths, and the ability to rotate text watermarks within the PDF print adjustments.

But most importantly, we’ve updated the InputDataHandler interface to make the process of handling documents from custom sources easier. Now you can simply pass files’ GUIDs, IDs, paths, etc. without worrying about any internal encoding. Overall, the implementation and usage of the updated InputDataHandler interface became much simpler and more straightforward. We’ve prepared a detailed guide on how to configure the InputDataHandler interface – please see it on this page.

Also, we’ve updated samples built based on the library, so that you can explore the new APIs yourself. In particular, there are individual samples for Spring, Dropwizard and Servlets currently available for your choice. You can either download them from our website, or from the GitHub repositories:

For more details on the GroupDocs.Viewer for Java library, please visit its homepage. In case you have any questions, please feel free to contact our support team.

GroupDocs Customer Newsletter – February 2015


View this email in your browser
Share this issue: Facebook Twitter Google+ LinkedIn YouTube
GroupDocs logo Monthly Newsletter
February, 2015

Collaborative Document Annotation in your SharePoint Environment

GroupDocs.Annotation for .NET is a lightweight library that can add document annotation functionality to any Enterprise Content Management (ECM) system, Content Management System (CMS), or web based application. It allows end users to view, comment on, redact and securely share documents of more than 50 different file formats.

In this month’s newsletter we are pleased to announce the release of our latest add-on that allows SharePoint users to easily integrate GroupDocs.Annotation for .NET into their SharePoint sites and applications.

Find Out More >>>

Product News
Advanced options for converting multipage documents to HTML Files in GroupDocs.Conversion for .NET
In the latest GroupDocs.Conversion for .NET release, we’ve implemented several enhancements that allow developers to have more control over document conversions when the output file is in the HTML format. In particular, we added the option of converting multi-page documents into a single HTML file with all the content (image, texts, etc.) encoded within it. Also, documents can now be obtained directly from streams when converting them to HTML files. For more detail please read release notes and download the latest version on this page.
Display Icons and right-to-left language based documents using GroupDocs.Viewer for .NET
The GroupDocs.Viewer for .NET library can now display the Icon file-type and we have added improved support for the display of documents where text is right-to-left based. We also added the page rotation control in the image-based rendering mode. This can also be triggered via a new Javascript API method. Other improvements include an accent-insensitive search option and a Javascript API method for displaying the “loading document” overlay. Please download the latest library from this page.
From The Library
A new GroupDocs.Comparsion for .NET Sample Project
GroupDocs.Comparison for .NET allows comparing two versions of a PDF, Microsoft Word, PowerPoint, Excel, ODT, HTML or TXT files without using any third party software. Recently, we’ve published a new comprehensive sample in the code.msdn.microsoft.com sample gallery , so you are welcome to download and review it.
How to Fix a VirtualPath Issue in SharePoint 2013
During development of our plugin, integrating GroupDocs.Annotation for .NET with SharePoint, we encountered a difficult to resolve VirtualPath issue. This article provides details on how we fixed it and can save other developers a large amount of time when building custom SharePoint integrations based on GroupDocs or other 3rd party libraries. Read the article.
How Can We Help You?
Do you have ideas for what you'd like to see us do in 2015? Take a minute to tell us.
Product Releases And Updates
GroupDocs.Total for .NET – The latest versions of our .NET products packaged into one product suite. GroupDocs.Total for Java – The latest versions of our Java products packaged into one product suite.
GroupDocs.Viewer for .NET 2.7.0 - ICO and RTL formats support, a JS method for page rotation, accent-insensitive search and 15 more improvements. GroupDocs.Viewer for Java 2.7.0 - Rotate pages in the image-based rendering mode; plus a number of code improvements and optimizations.
GroupDocs.Signature for .NET 1.7.0 - Added support for pre-define/configure date formats, signature pen colors, watermark properties and field types. GroupDocs.Annotation for Java 1.8.0 - Additional language support, access to custom DAO’s and a document collaborator permission overriding API.
GroupDocs.Comparison for .NET 2.3.0 - Improved comparison accuracy for Word, Excel and PDF files; custom locales can now be added easily.
GroupDocs.Conversion for .NET 1.7.0 - Added the ability to convert multi-page documents into a single HTML file.
GroupDocs.Assembly for .NET 1.2.0 - Now supports PowerPoint as an output format and implemented a new simplified API.


Display and Securely Share Documents of More than 50 File Formats from within Your ExpressionEngine Website

GroupDocs.Viewer for .NETGreat news for ExpressionEngine site owners and developers. Not a long time ago we’ve published a new plugin that allows you to integrate the GroupDocs.Viewer for .NET library into your ExpressionEngine website. The plugin is now available for download from the EE marketplace.

This integration adds an ability to display 50+ types of documents right on your ExpressionEngine website. Among supported file formats are: PDF, Microsoft Word, Excel, PowerPoint, Outlook, Visio, RTF, CSV, CAD, multipage TIFF and a lot more.

One of the key features of the viewer is a capability to display documents in a “read-only” mode. Documents displayed within your website are not downloaded to user machines, but rendered in a browser just like a regular web-page. Thanks to the DRM (digital rights management), all document copying options (printing, downloading, text copy/pasting) can be easily disabled. This allows you to protect you content from unauthorized copying, while still sharing it with others.

This latest integration is the third GroupDocs.Viewer plugin released for ExpressionEngine. It allows you to integrate the downloadable .NET version of the viewer, which can be deployed on-premises. Earlier we also released plugins for the downloadable Java and cloud-based versions of the viewer.

If you already own a GroupDocs.Viewer for .NET license, you can use the plugin for free. In case you don’t have a license yet, you can still download the plugin for free and test it with an evaluation copy of the library.

For more details on the plugin and installation instructions, please visit its page on the official ExpressionEngine marketplace.

GroupDocs.Comparsion for .NET Sample – Compare Two Documents in C#/VB.NET and Display Diffs on APS.NET Sites

GroupDocs.Comparison for .NET LogoGroupDocs.Comparison for .NET is a diff/merge library that allows you to compare two versions of a document and generate a resulting file by applying or rejecting the differences found. Using the library, you can compare two Word documents, PDF files, PowerPoint presentations, Excel spreadsheets, TXT, ODT or HTML files.

The library is designed as a middleware which makes it easy for developers to integrate it into any document management/collaboration workflow. It is written in a 100% managed code and can be used in any .NET application with C#/ VB.NET or any other CLR-compatible languages.

The core engine of the GroupDocs.Comparison for .NET can be used in any type of applications with or without a GUI. For example, you can use the library to compare documents, generate a list of differences and even merge the compared documents programmatically in a console application.

In addition to that, the library comes with an out-of-the box diff view web interface. The UI along with specifically designed API methods for ASP.NET apps, allow you to seamlessly provide your end users with the capability to compare documents right in a web-browser, without having to install any office software.

To demonstrate its key features and different use cases live, we’ve created a sample project that is easy to explore and comes with a detailed description. The sample is now published on the code.msdn.microsoft.com sample gallery, so you are welcome to download and explore it.

For more details on GroupDocs.Comparison for .NET, its key features and support resources, please visit the products page.

How to Fix a virtualPath Issue in the SharePoint 2013

GroupDocs.Annotation for .NET Library logoThis article will guide you how to resolve a virtualPath issue that may appear in SharePoint 2013 when trying to add a 3rd party library (for example SignalR), or when you use the "~" symbol in the path. We encountered this issue while developing a plugin that allows you to integrate the GroupDocs.Annotation for .NET library into SharePoint.

Overall, the issue is quite strange, as it is not reported in the stack trace or logs. Googling it didn’t give us any valuable details either. After several hours of investigation, we found out that the issue appeared due to the SharePoint server got "frightened and faints" just because it saw the "~" symbol in the path (for example: Server.Mappath("~/testFolder/page.aspx")).

To resolve the issue, we should teach SharePoint how to work with this symbol. For doing so, we’ll create a custom handler that will override SharePoint’s common path handler. First, we need to create a custom http module that can be deployed to SharePoint:

1. Open your VisualStudio 2012 as administrator.
2. Create an empty SharePoint project.
3. Create a new class with the following code:

4. Register this GDPathProvider in the HostingEnvironment via the custom HttpModule:

5. In order to add the GdHttpModule to the application pipeline, we used the PreApplicationStartMethod assembly attribute that allows us to register the module via DynamicModuleUtility.RegisterModule when the application starts:

6. Finally, add this assembly to the web.config assemblies:

Done! Hope this will help you to deal with the issue when integrating any 3rd party libraries to your SharePoint environment.

Welcome to 2015 – GroupDocs customer newsletter, January

Share this issue: Facebook Twitter Google+ LinkedIn YouTube
GroupDocs logo Monthly Newsletter
January, 2015
Ending soon: great savings on GroupDocs.Total

With GroupDocs.Total, developers can create applications for viewing, annotating, signing, comparing, converting and assembling documents. It brings together all the libraries, apps and APIs that we have for a platform into one package at a reduced price. We're offering even better prices in January. But hurry: the offer ends January 31, 2015.

  • GroupDocs.Total for .NET and Java libraries: 25% off all license types.
  • GroupDocs.Total for Cloud apps: 25% off monthly plans.
  • GroupDocs.Total for Cloud APIs: 10% off annual Business and Enterprise plans.

Simply enter XMAS2014NWL when checking out to apply the discount.
The 25% off offer is only available on new GroupDocs.Total for .NET, Java and Cloud App purchases. The GroupDocs.Total for Cloud API offer is available to customers who sign up to, or upgrade to, annual Business or Enterprise Cloud API plans. Only available directly from GroupDocs.com.

Product News
Converting Documents with Java?
Last month, we introduced GroupDocs.Conversion for Java. The initial release converts Microsoft Word, Excel, PowerPoint and PDF files to images, and more. Find out more.
GroupDocs.Signature for .NET updates
The most recent release of GroupDocs.Signature for .NET adds flexible watermark features, and allows users to configure different pen colors for the signature field. In the next release of GroupDocs.Signature for .NET, we're adding methods that let you add, update or delete fields in document preparation mode. JavaScript widgets that support these features will also be added. These features will give end users greater flexibility to prepare documents for signature.
New and Coming Soon to GroupDocs.Annotation for .NET
We strive to make our applications and libraries easy to use and feature rich. We've recently added support for different annotation print modes to GroupDocs.Annotation for .NET. In the next couple of releases, we'll look at features that improve the end users' experience, such as the ability to resize annotations and the toolbar, as well as support for layers.
From The Library
Working with GroupDocs.Assembly for .NET
GroupDocs.Assembly for .NET lets you build ASP.NET, C# and VB.NET applications that simplify document assembly and automation. We've written an article that explains how the library's three components - the Template Editor, Questionnaire Builder and Questionnaire Executor - work and interact. Read the article.
Integrating GroupDocs.Conversion for Java with Maven
Working with Maven? We've created a worked example that shows how to integrate GroupDocs.Conversion for Java with Maven. The sample code helps you get up and going. Read the article.
How Can We Help You?
Do you have ideas for what you'd like to see us do in 2015? Take a minute to tell us.
Product Releases And Updates
GroupDocs.Total for .NET – The latest versions of our .NET products packaged into one product suite. GroupDocs.Total for Java – The latest versions of our Java products packaged into one product suite.
GroupDocs.Viewer for .NET 2.6.0 – Error messages that are more user-friendly and a range of other improvements. GroupDocs.Viewer for Java 1.7.0 – Support for DWG, EPUB, MPP and PPT, as well as Amazon S3 storage.
GroupDocs.Annotation for .NET 1.8.0 – Set pre-defined watermarks, change the color of underlines. GroupDocs.Annotation for Java 1.7.0 – Improved HTML and CSS creation and other fixes.
GroupDocs.Comparison for .NET 2.2.1 – Maintenance release with a number of fixes.
GroupDocs.Conversion for .NET 1.6.0 – Improved merge features and other fixes.

Back to top