Aspose.Slides.NET6.CrossPlatform
Aspose.Slides.NET6 CrossPlatform can be used for .NET6, .NET7, and future .NET releases. Supported systems: Windows, Linux, and macOS. Aspose.Slides cross-platform contains a collection of libraries that implements its own graphics subsystem: aspose.slides.drawing.capi_vc14x64.dll, aspose.slides.drawing.capi_vc14x86.dll, libaspose.slides.drawing.capi_x86_64_libstdcpp_libc2.23.so, libaspose.slides.drawing.capi_appleclang_x86_64.dylib, and libaspose.slides.drawing.capi_appleclang_arm64.dylib. Notes: Aspose.Slides .NET6-CrossPlatform public API duplicates the types and namespaces from System.Drawing.Common (Bitmap, Metafile, Graphics, and many others). Potential problem: The described setup has its cons. For example, if you develop in Windows and you have projects that use the original System.Drawing.Common, you might encounter conflicts with Aspose.Slides types. Solution: You can use extern alias to resolve the problem. Aspose.Slides for .NET6+ CrossPlatform requires Linux x86_x64 with GLIBC 2.23 and higher for Linux systems. CentOS 7 GLIBC version is 2.14 and it is not supported. To use Aspose.Slides under CentOS 7 or other systems (like Alpine) that do not meet this requirement, please get Aspose.Slides for .NETStandard.
Install
dotnet add package Aspose.Slides.NET6.CrossPlatform --version 26.3.0
Install-Package Aspose.Slides.NET6.CrossPlatform -Version 26.3.0
<PackageReference Include="Aspose.Slides.NET6.CrossPlatform" Version="26.3.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.