PC Review
Forums
Newsgroups
Microsoft DotNet
Microsoft Dot NET Framework Forms
Design Time ability of Inherited Forms in VS2005 Final Release
Forums
Newsgroups
Microsoft DotNet
Microsoft Dot NET Framework Forms
Design Time ability of Inherited Forms in VS2005 Final Release
![]() |
Design Time ability of Inherited Forms in VS2005 Final Release |
|
|
Thread Tools | Rate Thread |
|
|
#1 |
|
Guest
Posts: n/a
|
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 |
|
![]() |
|
| Thread Tools | |
| Rate This Thread | |
|
|

Main Page 

