My old problem is easily re-creatable. 1) create a new winforms project. 2) add a menu on the form with an iteam 3) build 4) add another form that inherits the first form 5) add code to handle the click event of the menu item in the other form.
When you say "other form", you mean the first form, right?
6) try to open the second form in design time You will get crazy message about the click event being read only. Of course the click event is read only...it's not a property and I'm not assigning anything to it. dahhhhhh.
Interesting, do you really get this behavior with exactly these steps? I can't reproduce it here with either VC# Express 2005 or VB Express 2005. How do you create the inherited form? Do you add a new standard form and then manually change the base class? (This is how I did it.) The reason why I tried to reproduce it is that I wanted to take a look at the resx file of the second form to find out where the error message stems from and why/when the Form1.Click event becomes referenced in Form2's serialized resource data. Fabian =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
