Troubleshoot guide for ASP.NET Core Word (DocIO) Library issues

When encountering problems with ASP.NET Core Word (DocIO) Library, it is essential to follow a structured approach to diagnose and resolve issues efficiently. Here are key things to check and share while dealing with such issues:

Things to check while facing an issue in Word Library:

1. Code snippet:

Double-check that your code snippets are error-free and logically sound. Any syntax errors or logical flaws can lead to unexpected behavior. Refer here to learn about using Word (DocIO) Library and the runnable examples from GitHub.

2. Proper disposal:

Ensure that all instances and streams are disposed of correctly. Failing to do so can result in memory leaks or resource exhaustion, impacting the application’s performance.

3. Version:

Verify if the issue persists in the latest NuGet package version. Updates often include bug fixes and improvements that might address the problem you are facing. You can get latest NuGet from nuget.org.

4. Input document:

Validate the integrity of the input document. Make sure it is not corrupted and is compatible with the Syncfusion Word (DocIO) Library. The current version of Synfusion Word (DocIO) Library supports from Word 97-2003 and later version documents.

5. Preservation:

Compare the input document and the generated output; this will help to point out whether the problem is in the input itself or anything in the Word (DocIO) Library only.

Things to share while reporting a bug:

1. Input documents:

Include the input document that triggered the problem. Generally, the issue depends on the internal structure of the file. So, providing the input documents aids in reproducing the issue accurately.
Note: If you have any confidential data in your input document, please replace it with some dummy data and provide us with the same. We just need your document to recreate the problem you face. Once the issue is investigated, we will delete the document permanently from our side and do not share it with anyone.

2. Complete code snippet / Issue reproducible sample:

Share the entire code snippet or a minimal reproducible sample that showcases the problem. This enables developers to understand and troubleshoot the issue effectively. You can download the runnable sample from GitHub and add your side code to prepare issue reproducible simple sample.

3. Details about the issue:

• Exception Issues: For exception type of issues, share the stack trace. This information is crucial for pinpointing the exact location of errors.
• Preservation Issues: Attach screenshots or output files highlighting the problem, which is helpful to figure out easily.

4. Environment details:

Sometimes, the issue may occur in a specific environment alone like Linux, macOS and cloud platforms. So, provide information about the environment where the problem occurred, including:

• Operating system
• Any other specific setup details (like the plan used in cloud platforms, docker file details if running in a container).

By adhering to these guidelines, you can streamline the bug reporting process and help developers investigate and resolve issues more effectively.

Conclusion

I hope you enjoyed learning about how can I have the server end of the Excel filter check.ox produce unique values in AP.NET Core Grid.

You can refer to our ASP.NET Core DocIO feature tour page to know about its other groundbreaking feature representations and documentation, and how to quickly get started for configuration specifications. You can also explore our ASP.NET Core DocIO example to understand how to create and manipulate data.

For current customers, you can check out our components from the License and Downloads page. If you are new to Syncfusion, you can try our 30-day free trial to check out our other controls.

If you have any queries or require clarifications, please let us know in the comments section below. You can also contact us through our support forums, Direct-Trac, or feedback portal. We are always happy to assist you!