Can't 'design' UserControl
-
**CROSSPOSTED TO VS .NET IDE ISSUES FORUM** Hi all, I've got a class called RowView derived from UserControl, which is itself the parent of another class (AuthorView). RowView has a public property Data. Since RowView should never be instantiated directly (it's a pseudo-abstract class) it doesn't implement Data, it simply throws a NotSupportedException. My AuthorView class does implement Data. Now my problem is that whenever I try and 'design' AuthorView in VS .NET the designer tries to access RowView.Data, which throws an exception. So my question is, how do I stop VS .NET's designer from attempting to access Data. I've tried settig the Browsable attribute to false in RowView.Data, but it doesn't help. I can post up some code if that'll help clarify the situation. TIA, Pete
-
**CROSSPOSTED TO VS .NET IDE ISSUES FORUM** Hi all, I've got a class called RowView derived from UserControl, which is itself the parent of another class (AuthorView). RowView has a public property Data. Since RowView should never be instantiated directly (it's a pseudo-abstract class) it doesn't implement Data, it simply throws a NotSupportedException. My AuthorView class does implement Data. Now my problem is that whenever I try and 'design' AuthorView in VS .NET the designer tries to access RowView.Data, which throws an exception. So my question is, how do I stop VS .NET's designer from attempting to access Data. I've tried settig the Browsable attribute to false in RowView.Data, but it doesn't help. I can post up some code if that'll help clarify the situation. TIA, Pete
you can always chekc if you are in designmode (this.designmode) and NOT throw the exception if you are in design mode.. not that this is a solution but i suppose it will atleast let you continue working on your controls untill you find a solution for this... //Roger
-
you can always chekc if you are in designmode (this.designmode) and NOT throw the exception if you are in design mode.. not that this is a solution but i suppose it will atleast let you continue working on your controls untill you find a solution for this... //Roger