| PdfCommonInitialize Method |
Initialize the SDK library
Namespace: Patagames.Pdf.NetAssembly: Patagames.Pdf (in Patagames.Pdf.dll) Version: 4.89.2704
Syntax public static void Initialize(
string licenseKey = null,
string specificPath = null,
string icuSpecificPath = null
)
Public Shared Sub Initialize (
Optional licenseKey As String = Nothing,
Optional specificPath As String = Nothing,
Optional icuSpecificPath As String = Nothing
)
public:
static void Initialize(
String^ licenseKey = nullptr,
String^ specificPath = nullptr,
String^ icuSpecificPath = nullptr
)
static member Initialize :
?licenseKey : string *
?specificPath : string *
?icuSpecificPath : string
(* Defaults:
let _licenseKey = defaultArg licenseKey null
let _specificPath = defaultArg specificPath null
let _icuSpecificPath = defaultArg icuSpecificPath null
*)
-> unit
public static void Initialize(
String licenseKey = null,
String specificPath = null,
String icuSpecificPath = null
)
Patagames.Pdf.Net.PdfCommon.Initialize = function(licenseKey, specificPath, icuSpecificPath);
Parameters
- licenseKey String (Optional)
- Yours license key. Can be null for demo mode
- specificPath String (Optional)
- Path to the pdfium dynamic library (.dll/.dylib). See remarks sections for detail.
- icuSpecificPath String (Optional)
- Path to the icudt dynamic labrary (.dll/.dylib). See remarks sections for detail.
Remarks You have to call this function before you can call any PDF processing functions.
In some cases, library initializer can not find pdfim/icudt dynamic library (.dll/.dylib) library to load.
A typical example of this situation is a Web application.
Web apps is running in a IIS working directory, unlike the classical apps. As a consequence, standard LoadLibrary function can not find the dll during loading process.
In this case, you must explicitly specify the full path to the dll files through specificPath parameters in the initialization method.
See Also