Aspose.OCR NuGet Package References

@Mitsobar

We are checking it and will get back to you shortly.

Any news. Were you able to reproduce my situation with my project?

@Mitsobar

We faced issue while downloading the files from the link shared by you. We are sorry for the trouble. Can you please share link to the files again and make sure that it is accessible for downloading?

Error

I’ve had this link tested to be sure it works. It has a timeout so it would be best if you used it as soon as possible.

@Mitsobar

We were able to replicate the issue in our environment and have logged it as OCRNET-594 in our issue tracking system for further investigation. We will surely look into its details and keep you posted with the status of its correction. Please be patient and spare us some time.

We are sorry for the inconvenience.

This is a time sensitive project. I know this is a Free Support forum.
If we convert to using a Paid Support will the fix be any faster?

In the past we had Paid Support and it took a quite a while to resolve a ticket.
We dropped it because the results weren’t worth the price.

@Mitsobar

We have recorded your concerns. Please spare us a little time to investigate the ticket initially. We will soon share some news about its ETA for both free and paid support cases.

@Mitsobar

We have performed an investigation for the ticket. The console application and the library were built with flags AnyCPU. But in Console App, this flag “Prefer 32bit” is checked and in the library is unchecked.

This flag means what the AnyCPU is - it is x64 or it is x86. For Aspose.OCR, possibly incorrectly resolves the dependency and connects with the mistaken ONNX runtime DLL version.

So in such case then we have an incorrect dependency connection of two projects - you can define the architecture exactly. x64-x64 or x86-x86

It also will work if you uncheck Prefer 32bit flag in both projects.

We will investigate why we have incorrect dependency resolving in the case of AnyCPU with a 32bit flag and without. If it is possible we will fix it in the nearest release.
correct_1.png (77.1 KB)
correct_2.png (85.0 KB)
correct_3.png (52.2 KB)
original.png (73.9 KB)