Logo
My Account |  Site Map | Contact Us  
Welcome Guest Search | Active Topics | Sign In | Register

WebBrowser - WPF - SAMPLE Options
Luiz
Posted: Friday, November 10, 2017 9:02:24 AM
Rank: Newbie
Groups: Member

Joined: 12/15/2015
Posts: 4
Hello friends
I opened the "WebBrowser" sample project in VB.NET.
When I compile and try to generate the executable the message will appear:
can anybody help me?

{"Dispatcher processing has been suspended, but messages are still being processed."}
    [System.InvalidOperationException]: {"Dispatcher processing has been suspended, but messages are still being processed."}
    Date: {System.Collections.ListDictionaryInternal}
    HelpLink: null
    HResult: -2146233079
    InnerException: null
    Message: "Dispatcher processing has been suspended, but messages are still being processed."
    Source: "WindowsBase"
    StackTrace: "at System.Windows.Threading.Dispatcher.WndProcHook (IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean & handled) \ r \ n in MS.Win32.HwndWrapper.WndProc (IntPtr hwnd, Int32 msg, IntPtr wParam , IntPtr lParam, Boolean & handled) in MS.Win32.HwndSubclass.DispatcherCallbackOperation (Object o) \ r \ n in System.Windows.Threading.ExceptionWrapper.InternalRealCall (Delegate callback, Object args, Int32 numArgs) \ r \ n at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen (Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler) "
    TargetSite: {IntPtr WndProcHook (IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)}
eo_support
Posted: Friday, November 10, 2017 10:07:41 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 19,749
Hi,

This is usually caused by an exception when the application launch. You can either set Visual Studio to break when an exception is thrown or handle EO.Base.Runtime.Exception event to catch the exception details. Once you can see the exception, you can tell us the exception details (error message, callstack, etc), we can then go from there.

FYI, here is a Microsoft article that you may find useful:

https://msdn.microsoft.com/en-us/library/d14azbfh(v=vs.110).aspx

The debugger may break on many exceptions but some are properly handled either by the framework or by us. So you will want to find the one that is directly from our code (callstack shows our DLLs).

Thanks!


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.