devexpress-office-file-api-ai-powered-extensions

Proofread, translate, and summarize Word, PDF, and PowerPoint documents using language models in .NET.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/AleksaRistic216/dotnet-playground --skill devexpress-office-file-api-ai-powered-extensions-aleksaristic216
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devexpress-office-file-api-ai-powered-extensions
Source: https://github.com/AleksaRistic216/dotnet-playground/tree/main/.github/skills/office-file-api/devexpress-office-file-api-ai-powered-extensions
Command: npx skills add https://github.com/AleksaRistic216/dotnet-playground --skill devexpress-office-file-api-ai-powered-extensions-aleksaristic216

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Adding AI-driven language operations like proofreading, translation, summarization, and contextual Q&A to .NET document processing workflows normally requires custom integration between LLM providers and document engines. This Skill provides the DevExpress AI-Powered Extensions for Office File API, which connect any IChatClient-compatible model (Azure OpenAI, OpenAI, Ollama, Gemini, ONNX) directly to Word, PDF, and PowerPoint processing. ## Core Features & Use Cases - Proofread and Translate Documents: Apply grammar, spelling, and style corrections or translate entire documents, specific paragraphs, slides, or PDF page regions while preserving formatting. - Summarize and Ask AI (RAG): Generate abstractive or extractive summaries and answer natural language questions about document content using retrieval-augmented generation. - Multi-Provider Support: Register Azure OpenAI, OpenAI, Ollama, Google Gemini, ONNX Runtime, or AI Foundry Local through the Microsoft.Extensions.AI abstraction in console or ASP.NET Core apps. - Use Case: A developer needs to translate a German contract PDF into English on a server. They load the PDF with PdfDocumentProcessor, call TranslateAsync with the target culture, receive the translated text, and render it onto a new page. ## Quick Start Ask the AI to set up the DevExpress AI document processing service with your chosen provider and proofread a Word document, then save the corrected result.

Frequently Asked Questions about devexpress-office-file-api-ai-powered-extensions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate a Word document with AI in .NET?

Load the document with RichEditDocumentServer, create an IAIDocProcessingService from the DevExpress AI container, and call TranslateAsync with a DocumentRange and target CultureInfo such as de-DE. The translation is applied in-place and formatting is preserved before saving.

How do I proofread a PowerPoint presentation programmatically?

Load the .pptx file into the DevExpress Presentation class and call ProofreadAsync on the whole presentation or a specific Slide with a CultureInfo. Corrections for spelling, grammar, and style are applied in-place, then saved with SaveDocument in Pptx format.

Which AI providers work with DevExpress AI document processing?

Any IChatClient implementation works, including Azure OpenAI, OpenAI, Ollama for self-hosted models, Google Gemini via Semantic Kernel, ONNX Runtime, and AI Foundry Local. The extensions follow a bring-your-own-key model with no DevExpress-hosted LLM included.

Does PDF translation modify the PDF file in place?

No. TranslateAsync for PDF returns the translated content as a string rather than modifying the document. You must render the returned text onto a page yourself using PdfGraphics, unlike Word and PowerPoint translations which are applied in-place.

Why does PDF translation return an empty string?

The PDF likely contains only images or scanned content with no extractable text layer. The AI PDF extensions process text content only and ignore images, annotations, comments, and form field values.

What .NET versions support DevExpress AI-Powered Extensions?

The extensions require .NET 8 or later, or .NET Framework 4.7.2. All DevExpress packages in the project must share the exact same version, and a valid DevExpress Universal or Office File API subscription is required.