How to Create a PDF with ASP.NET on a Web Server without Visual Studio

PDF Creator Pilot documentation

Download CHM version of this manual.

PDF Creator Pilot 4 Knowledge Base

How to Create a New PDF Document

How to Insert an Image into a PDF

How to Write Text in a PDF Document

How to Draw Simple Elements (Line, Circle, Arc) with Different Attributes

How to Manipulate Primitives to Clip Drawing Objects

How to Create a PDF with ASP.NET on a Web Server without Visual Studio

How to Create a PDF with PHP on a Web Server

How to Create a PDF with Python on a Web Server

How to Create or Edit a PDF with Python

How to Convert a Metafile to a PDF Using C++

How to Convert an Image to a PDF Using VB.NET

How to Make Graphics and Images Transparent

How to Create a PDF with ASP.NET on a Web Server without Visual Studio

Knowledge Base :: PDF Creator Pilot 4 Knowledge Base

See Also Example

Collapse All

To enable PDF Creator Pilot to work with ASP.NET, you must perform three steps:

Create an Interop wrapper.
Copy the wrapper into a specific folder.
Attach the namespace libraries to the application.

To create the Interop wrapper of PDF Creator Pilot (i.e. a wrapper that would make it possible to call the unmanaged COM object code of the library from the managed code of an ASP.NET application), we should use one of the standard utilities from the .NET SDK - TlbImp.exe (C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin\TlbImp.exe)

Example:

TlbImp.exe PDFCreatorPilot.dll /out:Interop.PDFCreatorPilotLib.dll

Then copy the wrapper into the "bin" subfolder of the Web application root folder. (If that folder does not yet exist, we will have to create it.)

Example:

If the Web application is located in "C:\Inetpub\wwwroot\MyApp", then put the wrapper into "C:\Inetpub\wwwroot\MyApp\bin".

To attach the Web application to the namespace library, append the following line to the ".aspx"-file:

<%@ Import Namespace="Interop.PDFCreatorPilotLib" %>

After that, a COM object of PDF Creator Pilot may be used from ASP.NET.

Important: after updating a PDF Creator Pilot to a new version you must update your Interop-wrappers also.

Example

Using PDF Creator Pilot in an ASP.NET Page

[copy to clipboard]

<%@ Import Namespace="System" %>
<!-- other import directives are here -->
<%@ Import Namespace="Interop.PDFCreatorPilotLib" %>
<HTML> <HEAD>
  <TITLE>Test</TITLE>
  <SCRIPT language="C#" runat="server">
    void ButtonPerform_Click(object sender, System.EventArgs e)
    {
      PDFDocument4Class pdf = new PDFDocument4Class();
      pdf.SetLicenseData("demo@demo", "demo");
      pdf.AutoCreateURL = true;
      // set other options if needed
      // do something
      pdf.SaveToFile("path\\saved.pdf", false);
    }
  </SCRIPT>
</HEAD>
<BODY>
  <!-- here page content goes -->
  <FORM runat="server">
    <INPUT type="button" id="ButtonPerform" value="Click Me"
      OnServerClick="ButtonPerform_Click" runat="server" />
    <!-- or another vaiant -->
    <asp:Button id="ButtonPerform1" Text="Click Me"
      OnClick="ButtonPerform_Click" runat="server" />
  </FORM>
</BODY>
</HTML>

Components for Developers © 2000-2008, Two Pilots

PDF Creator Pilot documentation

Example

See Also

Components for Developers
© 2000-2008, Two Pilots