Hi there,
I still not understand this behaviour of VS2005 Windows Forms Designer. It
is a normal practice that we create a base form and then master form and
then final form. I mean let say I create BaseForm.cs which is my base form
(just derived form System.Windows.Forms) then I create MasterForm in wich I
put toolbar and datagridview control (with public modifiers). And then I
finally create EmployForm.cs in which I add few more things and fetch
dataset and show it in datagridview control. These works absolutely fine in
VS2003 at design time and runtime but with VS2005 I cannot do this at design
time. When I click on dataviewgrid control in final form (employeform.cs),
all properties turn in gray and read-only. WHY WHY WHY????
Same thing If I want to add few more buttons in my menuStrip control, I
cannot do it in final form which is derived from my master form.
I reported this problem at Beta2 stage and Microsoft said that it requres
extensive engineering efforts and cannot be accomplished in this release
(And I thought Microsoft will solve in the final release but still not
there)
I checked with few other vendors (like DevExpress), and they have now
released their latest components so that I can use them in derived forms (I
am using XtraGrid now in my derived forms and it just working fine at design
time!).
Is there any work around to solve the problem???
Thanks,
Binoy
Frank Fang - 20 Dec 2005 23:57 GMT
Binoy,
Have you tried to rebuild the project before doing things from the Inherited
Forms?
Frank
Miha Markic [MVP C#] - 06 Jan 2006 19:53 GMT
This is by design - go figure. I can't understand the MS' decision either.
http://cs.rthand.com/blogs/blog_with_righthand/archive/2005/11/10/186.aspx
At least the fine folks at DevExpress made a workaround - their stuff works
as usual in visual inheritance scenario.

Signature
Miha Markic [MVP C#]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/
> Hi there,
>
[quoted text clipped - 27 lines]
> Thanks,
> Binoy