Re: Once again - Object of type x...

OK.  So the 'nested' user controls - although the concept still seems a bit
strange - is not necessarily a bad idea.  However, the classes those
controls use ought to be split out to a separate project.

Peter

> -----Original Message-----
> From: Discussion relating to the specifics of the C# and
> Managed C++ languages [mailto:[email protected]]
> On Behalf Of Chris Anderson
> Sent: Monday, December 18, 2006 3:36 PM
> To: [email protected]
> Subject: Re: [DOTNET-CX] Once again - Object of type x...
>
> > > This is the generally recommended approach.
> > > If you get into a habit of checking this.DesignMode it
> stops a lot
> > > of unexpected problems (and helps to stop the IDE feeling
> sluggish
> > > as it runs runtime code (possibly trying to access
> databases, etc!))
> >
> > How will this (or better yet, will it at all) help the
> situation where
> > the project has 'nested' controls?
>
> The "in-design" usercontrols and their nested controls will
> not be communicating with each other (at least they will not
> be passing user classes between each other) because that code
> will be hidden behind a check for DesignMode and will
> therefore not be executed.
>
> Chris

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com