Testing_PR_creation_test

Document-Processing/Data-Extraction/Smart-Data-Extractor/NET/Assemblies-Required.md

@@ -0,0 +1,72 @@
+---
+title: Assemblies required for SmartDataExtractor | Syncfusion
+description: This section details the Syncfusion assemblies required to configure and run Smart Data Extractor seamlessly in .NET projects.
+platform: document-processing
+control: SmartDataExtractor
+documentation: UG
+keywords: Assemblies
+---
+# Assemblies Required to work with Smart Data Extractor
+
+The following assemblies need to be referenced in your application based on the platform.
+<table>
+  <thead>
+    <tr>
+      <th>Platform(s)</th>
+      <th>Assembly</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        {{'[WPF]'| markdownify }},
+        {{'[Windows Forms]'| markdownify }} and {{'[ASP.NET MVC]'| markdownify }}      
+      </td>
+      <td>
+        Syncfusion.Compression.Base<br/>
+        Syncfusion.ImagePreProcessor.Base<br/>
+        Syncfusion.OCRProcessor.Base<br/>
+        Syncfusion.Pdf.Imaging.Base<br/>
+        Syncfusion.Pdf.Base<br/>
+        Syncfusion.PdfToImageConverter.Base<br/>
+        Syncfusion.SmartFormRecognizer.Base<br/>
+        Syncfusion.SmartTableExtractor.Base<br/>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      {{'[Blazor]'| markdownify }},
+      {{'[.NET Core]'| markdownify }}
+      and {{'[.NET Platforms]'| markdownify }}
+      </td>
+      <td>
+        Syncfusion.Compression.Portable<br/>
+        Syncfusion.ImagePreProcessor.Portable<br/>
+        Syncfusion.OCRProcessor.Portable<br/>
+        Syncfusion.Pdf.Imaging.Portable<br/>
+        Syncfusion.Pdf.Portable<br/>
+        Syncfusion.PdfToImageConverter.Portable<br/>
+        Syncfusion.SmartFormRecognizer.Portable<br/>
+        Syncfusion.SmartTableExtractor.Portable<br/>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      {{'[.NET Multi-platform App UI (.NET MAUI)]'| markdownify }}
+      </td>
+      <td>
+        Syncfusion.Compression.NET<br/>
+        Syncfusion.ImagePreProcessor.NET<br/>
+        Syncfusion.OCRProcessor.NET<br/>
+        Syncfusion.Pdf.Imaging.NET<br/>
+        Syncfusion.Pdf.NET<br/>
+        Syncfusion.PdfToImageConverter.NET<br/>
+        Syncfusion.SmartFormRecognizer.NET<br/>
+        Syncfusion.SmartTableExtractor.NET<br/>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+
+

Document-Processing/Data-Extraction/Smart-Data-Extractor/NET/FAQ/how-to-resolve-the-onnx-file-missing-error-in-smart-data-extractor.md

@@ -0,0 +1,37 @@
+---
+title: FAQ for SmartDataExtractor | Syncfusion
+description: This section provides answers to frequently asked questions about Syncfusion Smart Data Extractor, helping users resolve common issues.
+platform: document-processing
+control: SmartDataExtractor
+documentation: UG
+keywords: Assemblies
+---
+
+# How to resolve the “ONNX file missing” error in Smart Data Extractor
+
+Problem:
+
+When running Smart Data Extractor you may see an exception similar to the following:
+
+```
+Microsoft.ML.OnnxRuntime.OnnxRuntimeException: '[ErrorCode:NoSuchFile] Load model from <path>\runtimes\models\syncfusion_doclayout.onnx failed. File doesn't exist'
+```
+
+Cause:
+
+This error occurs because the required ONNX model files (used internally for layout and data extraction) are not present in the application's build output (the project's `bin` runtime folder). The extractor expects the models under `runtimes\models` so the runtime can load them.
+
+Solution:
+
+1. Run a build so the application output is generated under `bin\Debug\netX.X\runtimes` (or your configured build configuration and target framework).
+2. Locate the project's build output `bin` path (for example: `bin\Debug\net6.0\runtimes`).
+3. Place all required ONNX model files into a `runtimes\models` folder inside that bin path.
+4. In Visual Studio, for each ONNX file set **Properties → Copy to Output Directory → Copy always** so the model is included on every build.
+5. Rebuild and run your project. The extractor should now find the ONNX models and operate correctly.
+
+Notes:
+
+- If you publish your application, ensure the `runtimes\models` folder and ONNX files are included in the publish output (you may need to mark files as content in the project file or use a <Content> entry).
+- If you prefer an automated approach, add the ONNX files to your project with `CopyToOutputDirectory` set, or create a post-build step to copy the models into the runtime folder.
+
+If the problem persists after adding the model files, verify file permissions and the correctness of the model file names.