Rank: Member
Groups: Member
Joined: 6/5/2018
Posts: 14
|
We are trying to assist a vision impaired customer who is having an issue with our application crashing. The full stack trace of the crash is below. I am wondering if you guys at EO could shed any light on what library might be failing to load?
The issue arises when he uses a part of the application that causes EO Browser to load into a webview. My guess is that there is a dependency missing from his computer, but any assistance working out what that dependency may be would be appreciated.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Failed to resolve LoadLibrary.
at EO.Internal.jr.b.d()
at EO.Internal.jr.b.a(bac[] A_0, String A_1, String A_2)
at EO.Internal.jr.a(Boolean& A_0, bac[] A_1, String A_2, String A_3)
at EO.Internal.jr.a(bac[] A_0, String A_1, String A_2)
at EO.Internal.jr.o.c()
at EO.Internal.jr.o.f()
at EO.Internal.jr.o()
at EO.Internal.jr.a(Boolean& A_0, bac[] A_1, String A_2, String A_3)
at EO.Internal.jr.a(bac[] A_0, String A_1, String A_2)
at EO.Internal.awa.b()
at EO.Internal.awa.a(WindowsIdentity A_0)
at EO.WebEngine.Engine.Start(WindowsIdentity user)
at EO.Internal.awa.c()
at EO.Internal.ct..ctor(WebView A_0)
at EO.WebBrowser.WebView.y()
at EO.WebBrowser.WebView.a(IntPtr A_0, Boolean A_1)
at EO.Wpf.WebViewHost.a.a()
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
Some extra details:
We are using version 18.2.26 of the browser controls.
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi, Please try to set EO.Base.Runtime.EnableEOWP to true and see if it resolves the issue for you: https://www.essentialobjects.com/doc/common/eowp.aspxThanks!
|
Rank: Member
Groups: Member
Joined: 6/5/2018
Posts: 14
|
This doesn't seem to be a likely fix. How likely do you think it is that this will work? We'd need to release a completely new version of our software to test this theory out. I can see that the change might be worthwhile, but our customer's need is a bit more pressing.
Our customer reports this additional information. The application stopped working after an upgrade to windows 10 release 1809. Both upgraded computers he has have this problem. An older machine that has not had Windows upgraded is working fine with the most recent version of our software.
Is there any known issue with EO.Wpf and Windows 10 1809?
Dylan
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi,
You can try to put eowp.exe in the same directory as your main exe file and it should have the same effects as setting the above property to true. You can get eowp.exe from your installation folder. Make sure it comes from exactly the same version that you used to build your application as our library won't use it unless the versions match.
Windows update 1809 has problems and Microsoft has already pulled the update. So we have no way of verifying the problem or the solution ---- we did have other customers reporting the same problem and the issue was resolved after setting EO.Base.Runtime.EnableEOWP to true.
Thanks
|
Rank: Member
Groups: Member
Joined: 6/5/2018
Posts: 14
|
I have been able to reproduce this issue by installing the Windows Insider Preview of Windows 10 on a machine. I am investigating further and will advise you in due course if the fix you suggest works in that environment.
The specific version of Windows I am running (in case you want to try and reproduce locally) is:
Windows 10 Pro Insider Preview
Build 18267.rs_prerelease.181020-1908
Added later:
I can confirm that we were able to resolve the issue locally by deploying the ewop.exe file and changing the EO.Base.Runtime.EnableEOWP setting. Just copying the eowp.exe file by itself did not work.
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Thanks for the additional information. We have confirmed that just copying eowp.exe over alone would not work. We are changing our code and this should work in our next build.
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi,
This is just to let you know that we have posted a new build that will automatically enable EOWP as long as the file eowp.exe is present in the application folder. The new build is available both on our download page and through nuget. Please feel free to let us know if you still have any questions.
Thanks
|