how do I turn off the form designer's automatic handler code deletion?

[Bob]

Is there a way to turn off the form designer's automatic deletion of
"handles <control>.<eventname>" when you delete a control? It's extremely
annoying to replace one control with another of the same name, run the
project, then realize that none of the events are being handled any more.
This feature *really* needs to be removed.

Bob

[Armin Zingler]

"Bob" <no****@nowhere.com> schrieb

Is there a way to turn off the form designer's automatic deletion
of "handles <control>.<eventname>" when you delete a control? It's
extremely annoying to replace one control with another of the same
name, run the project, then realize that none of the events are being
handled any more. This feature *really* needs to be removed.

No, not possible. If there's no control, there can be no "Handles.."
anymore. Only events of existing controls can be handled.
--
Armin

How to quote and why:
http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html

[Bob]

> No, not possible. If there's no control, there can be no "Handles.."

anymore. Only events of existing controls can be handled.

Impossible for MS to change such behavior? Highly doubtful. The designer is
perfectly capable of tolerating a compile error outside of
InitializeComponent.

Bob

[Armin Zingler]

"Bob" <no****@nowhere.com> schrieb

No, not possible. If there's no control, there can be no
"Handles.." anymore. Only events of existing controls can be
handled.

Impossible for MS to change such behavior? Highly doubtful. The
designer is perfectly capable of tolerating a compile error outside
of InitializeComponent.

If you are capable of tolerating it, yes, then it could make sense.

BTW, your system date/time is wrong.

--
Armin

How to quote and why:
http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html

[Herfried K. Wagner [MVP]]

* "Bob" <no****@nowhere.com> scripsit:

No, not possible. If there's no control, there can be no "Handles.."
anymore. Only events of existing controls can be handled.

Impossible for MS to change such behavior? Highly doubtful. The designer is
perfectly capable of tolerating a compile error outside of
InitializeComponent.

I don't see any reason for changing the behavior. You could comment out
the 'Handles...' that would be removed /before/ removing the control in
the designer.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>