ByteScout PDF Extractor SDK - ASP.NET - Make PDF Unsearchable - ByteScout

ByteScout PDF Extractor SDK – ASP.NET – Make PDF Unsearchable

  • Home
  • /
  • Articles
  • /
  • ByteScout PDF Extractor SDK – ASP.NET – Make PDF Unsearchable

ByteScout PDF Extractor SDK – ASP.NET – Make PDF Unsearchable


using System;
using System.IO;
using System.Web.UI;
using Bytescout.PDFExtractor;

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

            // Create Bytescout.PDFExtractor.UnsearchablePDFMaker instance
            UnsearchablePDFMaker unsearchablePDFMaker = new UnsearchablePDFMaker();
            unsearchablePDFMaker.RegistrationName = "demo";
            unsearchablePDFMaker.RegistrationKey = "demo";

            // Load sample PDF document

            // Set PDF rendering resolution to 150 DPI. Higher value - better quality, but larger output file.
            unsearchablePDFMaker.RenderingResolution = 150;
            // Set embedded images format
            unsearchablePDFMaker.ImageFormat = EmbeddedImageFormat.PNG;

            Response.ContentType = "application/pdf";
            Response.AddHeader("Content-Disposition", "attachment;filename=result.pdf");

            // Process document and write result to temporary stream.
            byte[] resultBytes;
            using (MemoryStream tempStream = new MemoryStream())
                resultBytes = tempStream.ToArray();

            // Write result bytes to the output stream



<?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