VintaSoft Imaging .NET SDK - F.A.Q.

Answers to popular questions

This page contains answers to the frequently asked questions about VintaSoft Imaging .NET SDK. If you have not found an answer to your technical question, please go to the technical support page. If you have not found an answer to your sales question, please go to the general sales information page.

VintaSoft Imaging .NET SDK is intended for usage in end-user applications based on .NET technology for Windows, Linux and macOS.

VintaSoft Imaging .NET SDK provides a set of software development tools for loading, viewing, editing, printing, capturing from camera and saving digital images, converting them among different image file formats, providing also broad facilities to work with multipage TIFF files and extra large TIFF images and much more.

So the product is attributed as a professional software development kit (library, component) meant for the use by persons having base knowledges and skills in programming of software applications. VintaSoft Imaging .NET SDK is the result of careful work of VintaSoft's highly educated staff for many years.

VintaSoft Imaging .NET SDK can be used as standalone component or its functions can be complemented with Annotation, PDF, JBIG2, JPEG2000, DocCleanup, OCR, DICOM, Forms Processing and Office Plug-ins features in any combination.

VintaSoft Imaging .NET SDK is the core library for all Plug-ins, which are not standalone products.

You can use the SDK in:
  • C#
  • Visual Basic .NET
  • C++ for .NET
  • F#
  • Borland Delphi for .NET
  • Borland C#
  • any other languages compatible with .NET technology.
The SDK consists from:
  • DLL files compiled under .NET 8, .NET 7, .NET 6, .NET Framework 4+, .NET Framework 3.5. Files are located in "[install_path]\Bin" folder.
  • SDK documentation, which contains User Guide and API Reference. Information about documentation can be found here.
  • Compiled demo applications (EXE files). Files are located in "[install_path]\Bin" folder.
  • Source codes of demo applications for Visual Studio .NET 2010-2022 for C#, VB.NET and ASP.NET. Files are located in "[install_path]\Examples" folder.
  • Test image files. Files are located in "[install_path]\Images" folder.
The files allowed for distribution are listed in paragraphs 4.6-4.9 of the License agreement.
Please read the information about the evaluation version limitations of VintaSoft Imaging .NET SDK and Plug-ins at the bottom of this page:
If you, after testing the evaluation version, have determined the set of necessary VintaSoft DLLs to be referenced in your application and now you have doubts what product license should be purchased, please refer to paragraphs 4.6-4.8 of the EULA.

It provides the list of all VintaSoft assemblies allowed for redistribution on one side and product names with editions on another side, allowing easily match DLL names with product names.
VintaSoft assemblies (DLL files) have four digits in version number. The information about the first version digit compatibility between Imaging DLL and a Plug-in DLL can be found on each Plug-in history page in versions headers. At the same time only the assemblies which have identical last 3 digits in version number can be used together (e.g. X.0.0.1). For example, when Imaging assembly has version X.0.0.1 and Plug-in assembly has version X.0.0.3 an exception will appear. Normally you shouldn't take any care about version numbers dependencies, we always provide setup packages with fully compatible assemblies by default.
Information about SDK documentation can be found here.

There are 2 ways to subscribe to the newsletter:

  • Subscribe to the newsletter of "Announcements" forums - all releases. Register yourself in VintaSoft Tech Community forums, login and click a tick "Subscribe forum" at the bottom of the forum page which is interesting for you.
  • Purchase a license and stay informed via e-mail directly from VintaSoft Support Service about all releases of licensed product during validity period of annual subscription.

Answers to the majority of questions can be found in the documentation or this web site. Please send a message to Customer Support Service to get more help.