It happens! :) On Sat, Dec 27, 2008 at 4:42 PM, nerd_boy <[email protected]> wrote:
> > Erm, actually, I found out what the real problem was about an hour or > so after posting, and I don't think the post had cleared moderation as > of then, so I couldn't throw solved in there. > So it is solved, and in fact isn't at all related to anything in my > post above. The problem seemed to be a capitalization error in the get > portion of a certain Property that was causing it to return itself. > :X > > Thanks though! > > On Dec 27, 5:30 am, "Kaarthik Padmanabhan" <[email protected]> > wrote: > > I am just spitballing, but have you tried > > setting System.ComponentModel.Bindable and > System.ComponentModel.Browsable > > to false? > > > > > > > > > > > > On Sat, Dec 27, 2008 at 11:49 AM, nerd_boy <[email protected]> > wrote: > > > > > I've got two custom controls, A and B. A is public, B is internal. B > > > is meant to act as a child to A, and all A acts as is the 'parent' for > > > one or more Bs. My reasons for keeping B internal is because A > > > contains the information that all Bs will access, and B is dependant > > > on the information in an A. > > > > > Anywho, whenever I attempt to add control A to a form in Visual Studio > > > Express(2008), the Designer crashes. After messing around with things > > > abit, it would seem that the problem lies with B being internal, since > > > making it public dosn't cause Designer to crash, but do what it would > > > normally do. > > > > > Is there anyway to get the Designer to completely ignore B? I've tried > > > [ToolboxBrowsable(false)], but this didn't work at all. > > > > > Thanks! > > > > -- > > Kaarthik,http://coding-passion.blogspot.com > -- Kaarthik, http://coding-passion.blogspot.com
