The .NET Framework v2.0, v3.0, v3.5, v4.0 and v4.5 are supported. DynamicPDF has been fully tested against these versions of the .NET Framework and there is a separate DynamicPDF build to target each framework version. Examples are included for Visual Studio 2005, 2008, 2010 and 2012 (Non-Visual Studio examples are also provided).

DynamicPDF v7.0 for .NET contains significant improvements over DynamicPDF v6.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.

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.

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

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

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.

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.

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

No, a maintenance plan is not required for major version upgrades but it is the most cost effective way to stay current with major version releases. Upgrades without an active maintenance plan will receive a credit based on the released and purchased version (credits are available for up to 2 versions back).

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.

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.

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.