Convert ZIP to PDF | C# example

Aspose.HTML offers a free online ZIP to PDF Converter that converts ZIP to PDF with high quality, easy and fast. Just upload, convert your files and get results in a few seconds!

Text “Banner ZIP to PDF Converter”

There are many reasons why would you require to convert ZIP to PDF format. PDF comes with many advantages that other files don’t have. For example, many programs and apps support PDF documents, most web browsers such as Chrome and Firefox can display a PDF. PDF files are optimized for printing; they are ideal for creating physical copies of your documents. PDF supports many compression algorithms. You can configure the security settings for your PDF file, etc.

Create a Custom Message Handler for ZIP to PDF Conversion

Aspose.HTML for .NET offers functionality for custom message handlers creating. Let’s design a custom handler that we can use to work with ZIP archives. Take the following steps:

  1. Use the necessary Namespace, which is the Aspose.Html.Net . This Namespace is presented by classes and interfaces which are responsible for helping easy network processing.

  2. To create a custom Message Handler, you need to define your own class that will be derived from the MessageHandler class. The MessageHandler class represents a base type for message handlers. Inheriting from IDisposable is necessary to provide a mechanism for the deterministic release of unmanaged resources.

using Aspose.Html.Net;
...

	class ZipArchiveMessageHandler : MessageHandler, IDisposable
	{
	}

So, you have defined your own ZipArchiveMessageHandler class, now you need to do some operations within it.

  1. Initialize an instance of the ZipArchiveMessageHandler class and define a Filter property for it.

  2. Override the Invoke() method of the MessageHandler class to implement the custom message handler behaviour.

	
using System.Net;
using Aspose.Html;
using Aspose.Html.Net;
using Aspose.Html.Net.MessageFilters;
using Aspose.Zip;
...	

	// Define ZipArchiveMessageHandler class that is derived from the MessageHandler class
	class ZipArchiveMessageHandler : MessageHandler, IDisposable
	{
	    private string filePath;
	    private Archive archive;
	
	    // Initialize an instance of the ZipArchiveMessageHandler class
		public ZipArchiveMessageHandler(string path)
	    {
	        this.filePath = path;
	        Filters.Add(new ProtocolMessageFilter("zip"));
	    }
	
	    // Override the Invoke() method
		public override void Invoke(INetworkOperationContext context)
	    {
	        // Call the GetFile() method that defines the logic in the Invoke() method
			var buff = GetFile(context.Request.RequestUri.Pathname.TrimStart('/'));
	        if (buff != null)
	        {
	            // Checking: if a resource is found in the archive, then return it as a Response
	            context.Response = new ResponseMessage(HttpStatusCode.OK)
	            {
	                Content = new ByteArrayContent(buff)
	            };
	            context.Response.Headers.ContentType.MediaType = MimeType.FromFileExtension(context.Request.RequestUri.Pathname);
	        }
	        else
	        {
	            context.Response = new ResponseMessage(HttpStatusCode.NotFound);
	        }
	        
	        // Call the next message handler
			Next(context);
	    }
	}		

Let’s take a closer look at this code snippet:

  • First of all, the custom ZipArchiveMessageHandler needs to inherit from the base MessageHandler class. It has two variables: the archive and the string representation of the path to the archive.

  • The message handler has the concept of filtering. In this case, a protocol (schema) filter is added; this message handler will only work with the "zip" protocol. That is, if the resource has a "zip" protocol, then it will be processed by ZipArchiveMessageHandler.

    Filtering messages by resource protocol is implemented using the ProtocolMessageFilter class. The ProtocolMessageFilter() constructor initializes a new instance of the ProtocolMessageFilter class. It takes the "zip" protocols as a parameter.

  • The Invoke() method implements the message handler behaviour. It is called for each handler in the pipeline and takes a context as a parameter. The GetFile() method defines the logic in the Invoke() method. It implements the chain of duties, after which the next Next(context) handler is called. The GetFile() method realizes a search for data as a byte array in a zip archive based on Request and forms Response.

    context provides contextual information for network services, the entity of the operation is passed through it, and the result of the operation is returned. In Aspose.HTML, the context is realized by INetworkOperationContext interface that has two properties (parameters) - Request and Response . Request gets or sets the request message, Response gets or sets the response message. The Request contains information for a web request, for example, a URL - a path to a resource, headers, etc. The Response contains the response that the endpoint (Internet) returned.

Define the GetFile(), GetArchive(), and Dispose() Methods

using System.IO;
using Aspose.Zip;
...

	byte[] GetFile(string path)
	{
	    path = path.Replace(@"\", @"/");
	    var result = GetArchive().Entries.FirstOrDefault(x => path == x.Name);
	    if (result != null)
	    {
	        using (var fs = result.Open())
	        using (MemoryStream ms = new MemoryStream())
	        {
	            fs.CopyTo(ms);
	            return ms.ToArray();
	        }
	    }
	    return null;
	}


	Archive GetArchive()
	{
	    return archive ??= new Archive(filePath);
	}


    public void Dispose()
    {
        archive?.Dispose();
    }

Add ZipArchiveMessageHandler in the Pipeline and Convert ZIP to PDF

You would now need to add ZipArchiveMessageHandler in the pipeline. Use Add() method that takes a zip object as a parameter and adds ZipArchiveMessageHandler to the end of the message handlers' collection.

The INetworkService.MessageHandlers property gets a list of MessageHandler instances to be invoked as a RequestMessage executes.

using System;
using Aspose.Html;
using Aspose.Html.Net;
using Aspose.Html.Rendering.Pdf;
using Aspose.Html.Services;
...

	// Prepare path to a source zip file
	string documentPath = Path.Combine(DataDir, "test.zip");
	
	// Prepare path for converted file saving
	string savePath = Path.Combine(OutputDir, "zip-to-pdf.pdf");
	
	// Create an instance of ZipArchiveMessageHandler
	using var zip = new ZipArchiveMessageHandler(documentPath);
	
	// Create an instance of the Configuration class
	using var configuration = new Configuration();
	
	// Add ZipArchiveMessageHandler to the chain of existing message handlers
	configuration
	    .GetService<INetworkService>()
	    .MessageHandlers.Add(zip);
	
	// Initialize an HTML document with specified configuration
	using var document = new HTMLDocument("zip:///test.html", configuration);
	
	// Create the PDF Device  
	using var device = new PdfDevice(savePath);
	
	// Render ZIP to PDF
	document.RenderTo(device);	

In the example, the ZIP archive (test.zip) has the HTML document (test.html) in which all related resources have paths relative to the HTML document.

Note: The HTMLDocument(address, configuration) constructor takes the absolute path to the ZIP archive. But all related resources have relative paths in the HTML document and in the example’s code.

Please read the Fine-Tuning Convserters article to learn more about converting HTML to PDF using Renderto(device) method.