>>>That's what I'm trying to avoid. I don't want to create a class for just one use. If I can't use a class at least twice, what's the point of creating it?
>>
>>I see what you mean. Sometimes we create a class that's not gonna be reused in order to "manage complexity". But that's not your case.
>>
>>I think I'm missing your point: if this is something so specific for this button, why don't you just put the code on its Click method?
>
>It's a fairly complex procedure that could really use some sub-programs. The entire code is about 200 lines long and logically can be broken into about 4 different sub-programs.

I know that you said you want to not use this.

But its really easy to create new method for the form in the designer.
You just have to add the 4 methods to the form and call them from your button click...

What do you need that cant be handle this way?