Yeah, the designer is the crux of my problem. I don't want to loose the
benefits, but I wish provisions were made to tell the designer when to
lay off. I'm working on an alternate solution that I'll post here if it
pans out. It doesn't use the normal serialization route, which I don't
like, but
Eric Burley [mailto:[EMAIL PROTECTED]] wrote:
> I've got a form which implements ISerializable. It contains
> custom controls that implement Iserializable as well. I can
> serialize those controls in the GetObjectData method on the
> form. The problem comes when I try to handle the
> Deseriali
I'm trying to get my head around using serialization with forms. Here's
the issue.
I've got a form which implements ISerializable. It contains custom
controls that implement Iserializable as well. I can serialize those
controls in the GetObjectData method on the form. The problem comes
when
