Convert PDF File to Word Document and Save Word to PCL (Printer Control Language) Format using Aspose.Words for Cloud 17.7

Aspose.Words for Cloud, a cloud-based document creation, manipulation and conversion API, helps you process documents with its many flexible features. You can perform a wide variety of document operations with Aspose.Words for Cloud’s REST API. Create a new document from scratch, modify an existing document, convert documents to different formats, and render the document to images.

Aspose.Words for Cloud’s platform independent document manipulation API is a true REST API that can be used with any language: .NET, Java, PHP, Ruby, Rails, Python, jQuery and many more. You can use it with any platform — web, desktop, mobile, and cloud. The API integrates with other cloud services to give you the flexibility you need when processing documents. It is suitable for any type of business, document, or content. Learn more about Aspose.Words for Cloud

We are pleased to announce the release of Aspose.Words for Cloud 17.7. This release contains a couple of new features, two bug fixes and two enhancements to Aspose.Words for Cloud. Aspose.Words core library has also been updated to version 17.7. You can find the list of features and bug fixes in the following link:

Aspose.Words for Cloud 17.7

Convert PDF to Word Formats

Aspose.Words for Cloud now allows you to convert PDF file to DOCX or DOC or to any desired supported Microsoft Word format. A conversion that many of our customers have requested is PDF to DOC or DOCX or converting a PDF file to a Microsoft Word document. Customers want this because PDF files cannot easily be edited, whereas Word documents can. Aspose.Words for Cloud can now work with PDF documents, converting them to desired format (when using convert call) or DOCX format (when using all other API calls). The request body and parameters do not differ in case of specifying input file as PDF or DOC/DOCX, making user experience consistent. As such, using PDF documents in Aspose.Words for Cloud allows to:

  • Convert PDF to DOC/DOCX format
  • Use Words API on PDF document, e.g. count number of words or get/update/delete specified paragraph

Please refer to the following article for more details:
Use Aspose.Words for Cloud API to work with PDF Documents

New Features and Enhancements

  • WORDSCLOUD-206: We have provided functionality to convert PDF document to DOCX, DOC or to any desired Microsoft Word format.
  • WORDSCLOUD-201: You can use Aspose.Words for Cloud to convert the document in the PCL (Printer Control Language) format. 

  • WORDSCLOUD-202: We have added “DisplayDocTitle” to the PdfSaveOptions class.

    DisplayDocTitle: This flag specifies whether the window’s title bar should display the document title taken from the Title entry of the document information dictionary. If false, the title bar should instead display the name of the PDF file containing the document. The default value is false.

  • WORDSCLOUD-191:  We have implemented form fields methods cleanup.

    Aspose for Cloud Resources

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

    Start a Free Trial Today

    Start a free trial today – all you need is to sign up with the Aspose for Cloud service. Once you have signed up, you are ready to try the powerful file processing features offered by Aspose for Cloud.

    Posted in Aspose.Words Product Family | Leave a comment

    Get Comment Replies, Mark Comment as Done, Sign Signature Line by using Aspose.Words for Android via Xamarin 17.8

    Aspose.Words for Android via Xamarin

    We are pleased to announce the new monthly release of Aspose.Words for Android via Xamarin 17.8. ‘Aspose.Words for Android via Xamarin’ has full functionality of Aspose.Words for .NET with few limitations, minor API changes and additional requirements. This version also includes all bug fixes and public API changes made in Aspose.Words for .NET 17.8, see following release notes for more information.

    Major fixes and improvements made in this ‘Aspose.Words for Android via Xamarin’ release are as follows:

    • A significant optimization of PDF rendering engine has been carried out.
    • Compression of document structure data and cross-reference table in PDF 1.5 output. Now the output PDF documents with the logical structure are much smaller.
    • Image tag in Fixed HTML documents can now contain an alternative text string.
    • API for ‘Mark Comment Done’ option.
    • Sign the signature line in Word document.
    • Add feature to set/get “Specify line and character grid”.
    • Detect comment resolved and comment replies and reply to which comment.
    • Added feature to format Data Labels of chart.

    ‘Aspose.Words for Android via Xamarin’ is an advanced Word document processing API to perform a wide range of document processing tasks directly within your native Android applications. You can integrate this API through Xamarin framework for Android applications. ‘Aspose.Words for Android via Xamarin’ API supports DOC, OOXML, RTF, HTML, OpenDocument, PDF, XPS, EPUB and other formats. You can generate, modify, convert and render documents.
    Learn more about Aspose.Words for Android via Xamarin

    ‘Aspose.Words for Android via Xamarin’ API Resources

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

    Start a Free Trial Today

    Start a free trial today – all you need is to sign up with Aspose. Once you have signed up, you are ready to try all the powerful file processing features offered by Aspose.

    You can easily download ‘Aspose.Words for Android via Xamarin’ API for evaluation. The evaluation download is the same as the purchased download. The evaluation version simply becomes licensed when you add a few lines of code to apply the license.

    The evaluation version of ‘Aspose.Words for Android via Xamarin’ (without a license specified) provides full product functionality, but it inserts an evaluation watermark at the top of the document on open and save, and limits the maximum document size to several hundred paragraphs.

    If you want to test ‘Aspose.Words for Android via Xamarin’ API without the evaluation version limitations, you can also request a 30-day Temporary License. Please refer to How to get a Temporary License?

    Posted in Aspose.Words Product Family | Leave a comment

    Get Minimum Required Hight And Width for A BarCode Image With Aspose.BarCode for JasperReports 17.7

    Aspose.BarCode for JasperReports We are pleased to announce the release of Aspose.BarCode for JasperReports 17.7. The major development in this release is the functionality to get the minimun size (height & width) required for the barcode image. Improved functionality of GetOnlyBarCodeImage method has also been incorporated in this release.

    Functionality of DataMatrix barcode has also been enhanced in this release. Aspose.BarCode for JasperReports now enables the developer to create DataMatrix barcode with C40 and Text encoding scheme.

    Enhancements

    Complete list of enhancements and fixes in this release is as follows.

    • Barcode recognition process has been improved. It is now reading DataMatrix and UPCA coded barcode correctly.
    • Barcode recognition process has been improved. It is now reading correct barcode from PDF.
    • Barcode generation process has been improved. API now validates the input text string for GS1 coded barcode and then generated the barcode image.
    • Functionality of ExportToXml method has been improved. It is now exporting dimensions of the barcode along with other attributes in the XML file.
    • Targets detection process for QR coded barcode has been improved.
    • Recognition process was recognizing EAN13 coded barcode as UPC-A. An enhancemnet has been made in the algorithm to correctly recognizing EAN13 coded barcode.
    • Functionality of GetOnlyBarCodeImage method has been improved. The working of GetOnlyBarCodeImage method with small size has been enhanced.
    • Functionality to recognize the supplement code text from EAN13 coded barcode has been improved.

    To view a complete list of new features, fixes and to download the latest release, please visit Aspose.Barcode for JasperReport 17.3 page in downloads section.

    Aspose.BarCode for JasperReports Resources

    The following API resources can be of help to you in getting started:

    Posted in Aspose.BarCode Product Family | Leave a comment

    Meet speakers from Google at the Auckland .NET user group

    The Auckland .NET user group is a bi-monthly meetup of around 60-100 different members each month. Topics discussed included e topics include any part of the .NET framework, web technology or Windows apps.

    Aspose is sponsoring a very special meetup at the Auckland .NET user group two speakers from Google are coming in for a chat. 

    • Mete Atamel will speak about Building ASP.NET apps on Google Cloud
    • Felipe Hoffa will talk about what can we learn from 750 billion GitHub events and 42 TB of code.
    We recommend if you are in in the neighborhood to go check them out for an interesting talk.

    Where and When?

    • GridAKL Offices, Auckland
    • 101 Pakenham Street West, Wynyard Quarter
    • August 21 2017, 6:30-9:00 pm

    Press Contact

    Web: www.aspose.com

    Telephone (Australia): +61 2 8006 6987

    Posted in Developer Community Support | Leave a comment

    Support for Exchange Server 2016 with Aspose.Email for Android via Xamarin

    Aspose.Email for Android via Xamarin 17.8 is now available for download. This monthly release of the API brings all the latest improvements in Aspose.Email for .NET API to Xamarin platform. Specifically, it provides the capability of converting email messages to HTML without embedding resources. For a detailed note on what is new and fixed, please visit the release notes section of API documentation.

    Major Improvements

    This latest version of the API not only includes enhancements from the equivalent .NET version of the API, but also contains all the bug fixes that were part of the .NET API. This keeps the Android API updated with the latest changes that are part of the parent .NET API. As mentioned earlier, we’ll be publishing monthly releases of this new API from now onwards to keep it abreast the .NET equivalent version.

    Exporting Messages to HTML without Embedding Resources: Aspose.Email for iOS now supports converting messages to HTML  without embedding resources in output file. This allows users the classical approach of saving resource files along with source HTML file. The SaveResourceHandler provided with HtmlSaveOptions lets you achieve this by specifying the path to save the resources of the message. This is as shown in the code sample below.

    MailMessage msg = MailMessage.Load(filePath);
    var outFileName = Path.Combine(dataDir, fileName + ".html");
    
    var options = new HtmlSaveOptions()
    {
        EmbedResources = false,
        SaveResourceHandler =
            (AttachmentBase attachment, out string resourcePath) =>
            {
                attachment.Save(Path.Combine(dataDir, attachment.ContentId));
                resourcePath = Path.Combine(".", attachment.ContentId);
            }
    };
    
    msg.Save(outFileName, options);
    

    Support for Exchange Server 2016: As part of transition from Aspose.Email for .NET, Android application developers can now use this API to provide support for Exchange server 2016 in their emailing applications. This is a worthy feature as even modern emailing services like Outlook 365 have shifted to Exchange Server 2016. Thus, you can right away empower your Android application with support of Outlook 365 using our API.

    Other Improvements

    The API also contains several fixes that further improve the API functionality as per the expected behavior. Details about such fixes are part of the release notes section for reference.

    API Resources

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

    Posted in Aspose.Email Product Family | Leave a comment

    Get hyperlink associated with image and stable inter file format conversion with Aspose.Pdf for Java 17.7

    A new release version Aspose.Pdf for Java 17.7 has been added to portfolio of Aspose.Pdf product family. This release offers a feature to Get hyperlink associated with image file, perform PDF files creation and manipulation with great stability. In this release, we have also improved the PDF form manipulation and the Flatten form fields feature is specifically improved. Furthermore, as a regular monthly release process, this version also includes fixes for issues reported in earlier release versions.

    Get hyperlink associated with image in PDF file

    Aspose.Pdf for Java supports the feature to Add Image in existing PDF document and also the feature to Add Hyperlink to PDF document. However there can be a scenario where an image already present inside PDF document points to a web URL and you may have a requirement to get hyperlink associated with image. Please note that links are represented as annotations in a PDF file and they can be added, updated or deleted. Furthermore, Aspose.Pdf for Java also supports getting the destination (URL) of hyperlink in a PDF file so in order to accomplish above mentioned requirement, we need to first search the images inside PDF document using following code snippet and then use the extracted rectangular coordinates to get the URL of LinkAnnotation from specific region.

    // Open document
     Document doc = new Document("D:\\Tests\\input.pdf");
     // Create ImagePlacementAbsorber object to perform image placement search
     ImagePlacementAbsorber abs = new ImagePlacementAbsorber();
     // Accept the absorber for first page
     doc.getPages().get_Item(1).accept(abs);
     // Display image placement properties for all placements
     for (ImagePlacement imagePlacement : (Iterable)abs.getImagePlacements())
     {     
         System.out.println("image width:" + imagePlacement.getRectangle().getWidth());
         System.out.println("image height:" + imagePlacement.getRectangle().getHeight());
         System.out.println("image LLX:" + imagePlacement.getRectangle().getLLX());
         System.out.println("image LLY:" + imagePlacement.getRectangle().getLLY());
         System.out.println("image horizontal resolution:" + imagePlacement.getResolution().getX());
         System.out.println("image vertical resolution:" + imagePlacement.getResolution().getY());
     }
    

    Stable inter-file format conversion

    In this release, we have specifically improved the inter file format conversion features, so PDF to DOC, PDF to PPTX, PDF to HTML and PDF to PDF/A have become more stable and robust as compared to earlier release versions. Some customers also reported incorrect rendering of Chinese text/content when PDF file is converted to HTML format. In some scenarios, the colors of images are also lost during PDF to HTML conversion and these scenarios are also fixed.

    Miscellaneous fixes

    As mentioned above, the tabular text alignment in resultant PPTX, missing notes in rendered PPTX, overlapping of text on table border during PDF to HTML conversion, splitting of text to multiple lines during PDF to PPTX conversion are also resolved. As it is always recommended to use latest release of our API’s, so we suggest you to please download the latest release of Aspose.Pdf for Java 17.7 and check Release Notes section regarding list of issues fixed in Aspose.Pdf for Java 17.7

    Posted in Aspose.Pdf Product Family, Nayyer Shahbaz | Leave a comment

    Aspose.Email for Android via Java has been upgraded!

    aspose-email-for-android-via-javaWe are pleased to announce the release of Aspose.Email for Android via Java 17.8. After the renaming of the API from Aspose.Email for Android to Aspose.Email for Android via Java, this is the first monthly release of the API that we will publish now every month. You can refer to the release notes section of API documentation for getting an idea about the changes included in this month’s release.

    Upgradation to the Latest Version of Aspose.Email for Java

     Aspose.Email for Andorid via Java API is powered by Aspose.Email for Java API at its back. The renaming of this API was meant for a strong reason where we intended to bring it at par with the latest version of Aspose.Email for Java. This month’s release now achieves that goal where the API is at par with respective Java API other than than support for protocols section. Thus, the API now provides all the latest functionality and improvements that are part of the Java API.

    API Differences and Limitations

    Aspose.Email for Android via Java has some limitations as compared to Aspose.Email for Java API. The API doesn’t support protocols, including:

    • SMTP
    • IMAP
    • POP3
    • Exchange Server (WebDav as well as EWS)

    Other than these, the API provides all the functionality that is part of Aspose.Email for Java. These include:

    • Working with Mime and Outlook Messages
    • Manipulating message attachements
    • Support for Microsoft OST and PST file formats
    • Working with TNEF messages
    • Conversion of messages to a number of formats including HTML, MSG, EML, EMLx, MHTML
    • Working with Outlook Contacts, Notes, Distribution items, Tasks and Calendar Items

    API Resources

    You can refer to Aspose.Email for Java API for consulting documentation, code samples and API reference guide. The API documentation has been updated for this purpose with relevant links are also mentioned as follow.

    Posted in Aspose.Email Product Family | Leave a comment

    Support of Signing Document, Set Lines per Page, Characters per Line, and Comment Reply

    Aspose.Words for .NET logoWe are pleased to announce our next version Aspose.Words for .NET 17.8. This month’s release contains over 85 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.

    • A significant optimization of PDF rendering engine has been carried out.
    • Compression of document structure data and cross-reference table in PDF 1.5 output. Now the output PDF documents with the logical structure are much smaller.
    • Image tag in Fixed HTML documents can now contain an alternative text string.
    • API for ‘Mark Comment Done’ option.
    • Sign the signature line in Word document.
    • Add feature to set/get “Specify line and character grid”.
    • Detect comment resolved and comment replies and reply to which comment.
    • Added feature to format Data Labels of chart.

    Added Public Properties into PageSetup Class Allowing to Define Document Grid

    We have added new feature in Aspose.Words for .NET 17.8 to control behavior of document grid. The LayoutMode, CharactersPerLine, and LinesPerPage properties have added into PageSetup class. Now, you can set and get the number of characters per line and number of lines per page in the document grid.
    PageSetup.LayoutMode property has added to get or set the layout mode of a section. Please refer to the following article for more detail:
    Set Lines per Page and Number of Characters per Line

    /// <summary>
    /// Gets or sets the layout mode of this section.
    /// </summary>
    public SectionLayoutMode LayoutMode { get; set; }
     
    /// <summary>
    /// Gets or sets the number of characters per line in the document grid.
    /// </summary>
    /// <remarks>
    /// Minimum value of the property is 1. Maximum value depends on page width and font 
    /// size of the Normal style. Minimum character pitch is 90 percent of the font size.
    /// For example, maximum number of characters per line of a Letter page with one-inch margins is 43. /// By default, the property has a value, on which character pitch equals to font size
    /// of the Normal style. /// </remarks> public int CharactersPerLine { get; set; } /// <summary> /// Gets or sets the number of lines per page in the document grid. /// </summary> /// <remarks> /// Minimum value of the property is 1. Maximum value depends on page height and font size
    /// of the Normal style. Minimum line pitch is 136 percent of the font size.
    /// For example, maximum number of lines per page of a Letter page with one-inch margins is 39. /// By default, the property has a value, on which line pitch is in 1.5 times greater
    /// than font size of the Normal style. /// </remarks> public int LinesPerPage { get; set; }

    Following public Enum has been added in Aspose.Words 17.8.

    /// <summary>
    /// Specifies the layout mode for a section allowing to define the 
    /// document grid behavior. /// </summary> public enum SectionLayoutMode { /// <summary> /// Specifies that no document grid shall be applied to the contents of the
    /// corresponding section in the document. /// </summary> Default, /// <summary> /// Specifies that the corresponding section shall have both the additional line
    /// pitch and character pitch added to /// each line and character within it in order to maintain a specific number of
    /// lines per page and characters per line. /// Characters will not be automatically aligned with grid lines on typing. /// </summary> Grid, /// <summary> /// Specifies that the corresponding section shall have additional line pitch
    /// added to each line within it in order /// to maintain the specified number of lines per page. /// </summary> LineGrid, /// <summary> /// Specifies that the corresponding section shall have both the additional line
    /// pitch and character pitch added to /// each line and character within it in order to maintain a specific number of
    /// lines per page and characters per line. /// Characters will be automatically aligned with grid lines on typing. /// </summary> SnapToChars }

    Note : The Document Grid tab becomes visible in the Page Setup dialog of MS Word if any Asian language is defined as editing language.

    Detect Comment Resolved and Comment Replies and Reply to Which Comment

    We have added read-only public API to get extended comment properties.  You can read the comment and resolve it. Comment.Replies property returns a collection of Comment objects that are immediate children of the specified comment. Please refer to the following article:
    How to Read Comment’s Reply
    Following methods have added to the Comment class.

    // Returns the parent Comment object. Returns null for top-level comments.
    public Comment Ancestor
     
    // Returns a collection of  objects that are immediate children of the specified comment.
    public CommentCollection Replies
     
    // Gets or sets flag indicating that the comment has been marked done.
    public bool Done

    DistanceLeft, DistanceRight, DistanceTop, DistanceBottom Properties Added in Table Class

    A new feature has added in Aspose.Words 17.8 to get the distance between table and its surrounding text when text Wrapping of table is “Around”. Please refer to the following article:
    Get Distance between Table and Surrounding Text

    // Gets distance between table left and the surrounding text, in points.
    public double DistanceLeft
     
    // Gets distance between table right and the surrounding text, in points.
    public double DistanceRight
     
    // Gets distance between table top and the surrounding text, in points.
    public double DistanceTop
     
    // Gets distance between table bottom and the surrounding text, in points.
    public double DistanceBottom

    Compression of Document Structure Data and Cross-Reference Table in PDF 1.5 Output

    Now document structure data and cross-reference table are compressed when saving to PDF 1.5. This changes do not affect PDF/A-1 output due to limitations in specification.

    Added Public Property ChartDataLabel.NumberFormat

    We have added new feature in Aspose.Words for .NET 17.8 to format chart’s data label. Please refer to the following article:
    How to Format Number of Chart Data Label

    /// Returns number format of the parent element.
    public ChartNumberFormat NumberFormat

    ChartNumberFormat class represents number formatting of the parent element and contains the following public properties

    
    /// <summary>
    /// Gets or sets the format code applied to a data label.
    /// </summary>
    /// <remarks>
    /// Number formatting is used to change the way a value appears in data label and can be used in some very creative ways.
    /// The examples of number formats:
    /// <para>Number - "#,##0.00"</para>
    /// <para>Currency - "\"$\"#,##0.00"</para>
    /// <para>Time - "\[$-x-systime\]h:mm:ss AM/PM"</para>
    /// <para>Date - "d/mm/yyyy"</para>
    /// <para>Percentage - "0.00%"</para>
    /// <para>Fraction - "# ?/?"</para>
    /// <para>Scientific - "0.00E+00"</para>
    /// <para>Text - "@"</para>
    /// <para>Accounting - "_-\"$\"\* #,##0.00_-;-\"$\"\* #,##0.00_-;_-\"$\"\* \"-\"??_-;_-@_-"</para>
    /// <para>Custom with color - "\[Red\]-#,##0.0"</para>
    /// </remarks>
    public string FormatCode
    
    /// <summary>
    /// Specifies whether the format code is linked to a source cell.
    /// Default is true.
    /// </summary>
    /// <remarks>The NumberFormat will be reset to general if format code is linked to source.</remarks>
    public bool IsLinkedToSource
    

    Implemented Signing Signature Line in Word Documents

    We have added new feature in Aspose.Words 17.8 to sign signature line in Word document. Please read following article:
    Signing Word Documents

    Please check the following API changes.

    1. Added new public property for SignatureLine class:

    
    /// <summary>
    /// Gets or sets identifier for this signature line.
    /// <p>This identifier can be associated with a digital signature, when signing document using <see cref="DigitalSignatureUtil"/>.
    /// This value must be unique and by default it is randomly generated with <see cref="Guid.NewGuid"/>.</p>
    /// </summary>
    public Guid Id

    2. Added new public class SignOptions:

    /// <summary>
    /// Allows to specify options for document signing.
    /// </summary>
    public class SignOptions

    It has the following public properties:

    
    /// <summary>
    /// Specifies comments on the digital signature.
    /// Default value is <see cref="string.Empty"/>.
    /// </summary>
    public string Comments
     
    /// <summary>
    /// The date of signing.
    /// Default value is <see cref="DateTime.Now"/>.
    /// </summary>
    public DateTime SignTime
     
    /// <summary>
    /// Signature line identifier.
    /// Default value is <see cref="Guid.Empty"/>.
    /// </summary>
    /// <remarks>
    /// When set, it associates <see cref="SignatureLine"/> with corresponding <see cref="DigitalSignature"/>.
    /// </remarks>
    public Guid SignatureLineId
     
    /// <summary>
    /// The image that will be shown in associated <see cref="SignatureLine"/>.
    /// Default value is <c>null</c>.
    /// </summary>
    public byte[] SignatureLineImage
     
    /// <summary>
    /// The password to decrypt source document.
    /// Default value is <see cref="string.Empty"/>.
    /// </summary>
    /// <remarks>
    /// If OOXML document is encrypted, you should provide decryption password
    /// to decrypt source document before it will be signed.
    /// This is not required for documents in binary DOC format.
    /// </remarks>
    public string DecryptionPassword
    

    3. New public methods are introduced in DigitalSignatureUtil class for signing documents:

    
    /// <summary>
     /// Signs source document using given <see cref="CertificateHolder"/> and <see cref="SignOptions"/>
     /// with digital signature and writes signed document to destination stream.
     /// <p>Document should be either <see cref="LoadFormat.Doc"/> or <see cref="LoadFormat.Docx"/>.</p>
     /// <p><b>Output will be written to the start of stream and stream size will be updated with content length.</b></p>
     /// </summary>
     /// <param name="srcStream">The stream which contains the document to sign.</param>
     /// <param name="dstStream">The stream that signed document will be written to.</param>
     /// <param name="certHolder"><see cref="CertificateHolder"/> object with certificate that used to sign file.
     /// <ms>The certificate in holder MUST contain private keys and have the X509KeyStorageFlags.Exportable flag set.</ms></param>
     /// <param name="signOptions"><see cref="SignOptions"/> object with various signing options.</param>
     public static void Sign(Stream srcStream, Stream dstStream, CertificateHolder certHolder, SignOptions signOptions)
     
    /// <summary>
    /// Signs source document using given <see cref="CertificateHolder"/> and <see cref="SignOptions"/>
    /// with digital signature and writes signed document to destination file.
    /// <p>Document should be either <see cref="LoadFormat.Doc"/> or <see cref="LoadFormat.Docx"/>.</p>
    /// </summary>
    /// <param name="srcFileName">The file name of the document to sign.</param>
    /// <param name="dstFileName">The file name of the signed document output.</param>
    /// <param name="certHolder"><see cref="CertificateHolder"/> object with certificate that used to sign file.
    /// <ms>The certificate in holder MUST contain private keys and have the X509KeyStorageFlags.Exportable flag set.</ms></param>
    /// <param name="signOptions"><see cref="SignOptions"/> object with various signing options.</param>
    public static void Sign(string srcFileName, string dstFileName, CertificateHolder certHolder, SignOptions signOptions)
     
    /// <summary>
    /// Signs source document using given <see cref="CertificateHolder"/> with digital signature
    /// and writes signed document to destination stream.
    /// <p>Document should be either <see cref="LoadFormat.Doc"/> or <see cref="LoadFormat.Docx"/>.</p>
    /// <p><b>Output will be written to the start of stream and stream size will be updated with content length.</b></p>
    /// </summary>
    /// <param name="srcStream">The stream which contains the document to sign.</param>
    /// <param name="dstStream">The stream that signed document will be written to.</param>
    /// <param name="certHolder"><see cref="CertificateHolder"/> object with certificate that used to sign file.
    /// <ms>The certificate in holder MUST contain private keys and have the X509KeyStorageFlags.Exportable flag set.</ms></param>
    public static void Sign(Stream srcStream, Stream dstStream, CertificateHolder certHolder)
     
    /// <summary>
    /// Signs source document using given <see cref="CertificateHolder"/> with digital signature
    /// and writes signed document to destination file.
    /// <p>Document should be either <see cref="LoadFormat.Doc"/> or <see cref="LoadFormat.Docx"/>.</p>
    /// </summary>
    /// <param name="srcFileName">The file name of the document to sign.</param>
    /// <param name="dstFileName">The file name of the signed document output.</param>
    /// <param name="certHolder"><see cref="CertificateHolder"/> object with certificate that used to sign file.
    /// <ms>The certificate in holder MUST contain private keys and have the X509KeyStorageFlags.Exportable flag set.</ms></param>
    public static void Sign(string srcFileName, string dstFileName, CertificateHolder certHolder)
    

    4. Old signing methods in DigitalSignatureUtil are marked as ‘Obsolete’

    public static void Sign(string srcFileName, string dstFileName, System.Security.Cryptography.X509Certificates.X509Certificate2 certificate, string comments, DateTime signTime);
    public static void Sign(string srcFileName, string dstFileName, CertificateHolder certHolder, string comments,DateTime signTime);
    public static void Sign(string srcFileName, string dstFileName, CertificateHolder certHolder, string comments, DateTime signTime, string srcPassword);
    public static void Sign(Stream srcStream, Stream dstStream, System.Security.Cryptography.X509Certificates.X509Certificate2 certificate, string comments, DateTime signTime);
    public static void Sign(Stream srcStream, Stream dstStream, CertificateHolder certHolder, string comments, DateTime signTime);
    public static void Sign(Stream srcStream, Stream dstStream, CertificateHolder certHolder, string comments, DateTime signTime, string srcPassword);

    Aspose.Words for .NET Resources

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

     

    Posted in Aspose.Words Product Family | Leave a comment

    Sponsoring User Groups and Conferences: Introducing NDC Sydney

    We are very excited about the latest NDC Conference to be held Down Under. NDC Sydney will hold nothing back when compared to its counterparts in Oslo and London. The agenda features 7 tracks and more than 100 speakers.

    Check out the NDC Sydney agenda and feel free to give them any feedback on Twitter @ndc_conferences

    Who?

    NDC Sydney has more than 100 speakers lined up, including:

    When and Where?

    • 14 – 18 August 2017, Hilton Sydney, Australia

    For more information, check the NDC Sydney FAQ.

    Buy Tickets now

    Posted in Developer Community Support | Leave a comment

    Aspose Supports DDD Melbourne 2017

    Sydney, Australia – DDD Melbourne is a full day non profit community event run by developers for developers. Topics include .NET, Java and Cloud based technologies. Anyone can submit a session to the event and delegates then vote on the sessions they want to see. We are always keen to sponsor developer events in the community such as DDD Melbourne. Check them out:

    What’s in Store?

    • One Day
    • Refreshments provided
    • Industry-leading Presenters
    • Only $49

    What’s On?

    Over 50 talks from a wide range of topics across the whole day. See the full agenda here 

    When and Where?

    • On Saturday, 12 August 2017 from 8:30 AM to 5:00 PM (AEDT)
    • Monash University Caulfield Campus

    ###END###

    About Aspose

    Aspose are file format experts. They offer a powerful set of file management APIs with which developers can create applications which can create, open, edit and save the majority of popular business file formats.

    The Aspose product range includes Microsoft Excel spreadsheet APIsMicrosoft Word processing APIsMicrosoft PowerPoint presentation APIsPDF document creation and manipulation APIs and many others.

    The Aspose products range of supported formats include Word documents, Excel spreadsheets, PowerPoint presentations, PDF documents, OneNote, Outlook, Project, Visio files, popular image formats and various other formats. Aspose produce APIs for .NET, Java, Cloud, which can be utilized in almost any modern language available today.

    Aspose Pty Ltd has been operating since 2002. The headquarters are in Australia, and the company has teams in numerous countries all over the world.

    Press Contact

    Web: www.aspose.com
    Telephone (Australia): +61 2 8006 6987

    Posted in Developer Community Support | Leave a comment