Hi,

We've upgraded to the latest version of the multiDLL build of EO.WebBrowser (3.0.112.1), since we do that we can't run our project (works fine with 3.0.100.1).

The project crash with an EndOfStreamException, here is the stack error :

Unable to read beyond the end of the stream

Détails:
à System.IO.MemoryStream.InternalReadInt32()
à System.IO.BinaryReader.ReadInt32()
à EO.WebBrowser.Internal.av.l()
à EO.WebBrowser.Internal.bu.a(a4 A_0)
à EO.WebBrowser.Internal.bp.a(a4 A_0)
à EO.WebBrowser.Internal.bp.b(a4 A_0)
à EO.WebBrowser.Internal.bu.b(a4 A_0)
à EO.WebBrowser.WebView.a(az A_0, a4 A_1)
à EO.WebBrowser.WebView.<>c__DisplayClass11.<OnMessage>b__10()
à EO.WebBrowser.WebView.<>c__DisplayClasse.<RunAction>b__d()
à EO.WebBrowser.WebView.a(Boolean A_0, b A_1)
à EO.WebBrowser.WebView.a(Boolean A_0, Action A_1)
à EO.WebBrowser.WebView.al(az A_0, a4 A_1)
à EO.WebBrowser.Internal.az.a(WebView A_0, az A_1, Int32 A_2, IntPtr A_3, IntPtr A_4)
à EO.WebBrowser.WebView.c(IntPtr A_0, Int32 A_1, IntPtr A_2, IntPtr A_3, Boolean& A_4)
à EO.WebBrowser.Internal.z.a(IntPtr A_0, Int32 A_1, IntPtr A_2, IntPtr A_3)
à System.Windows.Forms.UnsafeNativeMethods.DispatchMessageA(MSG& msg)
à System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
à System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
à System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
à System.Windows.Forms.Application.Run(ApplicationContext context)
à Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
à Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
à Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
à avensys.My.MyApplication.Main(String[] Args) dans 17d14f5c-a337-4978-8281-53493378c1071.vb:ligne 81
à System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
à System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
à Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
à System.Threading.ThreadHelper.ThreadStart_Context(Object state)
à System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
à System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
à System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
à System.Threading.ThreadHelper.ThreadStart()

Are you aware of this bug? How can we resolve that?

For now, we remain on the previous version (3.0.100.1)...

Thanks for your help