I have created the Document Understanding process using the Document understanding template in UiPath studio. When i publish this process i get the error message as shown below while loading dependencies. Its reporting error for in total 18 files
Bad IL format. The format of the file .nuget\packages\UiPath.cefsharpbundle.netcore\1.9.0\lib/net6.0-windows7.0/Ijwhost.dll’ is invalid.
Bad IL format. The format of the file .nuget\packages\UiPath.emgucvbundle\1.1.0\lib/net5.0/concrt140.dll is invalid.
It still goes ahead with package creation and creates the package.
I have tried updating the dependencies to the latest available version but still the same issue
The project shows some compilation errors that appear when it is built, but disappear when it is debugged or run. The errors also show up when the process is published to orchestrator during loading dependencies, but the package is still created and can be executed in both attended and unattended mode. I am not sure if these errors will affect the document understanding process in any way .
Thus checking here if if there is any solution of this problem
I have a bot that uses Excel, System and UiAutomation packages. That’s it. Still I get this error: Bad IL format. The format of the file ‘C:\Users\surya.avantsa.nuget\packages\UiPath.emgucvbundle\1.1.0\lib/net5.0/msvcp140_atomic_wait.dll’ is invalid. C:\Users\surya.avantsa.nuget\packages\UiPath.emgucvbundle\1.1.0\lib/net5.0/msvcp140_atomic_wait.dll
This issue is still in studio 24.10.1 for windows projects & libraries. VB or C# doesn’t seem to make a diffference, but I don’t get this compile error in windows-legacy or cross-platform projects.
It’s not preventing me from publishing or running the code, but it’s annoying to see those see those red compile errors which you can’t do anything about. Please fix!
The error message still occurs after installing the EmguCVBundle package:
After installing the bundle I still can’t find the folder “UiPath.emgucvbundle”.
I agree that, however the workflows run normally (attended as wel as unattended) it’s really annoying seeing the red lines go by when compiling. Also when something else goes wrong you won’t notice it because you think it’s the same old red lines.
These “Bad IL Format” errors are not affecting the project execution or compilation.
These are false errors. They can be ignored in the generated logs (execution and Event Viewer logs). In the higher Studio versions they will set as warnings or removed completely. Until then, you need to ignore them.
Solution:
Ignore for now the “Bad IL Format” false errors for various dll files in your project compilation/execution.
References for “Studio logged Bad IL format compilation errors when running some projects containing libraries migrated from Windows - Legacy. These errors did not affect project execution.”: