Implemented Aspose.Words for .NET Standard 2.0 Added Feature to Set Chart Axis Properties

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Aspose.Words for .NET logoWe are pleased to announce our next version Aspose.Words for .NET 17.12. This month’s release contains over 84 useful new features, enhancements and bug fixes. Please see the release notes for more detail. If you are planning to upgrade from older version of Aspose.Words to the current version, we would strongly suggest you to check the Public API and Backward Incompatible Changes section to know what APIs are changed so far.

 

Here is a look at just a few of the biggest features and API changes in this month’s release.

  • Implemented Aspose.Words for .NET Standard 2.0.
  • Implemented API to set chart axis properties.
  • Added feature to get the docPartGallery value of StructuredDocumentTag of type SdtType.DocPartObj.
  • Horizontal and vertical flipping attributes are now taken into account when rendering DML textboxes.
  • Improved rendering of diacritics for “Courier New” font.
  • Multiline MathML expressions rendering fixed.
  • EMR_ROUNDRECT records processing while rendering metafiles fixed.
  • PDF Rendering of indexed images while converting to CMYK color space fixed.
  • Fixed bug causing freezes when converting document with DML Charts to PDF in debug x86 mode.
  • OTF(CFF) fonts to PDF/A documents export fixed.
  • DML Charts with empty area do not throw exception on rendering now.
  • Fixed scaling problem with DML bubble charts on rendering.
  • LINQ Reporting Engine supports dynamic setting of chart axes’ titles.
  • Improved handling of decimal tab alignment in cells when paragraph has hanging indent.
  • Improved text wrapping when line contains single or no characters.
  • Improved handling of cell margins and table alignment.
  • Improved cell alignment when line has trailing spaces and custom tabs.
  • Improved handling of collapsed paragraphs.
  • Fixed exception in rare case when line break point cannot be found.
  • Fixed exception when document is saved with revision balloons inside of a cell.

Included Aspose.Words for Android via Xamarin, Aspose.Words for iOS via Xamarin and Aspose.Words for Mac via Xamarin in Aspose.Words for .NET

Now, Aspose.Words for .NET includes Aspose.Words for Android via Xamarin, Aspose.Words for iOS via Xamarin and Aspose.Words for Mac via Xamarin. Following breaking changes have been made:

  • External reference to SkiaSharp has been added (in previous versions SkiaSharp was merged into Aspose.Words for Xamarin dlls)
  • Native graphics objects (Android.Graphics.Bitmap and Android.Graphics.Canvas in Aspose.Words for Android via Xamarin version and CoreGraphics.CGImage and CoreGraphics.CGContext in Aspose.Words for iOS via Xamarin and Aspose.Words for Mac via Xamarin) has been replaced in public API with SkiaSharp.SKBitmap and SkiaSharp.SKCanvas accordingly. This allowed us to fully unify public API of all Aspose.Words for Xamarin versions. Code written for one platform can be reused on another without any changes.

Implemented Aspose.Words for .NET Standard 2.0

Starting from this release, Aspose.Words for .NET includes .NET Standard 2.0 version. It has full functionality of regular .NET version of Aspose.Words with few limitations and public API difference:

  • Saving to BMP is not yet supported.
  • Signing of PDF document is not yet supported.
  • Printing feature is not provided in .NET Standard
  • Saving to user browser is not provided, i.e. Document.Save(HttpResponse,string,ContentDescription,SaveOptions) overload is not available.
  • Public API differences are the same as in Xamarin versions, i.e. SkiaSharp.SKBitmap and SkiaSharp.SKCanvas are used as native graphics objects instead of System.Drawing.Bitmap and System.Drawing.Graphics.

Implemented API to Set Chart Axis Properties

We have added public classes ChartAxis, AxisDisplayUnitAxisScaling and following enumeration in this release to allow setting chart axis properties.

Please check the examples from following documentation link.
How to Set Chart Axis Properties

Added Feature to Get the docPartGallery Value of StructuredDocumentTag of Type SdtType.DocPartObj

We have improve the behavior of following properties. Now, you can get the value of these properties for “Markup.SdtType.DocPartObj” SdtType.


public class StructuredDocumentTag
{
    .....
 
    public string BuildingBlockGallery{ get; set;}
 
    public string BuildingBlockCategory{get; set;}
 
    .....
}

Changed Return Type for FieldMergingArgsBase.Field

We have provided typed access to a merge field’s properties in this release of Aspose.Words. We have changed the return type of the FieldMergingArgsBase.Field property (and hence of the corresponding descendants’ properties) from Field to FieldMergeField. Please refer to the following article for more detail.
How to Handle Text Before and After Switches During Mail Merge Operation

/// <summary>
/// Gets the object that represents the current merge field.
/// </summary>
public FieldMergeField Field
{
    get { return mField; }
}

Aspose.Words for .NET Resources

The following resources will help you work with Aspose.Words for .NET:

    • Home page of .NET API.
    • Install using NuGet Package
    • Documentation – up-to-date documentation containing Programmer’s Guide, Knowledge Base and much more.
    • API Reference Guide – detailing the publicly exposed classes, methods, properties, constants & interfaces.
    • Aspose.Words Product Family Forum – post your technical questions and queries, or any other problem you are facing while working with Aspose.Words APIs.
    • Enable Blog Subscription – do not limit yourself, you can keep yourself updated with the latest news on Aspose.Words APIs, new features, fixes and other API related topics by subscribing to Aspose.Words blog.
    • Examples – we have published our code examples on the social coding website GitHub.com. Anyone could explore the code examples for learning purposes.
Posted in Aspose.Words Product Family | Leave a comment

Version Number Setting in QR Coded Barcode With Aspose.BarCode for SSRS 17.12

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Aspose.BarCode for SSRS We are pleased to announce the release of Aspose.BarCode for Reporting Services 17.12. The major development in this release is the support to generate QR coded barcode with setting version number.

Setting QR version Number

Aspose.BarCode for Reporting Services now enables the developers to generate QR coded barcode with setting its version number. Setting QR version number is very simple and is demonstrated in the code snippet given below. The code snippet contains comments that makes it self explanatory.


// Instantiate BarCodeBuilder object
Aspose.BarCode.BarCodeBuilder builder = new Aspose.BarCode.BarCodeBuilder();

// Set the Code text for the barcode
builder.CodeText = "ABCDEFGHIJKLMNOPQRSTUVWXYZ";

// Set the symbology type to QR
builder.EncodeType = Aspose.BarCode.Generation.EncodeTypes.QR;

// Set the error level
builder.QRErrorLevel = Aspose.BarCode.QRErrorLevel.LevelQ;

// Set the QR barcode version number
builder.QRVersion = Aspose.BarCode.QRVersion.Version10;

//Save the image
builder.Save("qr_version10_errorQ.png");

Other Improvements

This release also fixes exceptions that were reported by our valued customers. Complete list of fixes in this release is as follows.

  • Process of setting license has been improved. Now API will show correct exception message in case license subscription is expired. Setting license time has also been improved.
  • Working of Aspose.BarCode in multi threaded environment has been enhanced.
  • DatabarStacked barcode recognition process has been enhanced.

To view the complete list of new features and fixes, please visit the release notes page. This release also includes many important API and Backward Incompatible changes. The list of all such changes are worth seeing and can be view on release notes page. You can download the latest version by visiting the Aspose.BarCode for Reporting Services 17.12 page in downloads section.

Aspose.BarCode for Reporting Services Resources

The following resources will help you work with Aspose.BarCode for SSRS:

Posted in Aspose.BarCode Product Family | Leave a comment

Setting Default Font for Project Data with Aspose.Tasks for .NET 17.12

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

aspose-tasks-for-netWe are pleased to announce the release of Aspose.Tasks for .NET 17.12. This month’s release includes several improvements in terms of feature enhancements and bug fixes. Specifically, it introduces the capability of setting default font for exporting project data to PDF. For a detailed note on what is new and fixed, please visit the release notes section of API documentation.

Setting Default Font for Conversion to PDF

This month’s release includes an enhancement for setting default font during project data conversion to PDF. Setting default font during rendering of documents helps when a font is not found on the server. In such case, default font replaces the missing font and output is not affected. This can be specified using the DefaultFontName property of the PdfSaveOptions as shown in following code sample.


Project project = new Project(dataDir + "CreateProject2.mpp");
project.Set(Prj.StartDate, new DateTime(2014, 9, 22));
        
// By default project.DateFormat == DateFormat.Date_ddd_mm_dd_yy (Mon 09/22/14) customize DateFormat (September 22, 2014)
project.Set(Prj.DateFormat, DateFormat.DateMmmmDdYyyy);
project.Save(dataDir + "CustomizeDateFormats1_out.pdf", SaveFileFormat.PDF);

// Export to date format 19/07/2016
project.Set(Prj.DateFormat, DateFormat.DateDdMmYyyy);
project.Save(dataDir + "CustomizeDateFormats2_out.pdf", SaveFileFormat.PDF);

Other Improvements

This release also includes fixes for issues found with the previous version of the API. These include:

  • Project reading exceptions while loading certain Project MPP files
  • Issues with Task Duration during recalculations
  • Incorrect start and finish times of resource baseline
  • Issues with header text while rending project data
  • Font information lost for MPP file

API Resources

You may visit the following API resources for getting started and working with the API.

  • Product Documentation – Detailed API documentation with code examples and details about API functional areas
  • Aspose.Tasks Forum – Our online support forum where we address your queries and inquiries
Posted in Aspose.Tasks Product Family | Leave a comment

Set Version Of QR Encoded Barcode With Aspose.BarCode for .NET 17.12

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Aspose.Barcode for .NET We are pleased to announce the release of Aspose.Barcode for .NET 17.12. The major development in this release is the support to generate QR coded barcode with version setting. This release also supports enhanced process of recognizing Code128 and OneD coded barcode. Improved speed and quality of 1D barcode recognition process has also been incorporated in this release.

Set QR version

Aspose.BarCode supports the functionality to generate QR coded barcode with its version information. This functionality allows to generate QR coded barcode by setting its version number. A property BarCodeBuilder.QRVersion has been introduced to define the said setting. How a developer can set QR version number is demonstrated in the code snippet given below. The code snippet contains comments that makes it self explanatory.


// Instantiate BarCodeBuilder object
Aspose.BarCode.BarCodeBuilder builder = new Aspose.BarCode.BarCodeBuilder();

// Set the Code text for the barcode
builder.CodeText = "ABCDEFGHIJKLMNOPQRSTUVWXYZ";

// Set the symbology type to QR
builder.EncodeType = Aspose.BarCode.Generation.EncodeTypes.QR;

// Set the error level
builder.QRErrorLevel = Aspose.BarCode.QRErrorLevel.LevelQ;

// Set the QR barcode version number
builder.QRVersion = Aspose.BarCode.QRVersion.Version10;

//Save the image
builder.Save("qr_version10_errorQ.png");

Other Improvements

This release also fixes exceptions that were reported by our valued customers. Complete list of fixes in this release is as follows.

  • Process of setting license has been improved. Now API will show correct exception message in case license subscription is expired. Setting license time has also been improved.
  • Working of Aspose.BarCode in multi threaded environment has been enhanced.
  • DatabarStacked barcode recognition process has been enhanced.
  • Process of recognizing barcode from JPEG and TIFF image has been improved.
  • Functionality to generate Datamatrix barcode has been updated.
  • Process to recognize PDF417 and Code128 barcode has been enhanced. Performance improvements have been made to boost up the process.

To view a complete list of enhancements and fixes, please visit the release notes page. This release also includes many important API and Backward Incompatible changes. The list of all such changes are worth seeing and can be view on release notes page. You can download the latest version by visiting the Aspose.Barcode for .NET 17.12 page in downloads section.

Aspose.BarCode for .NET Resources

You can get started with Aspose.BarCode for .NET by making use of information available in the following:

Posted in Aspose.BarCode Product Family | Leave a comment

Z-Index Positioning Algorithms and Inter File Format Conversion

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

We at Aspose are pleased to announce new version of Aspose.Html for .NET. As per regular monthly update process, Aspose.Html for .NET 17.12 is available on NuGet for download. In this version of the API, we have made significant improvements to the processing of CSS styles and HTML to PDF conversion feature. Furthermore, we have also made some internal bug fixes and enhancements, related to z-index and page splitting algorithms. An overview of the improvements and changes is given in the release notes of Aspose.Html for .NET 17.12.

According to z-index positioning specifications, z-index specifies the stack level of the box in the current stacking context as well as whether the box establishes a stacking context. In Aspose.Html for .NET 17.12, we have improved z-index positioning algorithms so setting position property of an element to “absolute” value will place the element correctly without an overlapping of content.

Since the inter file format conversion has been the most attractive feature of the APIs offered by Aspose, we have fixed some internal bugs related to formatting in HTML to PDF/XPS conversion(s). In previous version(s) of Aspose.Html for .NET, it was observed while converting HTML into PDF/XPS, that the resultant PDF/XPS file(s) used to have some formatting issues. These issues were identified as miscalculation of Colspan width with incorrect processing of CSS styles and have been fixed in Aspose.Html for .NET 17.12.

Miscellaneous Resources

Please visit the following links for information regarding Aspose.Html for .NET 17.12 and Release Notes section.

Posted in Asad Ali, Aspose.Html Product Family | Leave a comment

Improved Memory usage in Multithreaded Environment and Text Manipulation

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

We always aspire to deliver an API with enhancements and improvements and our product team has been working hard to implement new features as well as improving performance of the API. We are pleased to announce that Aspose.Pdf for Java 17.11 is available for download with exciting features and improvements. Please visit release notes of Aspose.Pdf for Java 17.11 for an overview of public API changes and improvements. However, please check following major improvements regarding memory usage and text manipulations in the new release of the API.

Memory Usage in Multithreaded Environment

In the previous version(s) of the API, the API used to raise an exception when the heap memory occupation was close to the limit. It has specifically been observed while converting PDF documents with a HOCR callback in multithreaded environments. The product team has been working on implementing functionality to extract images from PDF in the raw format, so the memory consumption was decreased to significant level. The existing method to convert PDF with HOCR callback has been improved as follows:

pdf.convert(callback, false, true);

In the above line of code, the first boolean parameter notifies that searchable text should be invisible with the false value – whereas the second boolean parameter is used to notify that the internal images should be returned as they are, with the true value. This enhancement in the convert() method has brought a significant improvement in the memory consumption and it also has been tested that using this approach, program has become faster twice than with the previous method.

Identify Underline Text and improved Replacement options

It was observed during replacing/removing underline text from PDF documents, that text was used to be replaced/removed but the underline stayed drawn. We have implemented mechanism that starts a searching for text underlining in the source document on any text edit operation. TextFragmentAbsorber removes the underline from text, where underline is not the part of actual text but a graphical element and replace it with original underline like it is added through TextState of the original TextFragment.

After that, any text edit operation will be performed with an affected fragment (or segment) in the same way if it was underlined by using TextState.Underline property of TextFragment (or TextSragment). In order to enable the described mechanism you can set ToAttemptGetUnderlineFromSource to ‘true’ in TextEditOptions option of TextFragmentAbsorber (or PdfContentEditor) object.

Miscellaneous fixes

As it always recommended to use latest release of our API’s as they include latest features / improvements and fixes related to issues reported in earlier released versions. Therefore, please download the latest release of Aspose.Pdf for Java 17.11.

Posted in Aspose.Pdf Product Family, Asad Ali | Leave a comment

First version of Aspose.Cells for JavaScript via Java released

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

We are pleased to announce the first public release of Aspose.Cells for JavaScript via Java (17.11). The new API incorporates MS Excel data processing and rendering functionalities in JavaScript (the most commonly used client-side scripting language). Aspose.Cells for JavaScript via Java has full functionality of Aspose.Cells for Java with a few limitations, minor API changes and additional requirements. See the following release notes on major features for your reference.
Aspose.Cells for JavaScript via Java 17.11 release notes

Aspose.Cells for JavaScript is a subset component that includes all the important and useful features present in its native Aspose.Cells for Java. Aspose.Cells for JavaScript is equally robust and feature rich component. It supports high-fidelity file format conversions to and from XLS, XLSX, XLSM, SpreadsheetML, CSV, Tab Delimited, HTML, MHTML and OpenDocument Spreadsheet in JavaScript. The developers will have full programmatic access through a rich APIs set to all MS Excel document objects and formattings that allows to create, modify, extract, copy, merge, and replace spreadsheet content. With Aspose.Cells for JavaScript via Java, developers can export data, format spreadsheets to the most granular level, create, manipulate and render charts, apply and calculate complex formulas efficiently and much more. All you need to do is install Node.js SDK for your specific platform and setup node-java bridge, see Setup environment and Installation guidelines.
Learn more about Aspose.Cells for JavaScript via Java

Aspose.Cells for JavaScript via Java Resources

Following are the links to some useful resources you may need to accomplish your tasks.

Posted in Aspose.Cells Product Family | Leave a comment

Segments Per Row Setting For Databar Barcode With Aspose.BarCode for Java 17.11

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Aspose.BarCode for Java Aspose.BarCode for Java 17.11 is available for download now. The major development in this release is the support to generate databar coded barcode with segments per row. Enhanced functionality to read barcode from PDF has also been incorporated in this release.

Generating Segments Per Row For Databar Barcode

Aspose.BarCode for Java now supports the functionality to generate segments per row databar encoded barcode. This functionality allows the developers to adjust the amount of information per (each) row in the barcode. A property BarCodeBuilder.setColumns has been introduced to define the said setting. How a developer can set segments per row for a databar is demonstrated in the code snippet given below. The code snippet contains comments that makes it self explanatory.


//Instantiate BarCodeBuilder object
com.aspose.barcode.BarCodeBuilder builder = new com.aspose.barcode.BarCodeBuilder();

//Set the Code text for the barcode
builder.setCodeText("(01)98898765432106(3202)012345(15)991231"); 

//Set the symbology type to Code128
builder.setEncodeType(com.aspose.barcode.EncodeTypes.DATABAR_EXPANDED_STACKED);

//Set the cloumn property to define segments per row
builder.setColumns(6);

//Save the image
builder.save("6segmets.png");

Other Improvements

Following is the list of improvements made in this release and bug fixes that were reported by our valued customers.

  • Functionality to recognize barcode from image has been enhanced. The functionality has been enhanced in such a way that API will extract exact number of available barcodes. No unwanted barcodes.
  • The process to extract supplement barcode has been improved. Aspose.BarCode now look for special parity pattern for correct recognition of supplement barcode.
  • DataMatrix barcode recognition process from a TIFF image has been improved. Aspose.BarCode returns all DataMatrix barcode if RecognitionMode.MaxQuality recognition mode is used.
  • Barcode recognition process have been enhanced to detect barcodes from PDF files.

To view a complete list of enhancements and fixes, please visit the release notes page.

Aspose.BarCode for Java Resources

The following API resources can be of help to you in getting started with Aspose.BarCode:

Posted in Aspose.BarCode Product Family | Leave a comment

Query Cell Areas Mapped to XmlMap Path, Render Limited No Of Sequential Pages and Ignore Errors while Rendering Excel to PDF with Aspose.Cells for Java 17.11

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Aspose.Cells for JavaWe are pleased to announce the release of Aspose.Cells for Java 17.11. This release includes many new features and enhancements along with some critical bug fixes that further improve the overall stability of the APIs. We also recommend our clients to use the powerful Aspose for Java APIs directly in their Maven Projects with simple configurations. Please check the release notes in order to get an idea about what is new and what has been fixed with this revision of Aspose.Cells for Java. Here is a look at the major features in this release.

Find the root element name of Xml Map

Aspose.Cells allows you to find the root element name of XML map using XmlMap.RootElementName property. For more detail, please see this article.

Query Cell Areas Mapped to Xml Map Path

You can query cell areas mapped to xml map path with Aspose.Cells using the Worksheet.xmlMapQuery() method. If the path exists, it will return the list of cell areas related to that path inside xml map. The first parameter of Worksheet.xmlMapQuery() method specifies the xml element path and the second parameter specifies the xml map you want to query.

The following sample code queries the xml map two times and prints the list of cell areas returned by the Worksheet.xmlMapQuery() method on console.

//Load sample Excel file having Xml Map
Workbook wb = new Workbook(dirPath + "sampleXmlMapQuery.xlsx");

//Access first XML Map
XmlMap xmap = wb.getWorksheets().getXmlMaps().get(0);

//Access first worksheet
Worksheet ws = wb.getWorksheets().get(0);

//Query Xml Map from Path - /MiscData
System.out.println("Query Xml Map from Path - /MiscData");
ArrayList ret = ws.xmlMapQuery("/MiscData", xmap);

//Print returned ArrayList values
for (int i = 0; i < ret.size(); i++)
{
    System.out.println(ret.get(i));
}

System.out.println("");

//Query Xml Map from Path - /MiscData/row/Color
System.out.println("Query Xml Map from Path - /MiscData/row/Color");
ret = ws.xmlMapQuery("/MiscData/row/Color", xmap);

//Print returned ArrayList values
for (int i = 0; i < ret.size(); i++)
{
    System.out.println(ret.get(i));
}

Determine Smart Art Shape and Convert it to Group Shape

Smart Art shapes are special shapes that allow you create complex diagrams automatically. Aspose.Cells allows you to detect Smart Art shapes and convert them to Group shape that enables you to handle smart art shape like a group shape. Consequently, you will have access to the individual parts or shapes of the group shape.

Create and Protect a Shared Workbook

Microsoft Excel allows you to create a shared workbook. When you share the workbook, then more than one user can edit the workbook. Aspose.Cells enables you to create a shared workbook with Workbook.Settings.Shared property. Besides, you can protect or unprotect a shared workbook.

Render Sequence of Pages using PageIndex and PageCount Properties of ImageOrPrintOptions

Aspose.Cells allows you to render sequence of pages of your Excel file to images using ImageOrPrintOptions.PageIndex and ImageOrPrintOptions.PageCount properties. These properties are useful when there are so many pages in your worksheet but you need to render a few pages only. This will not only save the processing time but also saves the memory consumption of the rendering process.

Ignore Errors while Rendering Excel to PDF

You can ignore all errors during the conversion process using the PdfSaveOptions.IgnoreError property. This way, conversion process will be completed smoothly without throwing any error or exception but data loss may occur.

Aspose.Cells for Java Resources

The resources, you may need to accomplish your tasks:

Posted in Aspose.Cells Product Family, Muhammad Shakeel Faiz | Leave a comment

Support for Extended Attributes Manipulation using Aspose.Email for Java

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

aspose-email-for-javaWe are pleased to announce the release of Aspose.Email for Java 17.11. This release introduces a new feature of working with Extended attributes of messages using API’s Exchange Web Service (EWS) client. In addition, it also brings several fixes to other functionality of the API that further stabilizes the overall behavior of the API in terms of expected behavior. For a complete list of what is new and fixed, please visit the release notes section of API documentation.

Working with Extended Attributes of Message using EWS

This version of Aspose.Email for Java provides the capability to work with Extended Attributes of messages using the API’s EWS client. Extended attributes can be added to message in the same way as adding Named properties to messages. The API now has FetchMapiMessage method that allows to retrieve a message from Exchange server along with such properties associated with it. This is as shown in the following sample code.

//Create a new Property
PidNamePropertyDescriptor pd = new PidNamePropertyDescriptor(
    "MyTestProp",
    PropertyDataType.String,
    UUID.fromString("00020329-0000-0000-C000-000000000046"));
String value = "MyTestPropValue";

//Create a message
MapiMessage message = new MapiMessage(
    "from@domain.com",
    "to@domain.com",
    "EMAILNET-38844 - " + UUID.randomUUID().toString(),
    "EMAILNET-38844 EWS: Support for create, retrieve and update Extended Attributes for Emails");

//Set property on the message
message.setProperty(pd, value);

//append the message to server
String uri = client.appendMessage(message);

//Fetch the message from server
MapiMessage mapiMessage = client.fetchMapiMessage(uri, Arrays.asList(new PropertyDescriptor[] { pd }));

//Retrieve the property from the message
String fetchedValue = mapiMessage.getNamedProperties().get_Item(pd).getString();

Other Improvements

In addition to new feature, this release of API also includes several improvements in terms of bug fixes. This further adds to the overall stability of the API in terms of expected output.

API Resources

We have detailed information available online for getting started with the Aspose.Email for Java API. These are:

Posted in Aspose.Email Product Family | Leave a comment