DynamicPDF™ for .NET- Frequently Asked Questions

What version of the .NET Framework is supported?

The framework v1.0, v1.1, v2.0, v3.0 and v3.5 are supported. It has been fully tested against these versions of the framework. Examples are included for Visual Studio 2005 and 2008. Non-Visual Studio examples are provided as well that work with both versions of the Framework.

Is DynamicPDF v5.0 for .NET compatible with DynamicPDF v4.0 for .NET?

DynamicPDF v5.0 for .NET contains significant improvements over DynamicPDF v4.0 for .NET and is mostly compatible with that product. However, small changes may need to be made to your code. A complete list of differences can be found on the Compatibility page.

Can I use XCOPY deployment?

Yes, Our assemblies are strongly named and 100% managed. They have no external dependencies. They can be deployed by placing them to your applications bin folder. The licensing information can be placed in your .config file or added with one line of code when your application starts.

If we purchase a Server Edition do we need a seperate license for our development server and development workstations?

No, Server Editions are licensed per production server. You may use the same license on development workstations and development servers.

If we purchase a Developer Edition, do we need to license servers that we deploy to?

No, Developer Editions are licensed per developer. A developer can deploy an unlimited number of server or workstation based applications and assemblies royalty free.

How is the licensing information included in my redistributable application?

With a developer license, your unique license key is embedded in your application or added with one line of code when your application starts. This license key can be retrieved from our website after purchasing a Developer Edition license.

If I purchase a Server Edition, can I deploy without installing the MSI package on the target server?

Yes, the target server can be licensed by placing a license key in your applications .config (web.config) file or by adding one line of code when your application starts. This license key can be retrieved from our website after purchasing a Server Edition license.

Our server has multiple processors. Do I need to purchase a license for each processor?

No, this product places no restrictions on the number of processors on the machine.

Do I need to purchase a maintenance plan to recieve upgrades or updates?

No, upgrades between minor version are free. Upgrades between major versions are provided free to maintenance subscribers and are offered at a significantly reduced cost to other licensed users.

Are there recurring costs when using your product?

No, once you purchase a license you can use that version of the software as long as you like. You can choose to purchase a support plan if you want preffered e-mail and telephone support and free upgrades between major versions.

What image types are supported?

DynamicPDF™ Merger for .NET relies on DynamicPDF™ Generator for .NET for all of the Page Elements including the images. It supports all the formats that DynamicPDF™ Generator for .NET supports: Jpeg, Jpeg 2000, Png, Bmp, Emf, Exif, Gif, Tiff, and Wmf. It also accepts images from System.IO.Stream or System.Drawing.Bitmap objects.

Note: The above only applies to new images added to the PDF. Any and all images pre-existing on the PDF are preserved.

Why do I see the PDF code in the browser instead of the PDF document?

This can be caused by using the refresh button after correcting an error. IE does not update the MIME type when using the refresh button. It is best to always link to the page from another to ensure that the MIME type is set correctly. This can also be caused by outputting HTML before the Draw method is called or by adding custom HTTP headers to the output stream. ISAPI filters on your web server can interfere with this as well.