Aspose.SVG.Drawing.SkiaSharp
Aspose.SVG.Drawing.SkiaSharp is a self-contained build of Aspose.SVG for .NET that uses the SkiaSharp graphics engine instead of GDI+. Simply add the package reference to begin rendering and processing SVG files - no extra configuration code is required. Aspose.SVG seamlessly integrates into your .NET apps to provide processing, DOM manipulation, rendering, and conversion of SVG files without installing any third-party modeling or rendering software. Its DOM implementation is fully compatible with official SVG specifications, allowing you to: • Create SVG files from scratch or merge multiple SVG documents • Navigate content via XPath queries or CSS selectors • Vectorize text elements to keep output crisp at any resolution • Convert or render SVG to PDF, XPS, PNG, JPEG, TIFF, and GIF with SkiaSharp's hardware-accelerated pipeline benefiting from its filters, shaders, and image-processing effects. Written in managed C#, the library works with C#, VB.NET, F#, and any .NET language targeting .NET Standard 2.0. It runs cross-platform on Windows, Linux, macOS, Mono, and all modern .NET (Core/5+/6+/7+) runtimes. Note: This package already contains the full Aspose.SVG API compiled with SkiaSharp. Do not call Aspose.Svg.Configuration.SetExtension(new SkiaModule()); and you do not need a separate Aspose.SVG package.
Install
dotnet add package Aspose.SVG.Drawing.SkiaSharp --version 26.1.0
Install-Package Aspose.SVG.Drawing.SkiaSharp -Version 26.1.0
<PackageReference Include="Aspose.SVG.Drawing.SkiaSharp" Version="26.1.0" />
Frameworks
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.
Compatibility metadata lists 1 target framework; confirm the exact target used by your application.
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.