Re: Button click event handler not called.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hi Dave,

Currently, I am not sure the root cause for your issue. But I have some
suggestions to your problem.

First, in Winform multithreading programming, any manipulating to the
controls' members from another thread must be marshaled with
Control.Invoke/BeginInvoke methods. This is because the underlying Win32
controls is not thread safe, so the calling must be marshaled to the
creation thread. Does your application obey this rule?

Also, have you tried your application on other machines? Then we can
determine if this issue is machines-specific.

For me, I will place a breakpoint in normal Button.Click event handler,
then get the fulll call stack for the Button.Click event(Make sure the
symbol is setup well). Then I will place the breakpoint above the call
stack methods one-by-one to see when clicking the button, which method
failed to execute. By using Reflector to tracing the source code of this
method, we will get some more internal detailed information of why the
calling is failed. I think you may also benefit from this troubleshooting
way.

At last, is there any way for you to level your application down to a
little sample project to demonstrate out this problem? If we can reproduce
out this problem, we can understand it better.

Thanks

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

.



Relevant Pages

  • Re: [RFC] hwbkpt: Hardware breakpoints (was Kwatch)
    ... The debugger should always eat the trap. ... agent who asked for the breakpoint and who is responsible for responding to ... some question about what value the debug exception handler should write ... For most other machines this will be a no-op. ...
    (Linux-Kernel)
  • Re: Alerting - Malicious software removal tool
    ... the proper tool to use when removing malware? ... How many machines were not cleaned by the MS provided tool? ... I have NO connection to any vendors products or tools, ... Calling an illegal alien an "undocumented worker" is like calling a ...
    (microsoft.public.security.virus)
  • Re: HijackThis Log Help
    ... The point is that if we teach people that we can mostly clean their ... machines, that it's good enough, and they don't feel the "pain", not ... Calling an illegal alien an "undocumented worker" is like calling a ...
    (microsoft.public.windows.server.sbs)
  • Re: [Clax86list] Looking for "binary bombs"
    ... fired up gdb and set a breakpoint on phase_1_of_1. ... I guess that's why the original assignment specified *which* machines in the cluster were to be used! ... But dynamic-linked executables are fussy! ... I guess obfuscated source code would be a solution... ...
    (comp.lang.asm.x86)
  • Re: Cannot install catalog file with SetupCopyOemInf() on 64bit OS
    ... calling SetupCopyOemInf() from my setup.exe. ... On 32bit machines, everything works fine, but somehow on 64bit machines, the ... To test this function, I tried another driver on the 64bit machine, but it ... co-installer, WdfCoInstaller01005.dll, so I'm kind of guessing ...
    (microsoft.public.development.device.drivers)