System Requirements – Aspose.SVG for .NET
Overview
To build and manipulate SVG documents, the machine that Aspose.SVG for .NET runs on doesn’t need to have modeling and rendering software installed. Aspose.SVG for .NET API also incorporates document generation engine.
Supported Operating System
Windows
- Microsoft Windows Server 2022 (x64)
- Microsoft Windows 2019 Server (x64)
- Microsoft Windows 2016 Server (x64)
- Microsoft Windows Server 2012 R2 (x64)
- Microsoft Windows Server 2012 (64-bit edition) (x64)
- Microsoft Windows Server 2008 R2 SP1 (x64)
- Microsoft Windows Server 2008 SP2 (x64, x86)
- Microsoft Windows 11 (x64)
- Microsoft Windows 10 (x64, x86)
- Microsoft Windows 8.1 (x64, x86)
- Microsoft Windows 8 (x64, x86)
- Microsoft Windows 7 SP1 (x64, x86)
- 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+)
Based on your Linux distribution or macOS version and the fact that Aspose.SVG for .NET uses the System.Drawing.Common assembly, you may need to install additional dependencies. The list of all the supported distributions and additional dependencies can be found here for Linux and here for macOS.
We also provide Aspose.SVG.Drawing.SkiaSharp for .NET that uses SkiaSharp instead of System.Drawing.Common. Using it on Linux will require installing an additional NuGet package containing the corresponding native assets, here are some of them:
- 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.
- Jellyfin.SkiaSharp.NativeAssets.LinuxArm – provides a native Skia build for arm32 and arm64 Debian based Linux distributions.
Development Environments
You can use Aspose.SVG for .NET to develop applications in any development environment that targets the .NET platform, but the following environments are explicitly supported:
- Microsoft Visual Studio 2010
- Microsoft Visual Studio 2011
- Microsoft Visual Studio 2012
- Microsoft Visual Studio 2013
- Microsoft Visual Studio 2015
- Microsoft Visual Studio 2017
- Microsoft Visual Studio 2019
Supported Frameworks
Aspose.SVG for .NET provides assemblies compiled for the following frameworks:
| .NET Standard |
|---|
| .NET Standard 2.0 |
Therefore it is compatible with:
| .NET Framework | .NET Standard | .NET Core | .NET |
|---|---|---|---|
| .NET Framework 4.6.1 | .NET Standard 2.0 | .NET Core 2.0 | .NET 5.0 |
| .NET Framework 4.6.2 | .NET Standard 2.1 | .NET Core 2.1 | |
| .NET Framework 4.6.3 | .NET Core 2.2 | ||
| .NET Framework 4.7 | .NET Core 3.0 | ||
| .NET Framework 4.7.1 | .NET Core 3.1 | ||
| .NET Framework 4.7.2 | |||
| .NET Framework 4.8 | |||
| .NET Framework 4.8.1 |
Due to the fact that some of the Microsoft libraries used by Aspose.SVG for .NET no longer support legacy frameworks, an error will be thrown when trying to compile using them. You can remove it in the following ways:
- Update to a newer framework.
- Hide it by writing “<PropertyGroup><SuppressTfmSupportBuildWarnings>true</SuppressTfmSupportBuildWarnings></PropertyGroup>” in the project file.
If you hide this error, then some functions of the library may not work correctly.
Trust Level
Generally, all Aspose .NET components require Full Trust permissions set. The reason is, Aspose .NET components need to access registry settings, system files, other than virtual directory, for certain operations, like reading fonts etc. Moreover, Aspose .NET components (including Aspose.SVG for .NET) are based on core .NET system classes, that also require Full Trust permissions set in many cases.
Internet Service Providers, hosting multiple applications from different companies, mostly enforce a Medium Trust security level. Such a security level may set the following constraints, which could affect the ability of Aspose.SVG for .NET to perform properly:
- RegistryPermission is not available. This means, you can’t access the registry.
- WebPermission is restricted. This means, your application can only communicate with an address or range of addresses, that you define in the
<trust>element. - FileIOPermission is restricted. This means, you can only access files in your applications virtual directory hierarchy.
Due to the reasons, specified above, it is recommended, that Aspose.SVG for .NET is run on servers granting Full Trust permissions.