Set up your AI agent

Give your coding agent the right documentation and project instructions for Aspose.Slides.

1. Connect your agent

Context7 lets your agent look up documentation while you work. Choose your agent, add the connection, then restart or reload it.

Claude Code

Merge this configuration into .mcp.json at the root of your project. Approve the server when Claude Code asks.

{
  "mcpServers": {
    "context7": {
      "type": "http",
      "url": "https://mcp.context7.com/mcp"
    }
  }
}

Claude Code connection guide

Cursor

Use the install button and review the connection, or merge this configuration into .cursor/mcp.json in your project.

Add to Cursor

{
  "mcpServers": {
    "context7": {
      "url": "https://mcp.context7.com/mcp"
    }
  }
}

Cursor connection guide

VS Code

In VS Code, use the install button and review the connection. For the current Copilot harness, merge this configuration into ~/.copilot/mcp-config.json.

Add to VS Code

{
  "mcpServers": {
    "context7": {
      "type": "http",
      "url": "https://mcp.context7.com/mcp",
      "tools": [
        "resolve-library-id",
        "query-docs"
      ]
    }
  }
}

VS Code connection guide

Codex

Merge this configuration into ~/.codex/config.toml. Keep any existing settings and server entries.

[mcp_servers.context7]
url = "https://mcp.context7.com/mcp"

Codex connection guide

The public connection can be used without a key. If Context7 asks you to sign in or you reach a usage limit, follow its authentication instructions.

2. Add your platform instructions

Choose the binding your project uses. Keep .NET and Java bindings separate, even when they use the same programming language.

Merge the instructions into your existing project file. Use AGENTS.md for Codex or VS Code, CLAUDE.md for Claude Code, or place aspose-slides.mdc in .cursor/rules/ for Cursor.

.NET

SDK for C# and other .NET languages.

Read the instructions
# Aspose.Slides for .NET

Use these instructions for this platform only. Read the project's existing instructions and dependency files first. Keep its current package version unless the task requires a change. Confirm API names against this platform's documentation; bindings are not interchangeable.

## Setup

Install the NuGet package `Aspose.Slides.NET` for your project's target framework and operating system. Use the platform-specific instructions for native dependencies and fonts. C# types are in `Aspose.Slides`; output formats are in `Aspose.Slides.Export`. Dispose each `Presentation`, normally with a `using` block.

## Install for a local test

In a new .NET 8 console project, the verified package command is:

```sh
dotnet add package Aspose.Slides.NET --version 26.10.0
```

These pinned versions reproduce the example below. Preserve an existing project's dependency choices unless the user asks to change them.

## Minimal example

After installation, run this as `Program.cs` in your configured project. It creates `hello.pptx` in the working directory. Use a scratch directory so an existing file is not replaced.

```csharp
using Aspose.Slides;
using Aspose.Slides.Export;

using (var presentation = new Presentation())
{
    var slide = presentation.Slides[0];
    var shape = slide.Shapes.AddAutoShape(ShapeType.Rectangle, 50, 50, 500, 80);
    shape.AddTextFrame("Hello, Aspose.Slides!");
    presentation.Save("hello.pptx", SaveFormat.Pptx);
}
```

Verified on 2026-11-18: Windows x64, .NET 8, Aspose.Slides.NET 26.10.0. The program ran and the saved file contained one slide with the expected text. This evaluation-mode check does not prove licensed output or other operating systems.

## License

Evaluation mode is suitable for a local smoke test and can add watermarks or other limits. If the user supplies a valid license, follow the [licensing guide](https://docs.aspose.com/slides/net/licensing/) before creating presentations. Read the license from a private local location accessible to the process. Never put license contents, keys, or personal paths in instructions, source control, or logs.

## Verify the change

Before expanding a change, create a small presentation, save it to a new file, and open the result. Check the requested content, slide count, and formatting. Build and run the exact code against the installed package; report any missing runtime or dependency instead of claiming it was tested.

Keep input files local unless the user permits sharing them. Write output to a new file and preserve the original. Report what ran, the versions used, and any checks that remain.

## Sources

- [Documentation](https://docs.aspose.com/slides/net/)
- [API reference](https://reference.aspose.com/slides/net/)
- [Installation](https://docs.aspose.com/slides/net/installation/)
- [Licensing](https://docs.aspose.com/slides/net/licensing/)

Documentation · API reference · Installation guide

Download .NET documentation English plain text

Java

SDK for Java applications.

Read the instructions
# Aspose.Slides for Java

Use these instructions for this platform only. Read the project's existing instructions and dependency files first. Keep its current package version unless the task requires a change. Confirm API names against this platform's documentation; bindings are not interchangeable.

## Setup

Use `com.aspose:aspose-slides` from [Aspose's Maven repository](https://releases.aspose.com/java/repo/) with the documented `jdk8` classifier. Match the project's JDK and dependency version. Import types from `com.aspose.slides`. Dispose each `Presentation` in a `finally` block. Check fonts on the machine that will render the slides.

## Minimal example

After installation, run this as `Starter.java` in your configured project. It creates `hello.pptx` in the working directory. Use a scratch directory so an existing file is not replaced.

```java
import com.aspose.slides.Presentation;
import com.aspose.slides.SaveFormat;
import com.aspose.slides.ShapeType;

public class Starter {
    public static void main(String[] args) {
        Presentation presentation = new Presentation();
        try {
            presentation.getSlides().get_Item(0).getShapes()
                .addAutoShape(ShapeType.Rectangle, 50, 50, 500, 80)
                .getTextFrame().setText("Hello, Aspose.Slides!");
            presentation.save("hello.pptx", SaveFormat.Pptx);
        } finally {
            presentation.dispose();
        }
    }
}
```

Verified on 2026-11-18: Windows x64, JDK 21, Aspose.Slides for Java 26.10 (jdk8). The program ran and the saved file contained one slide with the expected text. This evaluation-mode check does not prove licensed output or other operating systems.

## License

Evaluation mode is suitable for a local smoke test and can add watermarks or other limits. If the user supplies a valid license, follow the [licensing guide](https://docs.aspose.com/slides/java/licensing/) before creating presentations. Read the license from a private local location accessible to the process. Never put license contents, keys, or personal paths in instructions, source control, or logs.

## Verify the change

Before expanding a change, create a small presentation, save it to a new file, and open the result. Check the requested content, slide count, and formatting. Build and run the exact code against the installed package; report any missing runtime or dependency instead of claiming it was tested.

Keep input files local unless the user permits sharing them. Write output to a new file and preserve the original. Report what ran, the versions used, and any checks that remain.

## Sources

- [Documentation](https://docs.aspose.com/slides/java/)
- [API reference](https://reference.aspose.com/slides/java/)
- [Installation](https://docs.aspose.com/slides/java/installation/)
- [Licensing](https://docs.aspose.com/slides/java/licensing/)

Documentation · API reference · Installation guide

Download Java documentation English plain text

Python via .NET

Python SDK using the .NET-based binding.

Read the instructions
# Aspose.Slides for Python via .NET

Use these instructions for this platform only. Read the project's existing instructions and dependency files first. Keep its current package version unless the task requires a change. Confirm API names against this platform's documentation; bindings are not interchangeable.

## Setup

Use an isolated Python environment and the `aspose.slides` package. Import it as `aspose.slides`, and use its Python properties and enum names. Use a `with` block for `Presentation`. Follow the operating-system dependency instructions; do not substitute the Python via Java package.

## Install for a local test

With an isolated Python environment active, install the verified version:

```sh
python -m pip install aspose.slides==26.10.0
```

These pinned versions reproduce the example below. Preserve an existing project's dependency choices unless the user asks to change them.

## Minimal example

After installation, run this as `starter.py` in your configured project. It creates `hello.pptx` in the working directory. Use a scratch directory so an existing file is not replaced.

```python
import aspose.slides as slides

with slides.Presentation() as presentation:
    shape = presentation.slides[0].shapes.add_auto_shape(
        slides.ShapeType.RECTANGLE, 50, 50, 500, 80
    )
    shape.text_frame.text = "Hello, Aspose.Slides!"
    presentation.save("hello.pptx", slides.export.SaveFormat.PPTX)
```

Verified on 2026-11-18: Windows x64, Python 3.12, aspose.slides 26.10.0. The program ran and the saved file contained one slide with the expected text. This evaluation-mode check does not prove licensed output or other operating systems.

## License

Evaluation mode is suitable for a local smoke test and can add watermarks or other limits. If the user supplies a valid license, follow the [licensing guide](https://docs.aspose.com/slides/python-net/licensing/) before creating presentations. Read the license from a private local location accessible to the process. Never put license contents, keys, or personal paths in instructions, source control, or logs.

## Verify the change

Before expanding a change, create a small presentation, save it to a new file, and open the result. Check the requested content, slide count, and formatting. Build and run the exact code against the installed package; report any missing runtime or dependency instead of claiming it was tested.

Keep input files local unless the user permits sharing them. Write output to a new file and preserve the original. Report what ran, the versions used, and any checks that remain.

## Sources

- [Documentation](https://docs.aspose.com/slides/python-net/)
- [API reference](https://reference.aspose.com/slides/python-net/)
- [Installation](https://docs.aspose.com/slides/python-net/installation/)
- [Licensing](https://docs.aspose.com/slides/python-net/licensing/)

Documentation · API reference · Installation guide

Download Python via .NET documentation English plain text

Python via Java

Python SDK using the Java-based binding.

Read the instructions
# Aspose.Slides for Python via Java

Use these instructions for this platform only. Read the project's existing instructions and dependency files first. Keep its current package version unless the task requires a change. Confirm API names against this platform's documentation; bindings are not interchangeable.

## Setup

Use an isolated Python environment, `aspose-slides-java`, JPype, and a matching Java runtime. Set `JAVA_HOME` to the intended JDK so JPype does not select an older installed runtime. Import `asposeslides` before starting the JVM; import API types from `asposeslides.api` after it starts. Dispose presentations before shutting down the JVM. Treat JVM startup and shutdown as process-wide operations; do not copy the Python via .NET API.

## Install for a local test

With an isolated Python environment active, install the verified versions:

```sh
python -m pip install aspose-slides-java==26.6.0 JPype1==1.7.1
```

These pinned versions reproduce the example below. Preserve an existing project's dependency choices unless the user asks to change them.

## Minimal example

After installation, run this as `starter.py` in your configured project. It creates `hello.pptx` in the working directory. Use a scratch directory so an existing file is not replaced.

```python
import jpype
import asposeslides

jpype.startJVM()
try:
    from asposeslides.api import Presentation, SaveFormat, ShapeType

    presentation = Presentation()
    try:
        shape = presentation.getSlides().get_Item(0).getShapes().addAutoShape(
            ShapeType.Rectangle, 50, 50, 500, 80
        )
        shape.getTextFrame().setText("Hello, Aspose.Slides!")
        presentation.save("hello.pptx", SaveFormat.Pptx)
    finally:
        presentation.dispose()
finally:
    jpype.shutdownJVM()
```

Verified on 2026-11-18: Windows x64, Python 3.12, JDK 21, aspose-slides-java 26.6.0, JPype1 1.7.1. The program ran and the saved file contained one slide with the expected text. This evaluation-mode check does not prove licensed output or other operating systems.

## License

Evaluation mode is suitable for a local smoke test and can add watermarks or other limits. If the user supplies a valid license, follow the [licensing guide](https://docs.aspose.com/slides/python-java/licensing/) before creating presentations. Read the license from a private local location accessible to the process. Never put license contents, keys, or personal paths in instructions, source control, or logs.

## Verify the change

Before expanding a change, create a small presentation, save it to a new file, and open the result. Check the requested content, slide count, and formatting. Build and run the exact code against the installed package; report any missing runtime or dependency instead of claiming it was tested.

Keep input files local unless the user permits sharing them. Write output to a new file and preserve the original. Report what ran, the versions used, and any checks that remain.

## Sources

- [Documentation](https://docs.aspose.com/slides/python-java/)
- [API reference](https://reference.aspose.com/slides/python-java/)
- [Installation](https://docs.aspose.com/slides/python-java/installation/)
- [Licensing](https://docs.aspose.com/slides/python-java/licensing/)

Documentation · API reference · Installation guide

Download Python via Java documentation English plain text

C++

Native C++ SDK.

Read the instructions
# Aspose.Slides for C++

Use these instructions for this platform only. Read the project's existing instructions and dependency files first. Keep its current package version unless the task requires a change. Confirm API names against this platform's documentation; bindings are not interchangeable.

## Setup

Choose the C++ package for the target operating system and architecture. On Windows, add the `Aspose.Slides.Cpp` package through Visual Studio's NuGet Package Manager; Linux uses the native download and its CMake configuration. Include the documented presentation and export headers, and link the matching Aspose.Slides and CodePorting libraries. A header-only compile does not prove the program can link or run.

## Minimal example

After installation, run this as `starter.cpp` in your configured project. It creates `hello.pptx` in the working directory. Use a scratch directory so an existing file is not replaced.

```cpp
#include <DOM/Presentation.h>
#include <DOM/SlideCollection.h>
#include <DOM/Slide.h>
#include <DOM/ShapeCollection.h>
#include <DOM/AutoShape.h>
#include <DOM/ShapeType.h>
#include <Export/SaveFormat.h>

int main()
{
    auto presentation = System::MakeObject<Aspose::Slides::Presentation>();
    auto shape = presentation->get_Slides()->idx_get(0)->get_Shapes()->AddAutoShape(
        Aspose::Slides::ShapeType::Rectangle, 50.0f, 50.0f, 500.0f, 80.0f);
    shape->AddTextFrame(u"Hello, Aspose.Slides!");
    presentation->Save(u"hello.pptx", Aspose::Slides::Export::SaveFormat::Pptx);
    presentation->Dispose();
    return 0;
}
```

Verified on 2026-11-18: Windows x64, MSVC v142, Aspose.Slides.Cpp and CodePorting 26.8.0. The program ran and the saved file contained one slide with the expected text. This evaluation-mode check does not prove licensed output or other operating systems.

## License

Evaluation mode is suitable for a local smoke test and can add watermarks or other limits. If the user supplies a valid license, follow the [licensing guide](https://docs.aspose.com/slides/cpp/licensing/) before creating presentations. Read the license from a private local location accessible to the process. Never put license contents, keys, or personal paths in instructions, source control, or logs.

## Verify the change

Before expanding a change, create a small presentation, save it to a new file, and open the result. Check the requested content, slide count, and formatting. Build and run the exact code against the installed package; report any missing runtime or dependency instead of claiming it was tested.

Keep input files local unless the user permits sharing them. Write output to a new file and preserve the original. Report what ran, the versions used, and any checks that remain.

## Sources

- [Documentation](https://docs.aspose.com/slides/cpp/)
- [API reference](https://reference.aspose.com/slides/cpp/)
- [Installation](https://docs.aspose.com/slides/cpp/installation/)
- [Licensing](https://docs.aspose.com/slides/cpp/licensing/)

Documentation · API reference · Installation guide

Download C++ documentation English plain text

Node.js via Java

Node.js SDK using the Java-based binding.

Read the instructions
# Aspose.Slides for Node.js via Java

Use these instructions for this platform only. Read the project's existing instructions and dependency files first. Keep its current package version unless the task requires a change. Confirm API names against this platform's documentation; bindings are not interchangeable.

## Setup

Use `aspose.slides.via.java` with the JDK and native build tools in the installation guide. Import the package with CommonJS `require`. This binding uses Java-style accessors such as `getSlides`; do not copy the Node.js via .NET API. Dispose each presentation. The JVM can keep a command-line process alive; follow the guide's standalone-program shutdown instructions without forcing a server to exit.

## Install for a local test

From a new npm project with the documented Java and native build prerequisites available, install the verified version:

```sh
npm install aspose.slides.via.java@26.11.0
```

These pinned versions reproduce the example below. Preserve an existing project's dependency choices unless the user asks to change them.

## Minimal example

After installation, run this standalone program as `starter.cjs` from your project folder. It creates `hello.pptx`. Use a scratch project so an existing file is not replaced.

```javascript
const slides = require("aspose.slides.via.java");

const presentation = new slides.Presentation();
try {
    const shape = presentation.getSlides().get_Item(0).getShapes().addAutoShape(
        slides.ShapeType.Rectangle, 50, 50, 500, 80
    );
    shape.getTextFrame().setText("Hello, Aspose.Slides!");
    presentation.save("hello.pptx", slides.SaveFormat.Pptx);
} finally {
    presentation.dispose();
}
// This is a standalone command-line program.
process.exit(0);
```

Verified on 2026-11-18: Windows x64, Node.js 22.23.5, JDK 21, aspose.slides.via.java 26.11.0. The program ran and the saved file contained one slide with the expected text. This evaluation-mode check does not prove licensed output or other operating systems.

## License

Evaluation mode is suitable for a local smoke test and can add watermarks or other limits. If the user supplies a valid license, follow the [licensing guide](https://docs.aspose.com/slides/nodejs-java/licensing/) before creating presentations. Read the license from a private local location accessible to the process. Never put license contents, keys, or personal paths in instructions, source control, or logs.

## Verify the change

Before expanding a change, create a small presentation, save it to a new file, and open the result. Check the requested content, slide count, and formatting. Build and run the exact code against the installed package; report any missing runtime or dependency instead of claiming it was tested.

Keep input files local unless the user permits sharing them. Write output to a new file and preserve the original. Report what ran, the versions used, and any checks that remain.

## Sources

- [Documentation](https://docs.aspose.com/slides/nodejs-java/)
- [API reference](https://reference.aspose.com/slides/nodejs-java/)
- [Installation](https://docs.aspose.com/slides/nodejs-java/installation/)
- [Licensing](https://docs.aspose.com/slides/nodejs-java/licensing/)

Documentation · API reference · Installation guide

Download Node.js via Java documentation English plain text

Node.js via .NET

Node.js SDK using the .NET-based binding.

Read the instructions
# Aspose.Slides for Node.js via .NET

Use these instructions for this platform only. Read the project's existing instructions and dependency files first. Keep its current package version unless the task requires a change. Confirm API names against this platform's documentation; bindings are not interchangeable.

## Setup

Use `aspose.slides.via.net`. Follow the complete installation guide, including its supported Node.js version, .NET SDK, `edge-js` override, and NuGet dependency restore. Import with CommonJS `require`. Run from the project directory containing the package's native files. This binding uses camelCase members and indexed collection methods. Dispose each presentation. Consult the .NET API reference together with the Node.js binding examples.

## Install for a local test

From a new npm project using Node.js 22 or 24, apply the bridge override before installing the verified package:

```sh
npm pkg set overrides.edge-js=26.1.0
npm install aspose.slides.via.net@24.4.0
```

These pinned versions reproduce the example below. Preserve an existing project's dependency choices unless the user asks to change them.

Before running the example, complete the one-time .NET dependency restore in the [installation guide](https://docs.aspose.com/slides/nodejs-net/installation/#restore-the-net-dependencies). The npm install alone is not sufficient.

## Minimal example

After installation, run this standalone program as `starter.cjs` from your project folder. It creates `hello.pptx`. Use a scratch project so an existing file is not replaced.

```javascript
const slides = require("aspose.slides.via.net");

const presentation = new slides.Presentation();
try {
    const shape = presentation.slides.get(0).shapes.addAutoShape(
        slides.ShapeType.Rectangle, 50, 50, 500, 80
    );
    shape.addTextFrame("Hello, Aspose.Slides!");
    presentation.save("hello.pptx", slides.SaveFormat.Pptx);
} finally {
    presentation.dispose();
}
```

Verified on 2026-11-18: Windows x64, Node.js 22.23.5, aspose.slides.via.net 24.4.0, edge-js 26.1.0, .NET dependency restore from the installation guide. The program ran and the saved file contained one slide with the expected text. This evaluation-mode check does not prove licensed output or other operating systems.

## License

Evaluation mode is suitable for a local smoke test and can add watermarks or other limits. If the user supplies a valid license, follow the [licensing guide](https://docs.aspose.com/slides/nodejs-net/licensing/) before creating presentations. Read the license from a private local location accessible to the process. Never put license contents, keys, or personal paths in instructions, source control, or logs.

## Verify the change

Before expanding a change, create a small presentation, save it to a new file, and open the result. Check the requested content, slide count, and formatting. Build and run the exact code against the installed package; report any missing runtime or dependency instead of claiming it was tested.

Keep input files local unless the user permits sharing them. Write output to a new file and preserve the original. Report what ran, the versions used, and any checks that remain.

## Sources

- [Documentation](https://docs.aspose.com/slides/nodejs-net/)
- [API reference (.NET types)](https://reference.aspose.com/slides/net/)
- [Installation](https://docs.aspose.com/slides/nodejs-net/installation/)
- [Licensing](https://docs.aspose.com/slides/nodejs-net/licensing/)

Documentation · API reference · Installation guide

Download Node.js via .NET documentation English plain text

PHP via Java

PHP SDK using a Java bridge.

Read the instructions
# Aspose.Slides for PHP via Java

Use these instructions for this platform only. Read the project's existing instructions and dependency files first. Keep its current package version unless the task requires a change. Confirm API names against this platform's documentation; bindings are not interchangeable.

## Setup

Install `aspose/slides` with Composer and configure the documented PHP/Java Bridge, PHP version, and Tomcat 9. On Linux, supply the JVM font libraries and fonts; the verified Ubuntu setup included fontconfig, DejaVu fonts, and `libharfbuzz0b`. Include the bridge and the package's `lib/aspose.slides.php` wrapper; Composer autoloading alone is insufficient. Use the `aspose\slides` namespace. Output and license paths must be accessible to the Java process. Dispose each presentation in a `finally` block.

## Install for a local test

With the bridge and Tomcat prerequisites from the installation guide configured, run this in a new Composer project:

```sh
composer require aspose/slides:26.9 --no-interaction --no-progress
```

This pinned version reproduces the example below. Preserve an existing project's dependency choices unless the user asks to change them. Finish the guide's JAR deployment and PHP 8 bridge-client replacement before running the example. Composer alone does not configure Tomcat.

## Minimal example

Save this as `starter.php` in the Composer project. Tomcat and PHP must see the same project directory. Use a scratch project so an existing `hello.pptx` is not replaced.

```php
<?php
require_once("http://localhost:8080/JavaBridge/java/Java.inc");
require_once(__DIR__ . "/vendor/aspose/slides/lib/aspose.slides.php");

use aspose\slides\Presentation;
use aspose\slides\SaveFormat;
use aspose\slides\ShapeType;

$presentation = new Presentation();
try {
    $shape = $presentation->getSlides()->get_Item(0)->getShapes()->addAutoShape(
        ShapeType::Rectangle, 50, 50, 500, 80
    );
    $shape->getTextFrame()->setText("Hello, Aspose.Slides!");
    $presentation->save(__DIR__ . "/hello.pptx", SaveFormat::Pptx);
} finally {
    $presentation->dispose();
}
```

With Tomcat running locally, execute:

```sh
php -d allow_url_include=On starter.php
```

Verified on 2026-11-18: Ubuntu 24.04 x64, PHP 8.3.6, OpenJDK 21.0.13, Tomcat 9.0.122, PHP/Java Bridge 7.2.1, and aspose/slides 26.9. The program ran and the saved file contained one slide with the expected text. This evaluation-mode check does not prove licensed output or other operating systems.

## License

Evaluation mode is suitable for a local smoke test and can add watermarks or other limits. If the user supplies a valid license, follow the [licensing guide](https://docs.aspose.com/slides/php-java/licensing/) before creating presentations. Read the license from a private local location accessible to the process. Never put license contents, keys, or personal paths in instructions, source control, or logs.

## Verify the change

Before expanding a change, create a small presentation, save it to a new file, and open the result. Check the requested content, slide count, and formatting. Build and run the exact code against the installed package; report any missing runtime or dependency instead of claiming it was tested.

Keep input files local unless the user permits sharing them. Write output to a new file and preserve the original. Report what ran, the versions used, and any checks that remain.

## Sources

- [Documentation](https://docs.aspose.com/slides/php-java/)
- [API reference](https://reference.aspose.com/slides/php-java/)
- [Installation](https://docs.aspose.com/slides/php-java/installation/)
- [Licensing](https://docs.aspose.com/slides/php-java/licensing/)

Documentation · API reference · Installation guide

Download PHP via Java documentation English plain text

Android via Java

SDK for Android Java applications.

Read the instructions
# Aspose.Slides for Android via Java

Use these instructions for this platform only. Read the project's existing instructions and dependency files first. Keep its current package version unless the task requires a change. Confirm API names against this platform's documentation; bindings are not interchangeable.

## Setup

Use the Android-specific artifact and `android.via.java` classifier from the installation guide. Do not substitute the desktop Java artifact. Confirm that the selected release has an Android package. Import `com.aspose.slides` types, run on an Android device or emulator, and save test output in app-private storage. Dispose presentations when finished.

## License

Evaluation mode is suitable for a local smoke test and can add watermarks or other limits. If the user supplies a valid license, follow the [licensing guide](https://docs.aspose.com/slides/androidjava/licensing/) before creating presentations. Read the license from a private local location accessible to the process. Never put license contents, keys, or personal paths in instructions, source control, or logs.

## Verify the change

Before expanding a change, create a small presentation, save it to a new file, and open the result. Check the requested content, slide count, and formatting. Build and run the exact code against the installed package; report any missing runtime or dependency instead of claiming it was tested.

Keep input files local unless the user permits sharing them. Write output to a new file and preserve the original. Report what ran, the versions used, and any checks that remain.

## Sources

- [Documentation](https://docs.aspose.com/slides/androidjava/)
- [API reference](https://reference.aspose.com/slides/androidjava/)
- [Installation](https://docs.aspose.com/slides/androidjava/install-aspose-slides-for-android-via-java/)
- [Licensing](https://docs.aspose.com/slides/androidjava/licensing/)

Documentation · API reference · Installation guide

Download Android via Java documentation English plain text

JasperReports

PowerPoint export integration for JasperReports.

Read the instructions
# Aspose.Slides for JasperReports

Use these instructions for this platform only. Read the project's existing instructions and dependency files first. Keep its current package version unless the task requires a change. Confirm API names against this platform's documentation; bindings are not interchangeable.

## Setup

Choose the exporter library that matches your JasperReports version. Follow the installation or JasperServer integration guide for your deployment. Use the `com.aspose.slides.jasperreports` exporter classes described there; the standalone Java SDK is a different product. Keep existing report definitions and deployment configuration as the starting point.

## License

Start with the documented evaluation mode on a test instance. If the user supplies a valid license, apply it through the [integration's licensing procedure](https://docs.aspose.com/slides/jasperreports/licensing/). Keep the license private and accessible only to the required service account; do not paste its contents into source control, instructions, or logs. Evaluation exports can contain watermarks.

## Verify the change

Use a small report in a test application or JasperServer instance. Export it to PowerPoint and open the result. Check report text, page layout, and images. Record the library and report-server versions; do not claim a server test from a Java-only compile.

Keep input files local unless the user permits sharing them. Write output to a new file and preserve the original. Report what ran, the versions used, and any checks that remain.

## Sources

- [Documentation](https://docs.aspose.com/slides/jasperreports/)
- [Installation](https://docs.aspose.com/slides/jasperreports/installing-aspose-slides-for-jasperreports/)
- [Licensing](https://docs.aspose.com/slides/jasperreports/licensing/)

Documentation · Installation guide

Download JasperReports documentation English plain text

Reporting Services

PowerPoint export extension for reporting servers.

Read the instructions
# Aspose.Slides for Reporting Services

Use these instructions for this platform only. Read the project's existing instructions and dependency files first. Keep its current package version unless the task requires a change. Confirm API names against this platform's documentation; bindings are not interchangeable.

## Setup

Identify the reporting server product and version before choosing the installation route. Follow the matching SSRS or Power BI Report Server instructions. This is a reporting extension, so no application import or standalone `Presentation` sample is required. Keep deployment changes scoped to a test instance until an administrator approves the production change.

## License

Start with the documented evaluation mode on a test instance. If the user supplies a valid license, apply it through the [integration's licensing procedure](https://docs.aspose.com/slides/reportingservices/license-aspose-slides-for-reporting-services/). Keep the license private and accessible only to the required service account; do not paste its contents into source control, instructions, or logs. Evaluation exports can contain watermarks.

## Verify the change

Export a small report through the installed PowerPoint rendering extension on a test server. Open the result and check report content and layout. Record the server and extension versions; do not treat a configuration edit as a completed export test.

Keep input files local unless the user permits sharing them. Write output to a new file and preserve the original. Report what ran, the versions used, and any checks that remain.

## Sources

- [Documentation](https://docs.aspose.com/slides/reportingservices/)
- [Installation](https://docs.aspose.com/slides/reportingservices/installation/)
- [Licensing](https://docs.aspose.com/slides/reportingservices/license-aspose-slides-for-reporting-services/)

Documentation · Installation guide

Download Reporting Services documentation English plain text

SharePoint

Presentation conversion integration for SharePoint.

Read the instructions
# Aspose.Slides for SharePoint

Use these instructions for this platform only. Read the project's existing instructions and dependency files first. Keep its current package version unless the task requires a change. Confirm API names against this platform's documentation; bindings are not interchangeable.

## Setup

Check the documented SharePoint version and farm requirements before planning installation. The documentation describes a farm solution with deployment and site-collection activation; do not assume it is a SharePoint Online add-in. This integration does not require a standalone SDK import. Use a test site collection and administrator-approved deployment steps.

## License

Start with the documented evaluation mode on a test instance. If the user supplies a valid license, apply it through the [integration's licensing procedure](https://docs.aspose.com/slides/sharepoint/license-aspose-slides-for-sharepoint/). Keep the license private and accessible only to the required service account; do not paste its contents into source control, instructions, or logs. Evaluation exports can contain watermarks.

## Verify the change

Convert a small presentation from a test document library using the installed feature. Open the result and check content and formatting. Record the SharePoint and integration versions; do not claim farm compatibility without testing the target environment.

Keep input files local unless the user permits sharing them. Write output to a new file and preserve the original. Report what ran, the versions used, and any checks that remain.

## Sources

- [Documentation](https://docs.aspose.com/slides/sharepoint/)
- [Installation](https://docs.aspose.com/slides/sharepoint/installation/)
- [Licensing](https://docs.aspose.com/slides/sharepoint/license-aspose-slides-for-sharepoint/)

Documentation · Installation guide

Download SharePoint documentation English plain text

3. Check the connection

Ask your agent:

Use Context7 to find the Aspose.Slides documentation for my platform. Explain how to create and save a presentation, and cite the source pages.

Check that it used the right platform and linked to Aspose documentation. Review and run generated code in your own environment.

Documentation downloads

For tools that accept files, download the complete English documentation, or use the smaller platform download above. These files contain the documentation pages; API reference links are provided separately. Large files may exceed your agent’s context limit.

Browse the documentation index