Hi,

>>Don't know if you've solved you MenuStrip problem yet but
>
>Yes, I solved it. As you may notice in source code I posted there was missing MainMenuStrip assignment in parent form which causes the issue.
>

I'm afraid I missed that. If you add the MenuStrip using the IDE doesn't it automatically set the MainMenuStrip property?

>
>>>3. I need to merge Toolstrip buttons also. Will Toolstrip button merging
>>>work in the same way as menu merging ? Can I remove child toolstrip by
>>>setting its visible propery to false ?
>>
>>I've just been looking at this. Firstly the automatic merge doesn't work with ToolStrips - you have to use the ToolStripManager.Merge() method. Having said that I can get it working successfully in a simple test scenario but *not* in my actual application - I'm having the same problem with the ToolStrip that you are/were having with the MenuStrip (but my MenuStrips are merging OK).
>
>I used code in mdi child activate event from the forum link I posted to you to merge my Toolstrips.
>I havent tested it a lot but my initial tests show that this work OK.

Mine's working now too. The problems weren't related (mine was related to stupidity - I was trying to merge the child toolstrip to the parent *menustrip* :={ )

>
>>
>>I'll let you know if I solve this - the problems may be related...
>
>My biggest issue is that MenuStrip and ToolStrip merging are not supported in MONO. So in MONO duplicate menus and toolstrips appear.

MONO? Is that Linux .NET stuff? If you have, say, a menuitem in a child form menustrip and programatically add it to the parent menustrip (rather than attempting an automatic merge) does that move it or does the same menuitem appear in both menus?

Regards,
Viv