@ Weiti : You have the latest button DLL if file version == 1.0.1.0; product version == 1.0.204.0. Make sure you copy the new DLLs to your project under P:\rojectRoot\bin\Debug. If you’re not comfy with that, start a new project [italic]after[/italic] you run Gadgeteer Button Module Patch.exe.
FWIW, I’ve encountered time where repeated build, deploy, run, stop, edit, build, deploy cycles will result in flaky interrupts behavior; whether it’s buttons, Ethernet, WiFi, etc.
I’ve found the following process provides the most consistent results when interrupts start flaking:
Stop Debugging
Close VisStudio
Open MfDeploy
Click “Erase”, acknowledge the “you sure you wanna?” pop-up
There is a problem with the way the driver handles events. The exception occurs on the Up event. Until the next SDK, make sure you have an event handler assigned to both the Up and Down events.
I hit the same null refrence error and went to see what I had messed after upgrading to the latest SDK (always assume user error first). I think I may have stumbled upon the cause of the button error (or my crack dealer is cheating me again).
What I discovered is that of all the DLLs that are imported into my projects, the Gadgeteer.NETMF set are all still dated 6 Oct 2011 - even if I clean my project and reassociate references.
When I manually extracted the files from the GHI NETMF v4.1 SDK.msi that came in the latest SDK, I found that it contained the 6 Oct file set.
Should any or all of these components have been updated as well?