Frequently Asked Questions
Common questions about OfficeIMO, PSWriteOffice, licensing, and technical details.
General
Does OfficeIMO require Microsoft Office to be installed?
No. OfficeIMO works entirely with Open XML standards and does not require Microsoft Office, COM automation, or any Office interop assemblies. It runs on any platform where .NET is available.
"]What .NET versions are supported?
OfficeIMO targets .NET 8.0, .NET 10.0, .NET Standard 2.0, and .NET Framework 4.7.2. This means it works with .NET Core, .NET 5+, and legacy .NET Framework projects.
"]Is OfficeIMO free for commercial use?
Yes. The OfficeIMO packages themselves are published under the MIT License. However, some optional package families build on third-party dependencies with their own upstream terms, so commercial teams should also review our Third-Party Dependencies page during OSS approval.
"]How does OfficeIMO compare to Aspose or GemBox?
OfficeIMO is open source and free (MIT license), while Aspose and GemBox are commercial products costing $890–$999+ per developer per year. OfficeIMO also offers unique features like a PowerShell module, Markdown library, typed CSV workflows, and NativeAOT support. See our detailed comparison.
"]Can I use OfficeIMO in a Docker container or CI/CD pipeline?
Absolutely. Since OfficeIMO has no COM dependencies and runs on .NET, it works perfectly in Linux containers, GitHub Actions, Azure DevOps, and any CI/CD environment. No special fonts or display servers needed.
"]What is PSWriteOffice?
PSWriteOffice is a PowerShell module that wraps the OfficeIMO .NET libraries. It provides 150+ cmdlets and DSL aliases for creating Office documents from PowerShell scripts without writing C#. Install it with Install-Module PSWriteOffice.
Does OfficeIMO support reading existing documents?
Yes. All core libraries (Word, Excel, PowerPoint) support both creating new documents and loading/editing existing ones. The OfficeIMO.Reader package provides a unified extraction API across all formats for AI ingestion and search indexing.
"]Is NativeAOT compilation supported?
Yes. The CSV and Markdown packages are fully AOT/trimming-safe. The Word, Excel, and PowerPoint packages are AOT-aware and work in trimmed scenarios with appropriate configuration.
"]Technical
What are the dependencies?
The core Office document packages are built on DocumentFormat.OpenXml, while image- and converter-oriented packages also use components such as SixLabors.ImageSharp, AngleSharp, and QuestPDF depending on the feature area. The Markdown and CSV core packages stay dependency-light. See the Third-Party Dependencies page for the package-by-package breakdown and upstream license notes.
"]Can I convert Word documents to PDF?
Yes. The OfficeIMO.Word.Pdf converter package supports Word-to-PDF conversion without Office. There are also converters for Word-to-HTML and Word-to-Markdown.
"]Is thread safety supported?
OfficeIMO.Excel supports parallel execution for bulk operations like AutoFit and bulk writes. Each document instance is independent and can be used on separate threads. Concurrent access to a single document instance is not supported.
"]