> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/uwp/get-started/samples/officetopdftest.md).

# OfficeToPDF

Sample C# code for using Apryse SDK to convert Office documents to PDF (including Word, Excel, PowerPoint and Publisher) without needing any external dependencies or MS Office licenses.

Sample C# code for using Apryse SDK to convert Office documents to PDF (including Word, Excel, PowerPoint and Publisher) without needing any external dependencies or MS Office licenses. Office to PDF conversion can be performed on a Linux or Windows server to automate Office-centric workflows, or entirely in the user's client (web browser, mobile device). The conversion functionality can be combined with our Viewer to display or annotate Office files (docx, xlsx, pptx) on all major platforms, including Web, Android, iOS, Xamarin, UWP, and Windows. Learn more about our [UWP SDK](/core/get-started/frameworks/dotnet.md) and [Office Document Conversion Library](https://apryse.com/products/core-sdk/office).

{% tabs %}
{% tab title="C#" %}
{% code lineNumbers="true" %}

```csharp
//
// Copyright (c) 2001-2020 by PDFTron Systems Inc. All Rights Reserved.
//

using System;
using System.IO;
using System.Threading.Tasks;
using Windows.Foundation;

using pdftron.PDF;
using pdftron.SDF;

using pdftron.Common;
using PDFNetUniversalSamples.ViewModels;

namespace PDFNetSamples
{
    /// <summary>
    ///---------------------------------------------------------------------------------------
    /// The following sample illustrates how to use the PDF::Convert utility class to convert 
    /// .docx files to PDF
    ///
    /// This conversion is performed entirely within the PDFNet and has *no* external or
    /// system dependencies
    ///
    /// Please contact us if you have any questions.	
    ///---------------------------------------------------------------------------------------
    /// </summary>

    public sealed class OfficeToPDFTest : Sample
    {
        public OfficeToPDFTest() :
            base("OfficeToPDF", "The following sample illustrates how to use the PDF::Convert utility class to convert .docx files to PDF")
        {
        }

        public override IAsyncAction RunAsync()
        {
            return Task.Run(new System.Action(async () =>
            {
                WriteLine("--------------------------------");
                WriteLine("Starting OfficeToPDF Test...");
                WriteLine("--------------------------------\n");

                try
                {
                    // first the one-line conversion method
                    await SimpleConvert("Fishermen.docx", "Fishermen.pdf");

                    // then the more flexible line-by-line conversion API
                    await FlexibleConvert("the_rime_of_the_ancient_mariner.docx", "the_rime_of_the_ancient_mariner.pdf");

                    // conversion of RTL content
                    await FlexibleConvert("factsheet_Arabic.docx", "factsheet_Arabic.pdf");
                }
                catch (Exception e)
                {
                    WriteLine("Unrecognized Exception: " + e.Message);
                }

                WriteLine("--------------------------------");
                WriteLine("Done OfficeToPDF Test.");
                WriteLine("--------------------------------\n");

            })).AsAsyncAction();
        }

        async Task<bool> SimpleConvert(String input_filename, String output_filename)
        {
            // Make sure all files exist
            if (!File.Exists(Path.Combine(InputPath, input_filename)))
            {
                WriteLine("File: " + input_filename + " not found!");
                return false;
            }

                // Start with a PDFDoc (the conversion destination)
                using (PDFDoc doc = new PDFDoc())
            {
                // perform the conversion with no optional parameters
                pdftron.PDF.Convert.OfficeToPDF(doc, Path.Combine(InputPath, input_filename), null);

                // save the result
                await doc.SaveAsync(Path.Combine(OutputPath, output_filename), SDFDocSaveOptions.e_linearized);

                WriteLine("Saved " + output_filename);

                await AddFileToOutputList(Path.Combine(OutputPath, output_filename));

                return true;
            }
        }

        async Task<bool> FlexibleConvert(String input_filename, String output_filename)
        {
            // Make sure all files exist
            if (!File.Exists(Path.Combine(InputPath,input_filename)))
            {                
                WriteLine("File: " + input_filename + " not found!");
                return false;
            }

            // Start with a PDFDoc (the conversion destination)
            using (PDFDoc doc = new PDFDoc())
            {
                // Instanciate convertion options
                OfficeToPDFOptions options = new OfficeToPDFOptions();

                // Smart Substitutions requires a plugin file, here we set the path to it 
                options.SetSmartSubstitutionPluginPath(
                    System.IO.Path.Combine(Windows.ApplicationModel.Package.Current.InstalledLocation.Path, "Resources"));
                
                // create a conversion object -- this sets things up but does not yet
                // perform any conversion logic.
                // in a multithreaded environment, this object can be used to monitor
                // the conversion progress and potentially cancel it as well
                DocumentConversion conversion = 
                    pdftron.PDF.Convert.StreamingPDFConversion(doc, Path.Combine(InputPath, input_filename), options);

                // actually perform the conversion
                // this particular method will not throw on conversion failure, but will
                // return an error status instead
                if (conversion.TryConvert() == DocumentConversionResult.e_document_conversion_success)
                {
                    var num_warnings = conversion.GetNumWarnings();

                    // print information about the conversion 
                    for (uint i = 0; i < num_warnings; ++i)
                    {
                        WriteLine("Warning: " + conversion.GetWarningString(i));
                    }

                    // save the result
                    await doc.SaveAsync(Path.Combine(OutputPath, output_filename), SDFDocSaveOptions.e_linearized);

                    WriteLine("Saved " + output_filename);

                    await AddFileToOutputList(Path.Combine(OutputPath, output_filename));

                    return true;
                }

                return false;
            }
        }
    }
}
```

{% endcode %}
{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apryse.com/uwp/get-started/samples/officetopdftest.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.