yakshasa
New member
In debug mode, after my application closes I am getting "Invoke or
BeginInvoke cannot be called on a control until the window handle has
been created".
It literally happens after the last form - The MDI parent form that
serves as my application's desktop - closes, right after the
FormClosed event End Sub.
I am not doing any sort of direct thread handling in code that calls
Invoke or BeginInvoke.
In the installed application executable, the message becomes
<ApplicationName> "has encountered an error and needs to close".
I recall glimpsing a KB article - which I have since misplaced -
about Framework 2.0 SP1 having an issue that caused the error to
display when an application otherwise closed without problems.
I'm leaning toward that explanation as I have one machine out of
three that is not getting the error, and the difference seems to be
which frameworks are installed (but all three have Framework 2.0
Service Pack 2).
The error cannot be trapped.
Any suggestions?
XP Machine Without error:
Microsoft .NET Compact Framework 1.0 SP3 Developer
Microsoft .NET Compact Framework 2.0 SP2
Microsoft .NET Compact Framework 3.5
Microsoft .NET Framework 1.1
Microsoft .NET Framework 1.1 Hotfix (KB928366)
Microsoft .NET Framework 2.0 Service Pack 2
Microsoft .NET Framework 3.0 Service Pack 2
Microsoft .NET Framework 3.5 SP1
VISTA Machine with error:
Microsoft .NET Compact Framework 2.0 SP2
Microsoft .NET Compact Framework 3.5
Microsoft .NET Framework 3.5 SP1
XP (SP3) Machine With error:
Microsoft .NET Compact Framework 2.0 SP2
Microsoft .NET Framework 3.0 Service Pack 2
Microsoft .NET Framework 3.5 SP1
BeginInvoke cannot be called on a control until the window handle has
been created".
It literally happens after the last form - The MDI parent form that
serves as my application's desktop - closes, right after the
FormClosed event End Sub.
I am not doing any sort of direct thread handling in code that calls
Invoke or BeginInvoke.
In the installed application executable, the message becomes
<ApplicationName> "has encountered an error and needs to close".
I recall glimpsing a KB article - which I have since misplaced -
about Framework 2.0 SP1 having an issue that caused the error to
display when an application otherwise closed without problems.
I'm leaning toward that explanation as I have one machine out of
three that is not getting the error, and the difference seems to be
which frameworks are installed (but all three have Framework 2.0
Service Pack 2).
The error cannot be trapped.
Any suggestions?
XP Machine Without error:
Microsoft .NET Compact Framework 1.0 SP3 Developer
Microsoft .NET Compact Framework 2.0 SP2
Microsoft .NET Compact Framework 3.5
Microsoft .NET Framework 1.1
Microsoft .NET Framework 1.1 Hotfix (KB928366)
Microsoft .NET Framework 2.0 Service Pack 2
Microsoft .NET Framework 3.0 Service Pack 2
Microsoft .NET Framework 3.5 SP1
VISTA Machine with error:
Microsoft .NET Compact Framework 2.0 SP2
Microsoft .NET Compact Framework 3.5
Microsoft .NET Framework 3.5 SP1
XP (SP3) Machine With error:
Microsoft .NET Compact Framework 2.0 SP2
Microsoft .NET Framework 3.0 Service Pack 2
Microsoft .NET Framework 3.5 SP1