WPF DOCX Editor SDK

Hey all I am looking for this example within the plethora of demos you can download off your GitHub page. 

Image_1250_1757378670240

Am I just missing it? Is there a “everything and the kitchen sink” type of example code?


12 Replies

KG Kalaivannan Ganesan Syncfusion Team September 9, 2025 07:57 AM UTC

Hi David,

Our GitHub repository includes a variety of completed demos related to the WPF DOCX Editor SDK. These cover different features and use cases to help you get started quickly.

You can find the demos here: docx-editor-sdk-wpf-demos

Please go through the samples for more information. If you need help locating a specific feature or example, feel free to let us know.



DA David September 12, 2025 05:02 AM UTC

Seems when i load up the example it has 84-ish errors

Image_2646_1757653318974



DA David September 12, 2025 05:05 AM UTC

and all of these dependencies:

Image_2293_1757653535282



KG Kalaivannan Ganesan Syncfusion Team September 12, 2025 07:02 AM UTC

Hi David,

The errors are occurring because the required assemblies are not referenced in the demos.

To refer the assemblies, please follow the instructions below:
Since you have the DOCX Editor build, it includes the assemblies and dependent assemblies required for the SfRichTextRibbon and SfRichTextBoxAdv controls only. However, it does not contain assemblies for other controls and themes used in the shared demos.

You can refer to the assemblies available in the build for the DOCX Editor controls. For the remaining assemblies, you can download and use them via NuGet packages.

We’ve attached a video illustration showing how to refer to the assemblies from the build. Please refer to it for more information on handling assemblies for SfRichTextRibbon and SfRichTextBoxAdv.

For other controls and themes, kindly remove the existing references and use the corresponding NuGet packages instead.

As shown in the video, the DOCX Editor build includes only the assemblies required for its specific controls. Once referenced correctly, the assemblies will be resolved properly.


Attachment: Refer_Assemblies_from_DOCX_Editor_build_300f7e59.zip


DA David September 13, 2025 04:28 AM UTC

Thanks for the video.

I followed it but i still have yellow triangles?

Image_8880_1757737138056

Image_4217_1757737157828



Image_8277_1757737430909


But when i load up the project, even though those yellow triangles are gone it still fails at compiling.

Image_4358_1757737638420

What am i missing to do?




DA David September 14, 2025 03:34 AM UTC

Alright spent a few more hours and got the errors down to 11

Image_6917_1757820697915But I am still not able to get rid of those. All the dependencies are found except for Microsoft.VisualStudio.DesignTools.Extensibility in the syncfusion.richtextboxdemos.wpf_lib.csproj and syncfusion.samplebrowser.wpf_docxeditorsdk.csproj:

Image_4759_1757820823928



KG Kalaivannan Ganesan Syncfusion Team September 15, 2025 10:33 AM UTC

Hi David,

We are checking the reported issue and testing with both the assemblies from the build and the NuGet packages. We’re working to make the sample runnable with this setup and will share a complete update with you by 17th September 2025.



KG Kalaivannan Ganesan Syncfusion Team September 16, 2025 07:43 AM UTC

Hi David,

As mentioned earlier, we should use the SfRichTextBoxAdv and SfRichTextRibbon related assemblies from the DOCX Editor SDK build. For other controls, we should use the latest version of the NuGet packages.

To achieve this, please update the .props file (demos.common.props ) where the common assemblies are referenced. Specifically, we need to ensure that assemblies not included in the DOCX Editor SDK build are referenced via NuGet, while others continue to use DLLs.

Except for the following: ( Shared.WPF, Tools.WPF, License DLL),  all other assemblies should be referenced using NuGet packages.

You can refer to the .props file in the attached sample application for more details.


Similarly, please update the following .csproj files to reflect which assemblies should be referenced from the build and which should use NuGet packages:

samplebrowser/syncfusion.samplebrowser.wpf_docxeditorsdk.csproj

showcase/documenteditor/syncfusion.documenteditor.wpf.csproj

showcase/documenteditor/syncfusion.documenteditor.wpf_lib.csproj

We’ve attached the updated sample application, which demonstrates the correct usage of assemblies from the build and NuGet packages. Please refer to it for more information.

Additionally, we’ve included a video illustration showing how the assemblies are referenced and how the sample application runs. Kindly review it as well.


Attachment: docxeditorsdkwpfdemosmasterUpdated_30ddf514.7z


DA David September 18, 2025 06:46 PM UTC

I can confirm that its finally able to compile and run!

Thanks!



KG Kalaivannan Ganesan Syncfusion Team September 19, 2025 05:03 AM UTC

Thank you for the confirmation.

We’re glad to hear that everything is compiling and running smoothly now. Please feel free to reach out if you need assistance with anything else.



XH xiaoli hao replied to Kalaivannan Ganesan November 20, 2025 02:52 PM UTC

    hi, I downloaded the WPF DOCX Editor Demo program, but my VS is the 2019 version I have been modifying the configuration file for a day, but still cannot enable it

    Because I am using the Win7 operating system, I am currently unable to upgrade to Win10. Can you provide a separate example program for the net462 framework

Thank you very much!



KG Kalaivannan Ganesan Syncfusion Team November 21, 2025 05:46 AM UTC

Hi Xiaoli Hao,

We have created a simple WPF application using .NET Framework 4.6.2 with SfRichTextBoxAdv and SfRichTextRibbon (version 31.2.12) and applied the Windows 11 Light theme.

Please refer to the following links for more details:

Additionally, we have attached a sample application and a video for your reference.


Attachment: SfRichTextBoxAdv_Framework462_5d76b930.zip

Loader.
Up arrow icon