Gnostice Document Studio .NET > Migration > Migration from Gnostice PDFOne .NET

As part of our plans to provide a single product for all your document processing requirements, we have now introduced all the functionality of PDFOne .NET into Document Studio .NET. The enhanced all-in-one product enables new workflows and possibilities apart from giving you a PDF document object that includes all the features of PDFOne .NET.

Document Studio users can now create new PDF documents or enhance and modify existing PDF documents and view, print, and convert that document in a single workflow using a single document object. On the other hand, PDFOne .NET users now get the capability to view, print and convert Microsoft Office, OpenOffice, and image formats and include them into the PDF being created or modified. Since Document Studio supports .NET Core, PDFOne .NET users can now build their apps for the .NET frameworks. Additionally, PDFOne .NET users get a much more powerful viewer for WinForms, WPF, and ASP.NET with full text search capability.

Migrating Document Studio .NET applications to use the enhanced product

•No changes are required to your application, except including appropriate using statements to use the new document classes.

Migrating PDFOne .NET applications to use the enhanced product

•NOTE: The enhanced Document Studio .NET product supports .NET framework 4.6.2 and above. If, for some reason, you are not able to use .NET framework 4.6.2, then please continue to use PDFOne .NET until you can upgrade to .NET 4.6.2.

•Reference the new Document Studio NuGet package.

•Update the using statements for the new classes you will use.

•Remove reference to System.Drawing if you are not using any GDI+ types.

•Change graphics/drawing objects to the new Document Studio .NET types.

•Document Studio .NET uses an activation-based licensing system. The license needs to be installed on the developer machine instead of passing a license key via code at run-time. See the help topic here for more details.

PDFOne .NET objects to Document Studio .NET objects mapping

The following sections list the affected PDFOne .NET types and their Document Studio .NET counterparts.

Namespace change

•Gnostice.PDFOne to Gnostice.Documents.PDF

Class name change

•PDFDocument to PDF

Method name changes

•PDFDocument.Load to PDF.LoadDocument

•PDFDocument.Split to PDF.ExtractPagesTo

Method argument changes

•Generic collections to parametrized collections, in some cases. For example ArrayList to List<T>

•PDFFont constructor: Changed the argument order

•PDF.WriteWatermarkText: Reduced number of overloaded methods by introducing default values for parameters

Methods removed

•PDF.SaveAsImage and PDF.SaveAsMultiPageTiff: Use the DocumentConverter component to convert PDF to images

Enumeration changes

•PDFMeasurementUnit to MeasurementUnit

•PDFFontEmbedType to FontEmbedType

Event name changes of the WinForms DocumentViewer control

•PasswordRequired to NeedPassword

•AfterPDFLoaded to DocumentLoaded

•RenderError to DocumentProcessingError

•PageMouseActivity to MouseUp / MouseDown / MouseMove

•PageClick to OnPageClicked

WinForms Document Viewer

•Document Studio .NET (Professional edition) includes a modern WinForms document viewer control that supports viewing multiple document formats. See the help topic here to get started with the control.

ASP.NET Document Viewer

•Document Studio .NET (Ultimate edition) includes a modern ASP.NET document viewer control that supports viewing multiple document formats, and supports ASP.NET Core platform. See the help topic here to get started with the control.

Product key and License

•No action is required for Document Studio .NET users to use the new product. You can continue to use your existing key and access the new functionality.

•PDFOne .NET users will need to use the new key assigned to them and activate their license. More details can be found in the help document.

•All PDFOne .NET users with active maintenance will be upgraded to Document Studio .NET Professional free of change.