ReleaseHandle trashes the default WindowProc

I have noticed an issue and I'm hoping you can confirm it. It's probably within the .NET framework itself - in which case I'll work around it.

After completing a 2nd edit on the editable label, the 2nd ReleaseHandle call seems to be unhooking the form's default window proc. The form no longer resizes correctly and if you Spy on the window messages, the message loop is receiving no replies to sent messages.

I think I can work around this by only assigning once when the form is initialised - certainly not as tidy.

I wanted to confirm that you see the same problem, if you have the time.

This is using Framework version 1.1.4322.573.

(I wish it were unbelievable that such a simple pair of calls could have such a bug in them).

Martin Frost

Software engineer

Westbrook Techno

I eventually found one reference to an unspecified bug in Assign/ReleaseHandle.

The workaround was to re-implement the methods and use SetWindowLong, tracking the WndProcs 'manually'.