ByteScout PDF Renderer SDK - ASP.NET - PDF to TIFF multipaged - ByteScout

ByteScout PDF Renderer SDK – ASP.NET – PDF to TIFF multipaged

  • Home
  • /
  • Articles
  • /
  • ByteScout PDF Renderer SDK – ASP.NET – PDF to TIFF multipaged

ByteScout PDF Renderer SDK – ASP.NET – PDF to TIFF multipaged


using System;
using System.Web.UI;
using Bytescout.PDFRenderer;

namespace BasicExample
	public partial class _Default : Page
		protected void Page_Load(object sender, EventArgs e)
			// Prepare a test document.
			// Multipage.pdf file will be copied to the project directory on the pre-build event (see the project properties).
			String inputDocument = Server.MapPath("multipage.pdf");

			// Create an instance of Bytescout.PDFRenderer.RasterRenderer object and register it.
			RasterRenderer renderer = new RasterRenderer();
			renderer.RegistrationName = "demo";
			renderer.RegistrationKey = "demo";

			// Load PDF document.

            // Write the response.
            Response.ContentType = "text/html";

            Response.Write("Converting into multipaged TIFF image...<br>");

			// Render document to multi-page TIFF file at 300 DPI resoultion
            renderer.SaveMultipageTiff(Server.MapPath("output.tiff"), 0, -1, 300);

            Response.Write("Done! Check <a href=\"output.tiff\">output.tiff</a> file saved");



<?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"/></system.web>

  Click here to get your Free Trial version of the SDK