Q: Is it possible to use PDF4NET library with Compact .NET Framework?
A: Yes, it is possible. The PDF4NET installation package contains a Compact .NET Framework edition
of PDF4NET library, along with the PDF4NET library for standard .NET framework (there are 2 different assemblies).
Please refer to Features page for details about the features supported by PDF4NET Compact .NET Edition |
| |
Q: Do I have to buy a separate license of PDF4NET to develop applications for
Compact .NET Framework?
A: No, you do not. A single license of PDF4NET covers both editions of the library, standard and compact .NET framework.
Now with a single license of PDF4NET library you can develop for web, desktop or mobile devices. The Compact .NET edition of
PDF4NET library can be redistributed ROYALTY FREE. |
| |
Q: Can I still use the library after my subscription expired?
A: Yes, you can. The subscription refers strictly to the period of time you get
technical support and have free access to new releases of PDF4NET library. 90 days subscription
means that you have free access to new releases (new versions) of the library for 90 days. A full year
subscription means free access for a year to new releases. The renewal of the subscription is not mandatory,
after the subscription expired, you can continue to use the library in development and
royalty free deploy/distribute your applications for unlimited time. You just do not have
free access to new versions of the library that were released after your subscription expired. |
| |
Q: Why are there only
14 page sizes?
A: The PDF4NET
library defines 14 page sizes as
being the most used sizes. If you
need other sizes for your pages,
just set the Width and Height properties
to the desired values. |
| |
Q: Why do you use your own graphic objects
(PDFPen, PDFBrush, PDFColor) instead of those built in .NET framework?
A: We chose to use our own graphic objects due to performance
reasons. Those built in .NET framework perform a lot of initializations
and allocate a large number of resources that are not needed
by our library. When profiling our library, we discovered that
even the "simple" Color performed a large number of calls in
.NET libraries, and consumed a significant percentage of execution
time, compared to the execution times of library's functions. |
| |
Q: Can PDF4NET be used as a printer driver?
A: PDF4NET library can not be used as a printer driver for creating pdf
files from Windows applications. It is a .NET class library used from any .NET
language to create pdf files from code. |
| |
Q: Can PDF4NET print existing pdf files to an installed
printer?
A: PDF4NET library can not print existing pdf files to a printer, it can only
create pdf files from code. |
| |
| |
|
