- How to use a system font for rendering text
- Customize the GUI interaction of a radio button
- Customize the UI interaction of a check box
- How to reduce PDF file size
- How do I create graphics with Icc based colors
- Draw interactively on a PDF page
- Verify a custom digital PDF signature
- How do I use PDFControls.NET in a WPF application
- Fill PDF form
- Flatten PDF form
- Digitally sign a PDF form in C# or VB.NET
- C# render pdf in browser using MVC
- Add hyperlink to PDF
- Rotate a PDF page
- Change the formatting of a numeric field
- Override MouseWheel event
- How to create a thumbnail viewer
- EMF to PDF as vector image
- EMF to PDF as raster image
- Add a rubber stamp annotation with a custom icon
- Create a text annotation in PDF with rich text
- Read and write meta data from PDF
- Use multiple licenses
Use multiple licenses
This code sample explains how to register multiple license keys with a single application.
Here is the web.config that includes a single license key for a PDFKit.NET 4.0 Server license:
<configuration> <appSettings> <add key="PDFKit.NET 4.0 Server Key" value="7206:JUm8jYm-4bwE84gi8RtQuk++" /> </appSettings> </configuration>
Now suppose that this web.config file is part of a project that is used to deploy to two different servers. In that case, it is possible to add a second key to the same web.config. Because a config file behaves like a dictionary, you must make the key attribute unique by adding a postfix. Our licensing code only checks if the key attribute starts with the expected string so the postfix may be anything. It will check all licenses until verification succeeds.
Here is the web.config file with the second key added:
<configuration> <appSettings> <add key="PDFKit.NET 4.0 Server Key SVR001" value="7206:JUm8jYm-4bwE84gi8RtQuk++" /> <add key="PDFKit.NET 4.0 Server Key SVR002" value="3070:5RwUiW1lHWFEcteNiQFTy+++" /> </appSettings> </configuration>
Note the postfix of the key attribute. Although it can be anything, it is recommended to use something that makes sense.
We have sent an email with a download link. Alternatively, you may want to use the NuGet package manager to install our library.
Use the NugetID and start right away, or download the package and install it handmatically