Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.
System Requirements
Contents
[
Hide
Show
]Aspose.SVG for .NET processes SVG documents directly in a .NET application and does not require a desktop drawing or rendering program. Review the supported operating systems, development environments, target frameworks, and rendering dependencies before deployment.
Supported Operating System
The current Aspose.SVG package information lists support for the following operating systems:
| Platform | Supported versions |
|---|---|
| Windows | Windows 11, 10, 8.1, 8, 7 SP1; Windows Server 2022, 2019, 2016, 2012 R2, 2012, 2008 R2 SP1, 2008 SP2; Microsoft Azure |
| macOS | Mac OS X x64 10.12+ |
| Linux | Linux x64 (6, 7, 27, 9, 8.7+, 18.04, 16.04, 14.04, 18, 17, 42.3+, 12 SP2+) |
For new applications, also check that the selected operating-system version is supported by the .NET runtime used in your project.
Linux and macOS Rendering Dependencies
The standard Aspose.SVG rendering implementation uses System.Drawing.Common. Depending on your Linux distribution or macOS version, additional dependencies may be required. See Microsoft’s platform installation documentation for
.NET on Linux and
.NET on macOS.
For modern non-Windows rendering scenarios, use
Aspose.SVG.Drawing.SkiaSharp, which renders through SkiaSharp instead of System.Drawing.Common. Starting with
Aspose.SVG for .NET 25.5, it is a self-contained Aspose.SVG build: install one package and no longer call SetExtension(new SkiaModule()) to activate it.
Linux deployments using Aspose.SVG.Drawing.SkiaSharp still require native Skia binaries. Published Aspose.SVG guidance lists the packages below. Before selecting one, check that its SkiaSharp version, target distribution, and CPU architecture match your application:
SkiaSharp.NativeAssets.Linux– provides a native Skia build for x64 Debian based Linux distributions.SkiaSharp.NativeAssets.Linux.NoDependencies– the package is intended to be used in Linux distributions that do not have the libfontconfig dependency. Tested on RHEL 7 (x64).Goelze.SkiaSharp.NativeAssets.AlpineLinux– provides a native Skia build for x64 Alpine Linux 3.9; NuGet marks this legacy package as deprecated and no longer maintained.Jellyfin.SkiaSharp.NativeAssets.LinuxArm– provides a native Skia build for arm32 and arm64 Debian based Linux distributions; its latest NuGet release is a legacy SkiaSharp 1.68.1 package.
Microsoft identifies System.Drawing.Common as Windows-specific starting with .NET 6 and documents that,
from .NET 7, it can no longer be enabled on non-Windows operating systems. This is why the SkiaSharp-based build matters for current Linux and macOS rendering deployments.
Development Environments
You can use Aspose.SVG for .NET in an environment that supports development for a compatible .NET target framework.
| Development environment | Supported versions or usage |
|---|---|
| Microsoft Visual Studio | Visual Studio 2010, 2011, 2012, 2013, 2015, 2017, and 2019 |
| SDK-based .NET projects | Use Visual Studio 2022, Visual Studio Code, Rider, or the .NET CLI with a compatible project target framework |
Supported Frameworks
The current Aspose.SVG and Aspose.SVG.Drawing.SkiaSharp packages target .NET Standard 2.0. Applications that implement .NET Standard 2.0 can reference these packages.
| .NET Framework | .NET Standard | .NET Core | .NET |
|---|---|---|---|
| .NET Framework 4.6.1+ | .NET Standard 2.0+ | .NET Core 2.0+ | .NET 5.0+ |
For an exact compatibility check in an existing project, compare its target framework with Microsoft’s .NET Standard implementation support table. NuGet recognizes .NET Framework 4.6.1 as compatible with .NET Standard 2.0, but Microsoft recommends targeting .NET Framework 4.7.2 or later when a .NET Framework application consumes .NET Standard 2.0 libraries.
Deployment Notes
Rendering can depend on resources available in the environment where an application runs:
- Provide required fonts when SVG text must render consistently.
- Ensure linked images, stylesheets, or fonts can be resolved when documents reference external resources.
- Grant access to input locations and output directories used by the application.
- Test representative SVG documents on the target environment before release.
Continue with Installation to add the selected package, Licensing before producing unrestricted output, and SVG Rendering Quality and Output Consistency before deployment.
FAQ
1. Which package should I use for an SVG rendering service deployed in a Linux container?
For a current Linux-based rendering service, evaluate Aspose.SVG.Drawing.SkiaSharp. It is the SkiaSharp-linked Aspose.SVG build intended for cross-platform rendering. The container must also include native SkiaSharp assets appropriate for its Linux distribution and CPU architecture, together with any fonts required by the SVG content.
2. Why can SVG output look different after moving an application from Windows to Linux?
The SVG source may be unchanged while the rendering environment is different. Missing fonts, font fallback, unavailable linked resources, and a different rendering implementation can affect text layout and image appearance. Render representative documents in the target environment before release, especially files that use branded fonts, filters, gradients, or external resources.
3. How can I check whether an existing .NET project can reference Aspose.SVG?
Check the project’s target framework against .NET Standard 2.0 compatibility. Both current Aspose.SVG packages target .NET Standard 2.0, so compatible .NET, .NET Core, .NET Framework, and .NET Standard projects can reference them. For a precise version check, use Microsoft’s .NET Standard implementation support table.