Janus GridEX is pretty good for it - I worked closely with them on the release of their Janus Suite to ensure it worked in inheritance situations, and they have done a really nice job of it.
Dino -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Sébastien Lorion Sent: Saturday, 29 July 2006 09:35 To: [email protected] Subject: Re: [ADVANCED-DOTNET] VS2005 s#cks!!!!!!!!!!!!! After losing my hairs one too many times, I really think composition works better than inheritance. Inheritance sounds cool but our experience is that it really sucks. If you use a control (commercial or not) that does not behave well in inheritance scenarios, you are in for a lot of troubles. Data grids and funky controls are particularly bad in that aspect. Sébastien On 7/28/06, Franklin Gray <[EMAIL PROTECTED]> wrote: > 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. > 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. > > My solution was to create my own events in the base form and raise them in > the click event on that form and catch them in the inheriting form. This > is more like parent child relationship which ISN'T what inheritance is all > about. > > > > > Message from Julia Lerman <[EMAIL PROTECTED]>@DISCUSS.DEVELOP.COM > received on 07/28/2006 03:55 PM > > 07/28/2006 03:55 PM > > > > Julia Lerman <[EMAIL PROTECTED]>@DISCUSS.DEVELOP.COM > > Please respond to "Discussion of advanced .NET topics." > <[email protected]> > Sent by "Discussion of advanced .NET topics." > <[email protected]> > > > > To: [email protected] > cc: > Subject: Re: [ADVANCED-DOTNET] VS2005 s#cks!!!!!!!!!!!!! > > Okay, I have been through this hell myself and generally in my app I can > solve it in one of three ways. It took me a long time and a lot of > patience > to come up with these crazy ways of making the problem go away. And it > comes > back sometimes, but I just do my magic incantations and I'm good to go > again. > > Sometimes there is a circular reference problem. Sometimes I have > mismatched > references. > > It's called the return of DLL hell. > > My solution has a dll with the base form, then about 20+ other dlls that > contain forms that inherit from that form. > > I also have a number of other projects in there that the dll's of the base > and subclassed forms depend on (reference). > > Pattern #1 > > I have found that sometimes (and I don't know why but I've learned to > accept > it) the references to these other dlls get out of synch. > > There are two dlls that I reference directly in the bin of the main > project > (I have them all build into the main project's bin) and the rest I just > reference the projects. The two that I reference directly are due to > another > issue that is not related to the UI stuff. > > So, if it's possible, remove all of the common references from both > projects > and then add them back in. Be sure to match the references. > > Pattern #2 > Remove and then re-add the dll with the subclassed form into the solution. > Rebuild. > > Pattern #3 > Remove the reference to the dll with the base form. Re-add it back in. > > No guarantees but in my app solution, one of these always does the trick. > > Good luck > > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Franklin Gray > Sent: Friday, July 28, 2006 4:37 PM > To: [email protected] > Subject: Re: [ADVANCED-DOTNET] VS2005 s#cks!!!!!!!!!!!!! > > tried that and it didn't work. It still wouldn't let me go into design > mode. What I was doing worked in vs2003 just fine. > > > > Message from Shawn Hempel <[EMAIL PROTECTED]>@DISCUSS.DEVELOP.COM > received on 07/28/2006 03:11 PM > > 07/28/2006 03:11 PM > > > > Shawn Hempel <[EMAIL PROTECTED]>@DISCUSS.DEVELOP.COM > > Please respond to "Discussion of advanced .NET topics." > <[email protected]> > Sent by "Discussion of advanced .NET topics." > <[email protected]> > > > > To: [email protected] > cc: > Subject: Re: [ADVANCED-DOTNET] VS2005 s#cks!!!!!!!!!!!!! > > If I understand your issue correctly -- you don't /have/ to subscribe to > inherited events like that. > Microsoft recommends you just override the base class' event handlers. > Very OOP friendly. > > :: > http://msdn2.microsoft.com/en-us/library/system.windows.forms.control.onente > r.aspx > :: > > The *OnEnter* method also allows derived classes to handle the event > without attaching a delegate. This is the preferred technique for > handling the event in a derived class. > > *Notes to Inheritors *When overriding *OnEnter* in a derived class, > be sure to call the base class's *OnEnter* method so that registered > delegates receive the event. > > > > Franklin Gray wrote: > > Sorry all for my outburst. I've never had so much pain in going to the > > next version before except when moving from COM to dotnet and that was > > expected. At least then the IDE didn't have much problems. It really > > buggs me that I have to put events into my base form that I inherit from > > and catch the events in the inheriting form. Somewhere I think MS > forgot > > what inheritance is all about. > > > > Thanks for the links. > > > > > > > > > > Message from Sébastien Lorion > > <[EMAIL PROTECTED]>@DISCUSS.DEVELOP.COM received on 07/28/2006 > > 01:55 PM > > > > 07/28/2006 01:55 PM > > > > > > > > Sébastien Lorion <[EMAIL PROTECTED]>@DISCUSS.DEVELOP.COM > > > > Please respond to "Discussion of advanced .NET topics." > > <[email protected]> > > Sent by "Discussion of advanced .NET topics." > > <[email protected]> > > > > > > > > To: [email protected] > > cc: > > Subject: Re: [ADVANCED-DOTNET] VS2005 s#cks!!!!!!!!!!!!! > > > > Humm, consider yourself lucky to not have worked with VS 2005 BETA 2. > > RTM is rock stable compared to it ! Btw, BETA 1 was mostly fine, so > > wtf happened between ? > > > > Sébastien > > > > On 7/28/06, Frans Bouma <[EMAIL PROTECTED]> wrote: > > > >>> http://www.windowsforms.net/articles/debuggingwsod.aspx > >>> > >> White Screen of .... 'Darn' ??? :) haha :) > >> > >> To Franklin: yes it sucks. MS has released some patches, call > >> > > PSS for the patches. Yes that sucks even more, we all ask MS > > > >> year after year to release patches early, but that's not the case, > >> > > because if they'd do that the world would obvious come to an > > > >> end... </sarcasm> > >> > >> FB > >> > >> =================================== > >> This list is hosted by DevelopMentor(r) http://www.develop.com > >> > >> View archives and manage your subscription(s) at > http://discuss.develop.com > >> > >> > > > > > > > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at http://discuss.develop.com > > > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at http://discuss.develop.com > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at http://discuss.develop.com > > > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at http://discuss.develop.com > -- Sébastien Lorion Software Architect / Architecte organique [EMAIL PROTECTED] =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
