Xceed PDF Library for .NET 3.1 introduces enhanced PDF/A standards validation, improved color handling with new RGBPaint y GrayPaint classes, more detailed validation results, flexible image exporting, and reliability improvements for PDF document processing. These updates give .NET developers greater control over PDF generation, validation, manipulation, and image extraction workflows.
Xceed PDF Library for .NET 3.1 introduces new capabilities for PDF/A standards validation, improved color handling, more flexible image exporting, and enhanced PDF document processing.
This release focuses on giving .NET developers greater control over PDF documents while improving validation accuracy and simplifying common document-processing workflows.
From generating PDF documents to validating archival standards and extracting images, version 3.1 delivers several improvements for developers building document-centric .NET applications.
What's New in PDF Library for .NET 3.1?
The latest release introduces several key enhancements:
- New RGBPaint and GrayPaint classes for more explicit color handling.
- PDF/A standards validation through the new ValidatePdfStandards() método.
- Expanded PDF/A support with additional profiles in PdfStandardOptions.
- Improved validation reporting with detailed error information.
- Flexible image exporting to file paths and streams.
- Reliability improvements for opacity, PDF manipulation, and raw content parsing.
Let's take a closer look at these updates.
1. Improved Color Handling with RGBPaint and GrayPaint
PDF Library 3.1 introduces an overhaul of how paint objects are handled within PDF documents.
The previous SolidColorBrush class has been replaced with two new classes:
RGBPaint
Provides a dedicated class for working with RGB colors, offering a more explicit approach to defining paint objects.
GrayPaint
Introduces a dedicated class for grayscale paint objects, allowing developers to work with grayscale values separately from RGB colors.
By separating these color representations, the updated API provides a clearer structure for handling paint objects in PDF workflows.
For developers upgrading from earlier versions, existing implementations using SolidColorBrush should be reviewed and updated to use the appropriate new class.
2. Enhanced PDF/A Standards Validation
PDF/A is an ISO-standardized PDF format designed to support long-term document preservation.
For applications handling financial records, legal documents, business archives, or other long-term documentation, validating PDFs against the appropriate archival standard can be an important requirement.
PDF Library 3.1 introduces the ValidatePdfStandards() method in DocumentoPdf, allowing developers to validate documents against supported PDF/A standards.
New PDF/A Validation Method
PdfDocument.ValidatePdfStandards()
Validate PDF documents against supported archival standards as part of document-processing workflows.
Expanded PDF/A Profiles
The release also expands PdfStandardOptions with additional PDF/A profiles.
| PDF/A Profile | Descripción |
|---|---|
| PdfA_2U | PDF/A-2 with Unicode text mapping requirements |
| PdfA_3B | PDF/A-3 basic visual appearance conformance |
| PdfA_3U | PDF/A-3 with Unicode text mapping requirements |
| PdfA_4 | PDF/A-4 archival standard |
| PdfA_4F | PDF/A-4 with support for embedded files |
Additional profiles are also included in this release.
These options give developers more flexibility when validating PDF documents against specific archival requirements.
Por qué importa
Developers can incorporate PDF/A validation into their .NET applications to identify standards-related issues before documents are archived or distributed.
Important: Validation identifies potential compliance issues; it does not automatically correct them.
3. More Detailed PDF Validation Results
Identifying PDF validation issues is an important part of maintaining reliable document-processing workflows.
In version 3.1, the PdfDocument.Validate() method has been improved to return a PdfStandardValidationResult containing detailed validation error information.
Instead of relying on a general validation outcome, developers can access more specific information about issues identified during validation.
Practical Applications
- Document quality assurance: Identify validation issues before PDFs are delivered to end users.
- Automated validation workflows: Incorporate validation results into document-processing pipelines.
- Error reporting: Provide more informative feedback when documents fail validation.
- Troubleshooting: Help developers investigate PDF-related issues more efficiently.
These improvements are particularly useful for applications that generate or process large volumes of PDF documents.
4. More Flexible Image Exporting
PDF Library 3.1 expands image export functionality, providing developers with additional options for extracting and managing images.
Images can now be exported from individual files or collections to file paths or streams.
This flexibility supports a range of document-processing scenarios.
Image Export Use Cases
- Extracting document assets: Export images from PDF documents for reuse in other application workflows.
- Stream-based processing: Export images directly to streams for further processing without requiring a file-based output at every stage.
- Document management systems: Extract and organize images as part of document management or archival workflows.
- Automated document processing: Integrate image exporting into larger workflows that process multiple PDF documents or image collections.
By supporting different export destinations, PDF Library 3.1 provides developers with more flexibility when handling PDF image content.
5. Additional Fixes and Reliability Improvements
Beyond the new features, PDF Library 3.1 includes fixes designed to improve document-processing reliability.
Improved Opacity Handling
Corrections to opacity handling address issues related to transparency when working with PDF content.
Independent PDF Manipulation
Fixes improve the handling of independent PDF manipulation operations, helping ensure more reliable document processing.
Improved Raw PDF Content Parsing
Enhancements to raw PDF content parsing address issues encountered when interpreting existing PDF content.
Together, these improvements strengthen the library's handling of PDF documents across different processing scenarios.
Upgrading to PDF Library for .NET 3.1
Developers using previous versions of Xceed PDF Library for .NET should review the changes introduced in version 3.1 before upgrading.
Two API changes deserve particular attention:
Paint Object Migration
The replacement of SolidColorBrush con RGBPaint y GrayPaint may require changes to existing code.
Validation Result Handling
Applications using PdfDocument.Validate() should account for the new PdfStandardValidationResult return type and its detailed error information.
Testing existing PDF generation, manipulation, and validation workflows is recommended before deploying the updated library to production.
PDF Library 3.1 Upgrade Checklist
- Review existing SolidColorBrush implementations and migrate to RGBPaint o GrayPaint.
- Update code that handles PdfDocument.Validate() results.
- Review the available PDF/A profiles in PdfStandardOptions.
- Test PDF/A validation against representative documents.
- Verify image exporting to file paths and streams.
- Regression-test PDF generation, transparency, manipulation, and content parsing before production deployment.
Build Better PDF Workflows with Xceed PDF Library for .NET
PDF Library for .NET 3.1 continues to improve the tools available to developers working with PDF documents in .NET applications.
With expanded PDF/A validation options, more detailed validation results, new paint classes, flexible image exporting, and additional reliability fixes, this release provides greater control over document-processing workflows.
Whether you're building document automation solutions, enterprise reporting systems, or applications that manage and validate PDF files, these enhancements can help simplify development and maintenance.
Explore PDF Library for .NET 3.1
Discover the latest improvements and evaluate how Xceed PDF Library for .NET can support your next project. Explore its PDF processing capabilities or start your free trial today.
For technical assistance, contact [email protected]. For licensing inquiries, contact [email protected].
Preguntas frecuentes
What's new in Xceed PDF Library for .NET 3.1?
Version 3.1 introduces RGBPaint y GrayPaint classes, enhanced PDF/A standards validation, additional PDF/A profiles, detailed validation error reporting, flexible image exporting to paths and streams, and reliability improvements for PDF processing.
Does PDF Library for .NET 3.1 support PDF/A validation?
Yes. The new PdfDocument.ValidatePdfStandards() method enables validation against supported PDF/A standards. Additional profiles include PDF/A-2U, PDF/A-3B, PDF/A-3U, PDF/A-4, and PDF/A-4F.
Does PDF/A validation automatically fix non-compliant documents?
No. PDF/A validation identifies potential standards-related issues, allowing developers to investigate and address them. Validation does not automatically correct document compliance problems.
What happened to SolidColorBrush in version 3.1?
En SolidColorBrush class has been replaced by RGBPaint y GrayPaint. Developers upgrading from previous versions should review existing code and migrate paint object implementations to the appropriate new class.
Can PDF Library for .NET 3.1 export images to streams?
Yes. Version 3.1 expands image exporting capabilities to support file paths and streams, making it easier to integrate image extraction into automated document-processing and management workflows.
What should developers check before upgrading to PDF Library 3.1?
Developers should review the paint class migration, update code handling PdfDocument.Validate() results, and test existing PDF generation, validation, manipulation, image exporting, and content-parsing workflows before deploying the new version.