ASP.NET Setup for .NET Framework 3.5 / 4.x

The appSettings element of the configuration element must contain the following keys:

• RadPdfLicenseKey – This key must contain the server license key provided by Red Software. If evaluating RAD PDF, "DEMO" should be used.
  XML

  Copy

  <add key="RadPdfLicenseKey" value="YOUR LICENSE KEY" />

The appSettings element of the configuration element may contain the following keys:

• RadPdfConnectionString – This key must contain a value which is a valid connection string to a SQL Server instance. This connection string must contain the name of the database which RAD PDF should use (e.g. RadPdf). This key is only required if using the PdfWebControl. The PdfWebControlLite does not use SQL Server.
  XML

  Copy

  <add key="RadPdfConnectionString" 
   value="Server=.\SQLExpress;Database=RadPdf;Trusted_Connection=Yes;" />

• RadPdfIntegrationProvider – This optional key registers a custom Integration Provider. The value of this key must be the assembly-qualified name of a Type which implements the abstract class PdfIntegrationProvider. This value should be a fully qualified name of a class in the format:
  Copy

  TopNamespace.SubNameSpace.ContainingClass+NestedClass,MyAssembly

  For example, to register a custom Integration Provider class with the type name CustomPdfIntegrationProvider located in an assembly with the name MyAssembly, a value of "CustomPdfIntegrationProvider,MyAssembly" should be used.

  XML

  Copy

  <add key="RadPdfIntegrationProvider" 
   value="CustomPdfIntegrationProvider,MyAssembly" />

  For example, to register a custom Integration Provider class with the type name CustomPdfIntegrationProvider located in your web application's App_Code directory, a value of "CustomPdfIntegrationProvider,App_Code" should be used.

  XML

  Copy

  <add key="RadPdfIntegrationProvider" 
   value="CustomPdfIntegrationProvider,App_Code" />

  To use the default Integration Provider, a value of "DefaultPdfIntegrationProvider" should be used or the key left absent from the web.config file.

  XML

  Copy

  <add key="RadPdfIntegrationProvider" 
   value="DefaultPdfIntegrationProvider" />

Note
These legacy settings are provided for backwards compatibility with previous versions of RAD PDF. They will be removed in a future version and should not be used in new applications.

The appSettings element of the configuration element may contain the following legacy keys if using the DefaultPdfIntegrationProvider (or no integration provider is specified in PdfIntegrationProvider):

• RadPdfDocumentOverheadMax – This legacy key can limit the size of a document's storage overhead (the space taken up by objects and images added to a document). To limit document overhead, a value of "x" should be used, where x is the maximum overhead per document in bytes. To not limit document overhead, a value of "0" should be used (default). (NOTE: This setting does not limit the size of PDF files loaded, only the content added to a document by users via the web browser.)
  XML

  Copy

  <add key="RadPdfDocumentOverheadMax" 
   value="1048576" />

• RadPdfHttpCompression – This legacy key can enable or disable HTTP Compression (GZip / Deflate) for requests handled by the PdfHttpHandler. By default (or if not specified), HTTP Compression is enabled. To disable, a value of "0" should be used.
  XML

  Copy

  <add key="RadPdfHttpCompression" 
   value="1" />

• RadPdfSearchTermMin – This legacy key can specify the minimum number of letters which a search term must contain in order to be used to search a PDF document. By default (or if not specified), no minimum is enforced (as if a value of "0" is specified).
  XML

  Copy

  <add key="RadPdfSearchTermMin" 
   value="3" />

• RadPdfServiceLocation – This legacy key can contain the location and port of the RAD PDF System Service. By default (or if not specified), the value "localhost:18104" is used.
  XML

  Copy

  <add key="RadPdfServiceLocation" 
   value="localhost:18104" />