DocumentRecognitionSettings missing in Aspose.OCR_25.11.0

Aspose.OCR Product Family
1

We are trying to follow the example in this article:
Create Scanned PDF to Excel Converter with OCR using C# | File Format Processing Plugins for C# .NET Core | Aspose Blog

but DocumentRecognitionSettings class is not available in Aspose.OCR_25.11.0

Can you please let us know what we are missing here?

2

@ganeshmuthuvelu

Summary
The DocumentRecognitionSettings class that appears in the blog example is not part of the Aspose.OCR 25.11.0 NuGet package, so the sample will not compile with that version.

Why it happens
In the 25.x release line Aspose.OCR introduced API changes and removed several older types, including DocumentRecognitionSettings. The current API uses the OcrEngine class with a Settings property (e.g., OcrEngineSettings) to configure language, page segmentation, etc. Because the older class no longer exists, code that references it fails to build.

What to do next

  1. Confirm the missing type – Open the Aspose.OCR 25.11.0 assembly (e.g., via Visual Studio’s Object Browser) and verify that DocumentRecognitionSettings is absent while OcrEngine and its Settings property are present.
  2. Adapt the sample – Replace the usage of DocumentRecognitionSettings with the current settings class. A typical pattern looks like:
var ocrEngine = new OcrEngine();
ocrEngine.Image = ImageStream.FromFile("page.png");
ocrEngine.Settings = new OcrEngineSettings
{
Language = OcrLanguage.English,
// other options as needed
};
var result = ocrEngine.Recognize();
// write result.Text to Excel, etc.

Adjust the properties to match the functionality you need.
3. Use an older package (temporary) – If you must keep the original code unchanged, you can reference an earlier Aspose.OCR version (e.g., 24.x) where DocumentRecognitionSettings still exists. This should be a short‑term workaround because older releases miss recent bug fixes and improvements.
4. Check the release notes – Review the Aspose.OCR 25.x release notes for the exact list of API changes. They will document the migration from DocumentRecognitionSettings to the newer settings model.
5. Validate – Re‑build the project, run a small test (e.g., a single‑page PDF), and confirm that the OCR output is written to Excel as expected.

Diagnostic checklist (useful if you still encounter issues):

  • Verify the exact Aspose.OCR NuGet version installed (dotnet list package).
  • Capture the full compiler error message (type not found, missing namespace, etc.).
  • Ensure the project references the correct Aspose.OCR DLL (no mixed versions).
  • Enable Aspose logging (Aspose.OCR.Logging.Enable = true;) to see any runtime warnings.
  • If the problem persists, create a minimal repro project and share the code and package version with Aspose support.

Note: The specific replacement class (OcrEngineSettings) and usage pattern are based on the typical 25.x API shape, but you should verify against the official Aspose.OCR documentation for your exact version.

:warning: I could not fully verify this explanation against the retrieved sources. Please double-check the behaviour in your environment and confirm the exact SDK/version.