GroupDocs.Conversion
GroupDocs.Conversion for .NET is a universal document conversion library designed for easy integration into any .NET application. The library allows you to enhance your app with the capability to convert back and forth over 50 document and image file formats. Keeping above in mind, GroupDocs.Conversion API is developed to make the life easier while working with Conversion. It is a very powerful and easy to use API that provides all basic Conversion operation for a number of file formats. API gets the file as an input and makes its Conversion accessible for the user. Now, its upto the user to perform any of his operations on this Conversion. The product has the following key features: - Converting document from all major file formats to all major file formats - Native .NET API, allowing to third party developers to easy integrate GroupDocs.Conversion in their products - Simple to use API - basically only one method with set of options for different formats. - Abstract Storage API - Abstract Cache API For more details on the library, please visit GroupDocs website at: https://products.groupdocs.com/conversion/net Note: The library comes up with some limitations in the evaluation mode. In order to test full features of GroupDocs.Conversion for .NET library, please request a free 30-day temporary license.
Install
dotnet add package GroupDocs.Conversion --version 17.12.0
Install-Package GroupDocs.Conversion -Version 17.12.0
<PackageReference Include="GroupDocs.Conversion" Version="17.12.0" />
Frameworks
No framework metadata available.
Dependencies
No declared dependencies.
Adoption guide
A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.
No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.
No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.