ByteScout PDF Extractor SDK - ASP.NET - Extract Attachments - ByteScout

ByteScout PDF Extractor SDK – ASP.NET – Extract Attachments

  • Home
  • /
  • Articles
  • /
  • ByteScout PDF Extractor SDK – ASP.NET – Extract Attachments

ByteScout PDF Extractor SDK – ASP.NET – Extract Attachments


using System;
using Bytescout.PDFExtractor;

namespace ExtractAttachments
    public partial class _Default : System.Web.UI.Page
        protected void Page_Load(object sender, EventArgs e)
            String inputFile = Server.MapPath(@".\bin\attachments.pdf");

            // Create Bytescout.PDFExtractor.AttachmentExtractor instance
            AttachmentExtractor extractor = new AttachmentExtractor();
            extractor.RegistrationName = "demo";
            extractor.RegistrationKey = "demo";

            // Load sample PDF document

            Response.ContentType = "text/html";

            for (int i = 0; i < extractor.Count; i++)
                string attachmentFileName = extractor.GetFileName(i);
                int attachmentFileSize = extractor.GetSize(i);

                Response.Write("Found attachment: " + attachmentFileName + "<br/>");

                // You can save the attachment to a file
                //extractor.Save(i, attachmentFileName);

                 // ... or write to output stream
                //extractor.Save(i, Response.OutputStream);

                Response.Write("- file size: " + attachmentFileSize + "<br/><br/>");




<?xml version="1.0"?>
            Set compilation debug="true" to insert debugging 
            symbols into the compiled page. Because this 
            affects performance, set this value to true only 
            during development.
    <compilation debug="true" targetFramework="4.0"/>
            The <authentication> section enables configuration 
            of the security authentication mode used by 
            ASP.NET to identify an incoming user. 
    <authentication mode="Windows"/>
            The <customErrors> section enables configuration 
            of what to do if/when an unhandled error occurs 
            during the execution of a request. Specifically, 
            it enables developers to configure html error pages 
            to be displayed in place of a error stack trace.

        <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
            <error statusCode="403" redirect="NoAccess.htm" />
            <error statusCode="404" redirect="FileNotFound.htm" />
    <pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID"/>

  Click here to get your Free Trial version of the SDK