Thanks for sharing your solution
Microsoft Developer Support
This posting is provided S ISwith no warranties, and confers no rights.
| From: "Patrick Vanden Driessche"<< XXXX@XXXXX.COM >>
| References:<< XXXX@XXXXX.COM >>
| Subject: Re: Parent/Child Components: How to make the child components go
away when deleting the Parent.
| Date: Fri, 14 Nov 2003 07:43:44 +0100
| Lines: 81
| Organization: DevBrains
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID:<<# XXXX@XXXXX.COM >>
| Newsgroups: microsoft.public.dotnet.languages.vb
| NNTP-Posting-Host: 173.128-136-217.adsl.skynet.be 188.8.131.52
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.languages.vb:156753
| X-Tomcat-NG: microsoft.public.dotnet.languages.vb
| Hi John,
| Thank you for the follow up ....
| As you can image, I kept looking for a solution on this myself too ...and
| managed to find a solution in the meantime ...
| For those interested, here's what I did:
| As my problem is 'Design-Time' related I created a custom
| 'ComponentDesigner' class, which hooks up to the 'ComponentRemoving' event
| of the 'IComponentChangeService'.
| Through this event, I can detect when the user deletes the 'parent'
| component from the form designer and manually remove the 'children' from
| same form source code persistence.
| Thank you.
| ""John Eikanger""<< XXXX@XXXXX.COM >> wrote in message
| news:I$ XXXX@XXXXX.COM ...
|>> Hi, Patrick
|>> I've started the process of escalating this issue to the product team.
|>> Please bear with us.
|>> Thank you for choosing the MSDN Managed Newsgroups,
|>> John Eikanger
|>> Microsoft Developer Support
|>> This posting is provided "AS IS" with no warranties, and confers no
|>> | From: "Patrick Vanden Driessche"<< XXXX@XXXXX.COM >>
|>> | Subject: Parent/Child Components: How to make the child components go
|>> away when deleting the Parent.
|>> | Date: Thu, 13 Nov 2003 04:56:21 +0100
|>> | Lines: 30
|>> | X-Tomcat-NG: microsoft.public.dotnet.languages.vb
|>> | Hi All,
|>> | I'm currently writing an in-house Form validation framework (WinForms)
|>> | is based on 'Component'-inheriting object.
|>> | So basically, I have a small hierarchy.
|>> | FormValidator
|>> | +-- ControlValidator
|>> | +--ValidationRule
|>> | Via UITypeEditors, I got the part of managing the different
|>> | child-collections to work properly. (CollectionEditor)
|>> | But what I don't get is how can I make the child components go away
|>> | form designer if you delete the 'FormValidator' component (top-leve
|>> | from the Form's component tray.
|>> | In other terms, I'm lookig for the same behaviour as with the
|>> | TabControl/TabPages control relationship...but not for 'Control', but
|>> | 'Component'-based objects.
|>> | I've read a few articles, have applied some attributes