Don't assume anything!!
I've not checked out anything yet.
I'm looking for the longer term... At the moment, some of my business logic
is exposed in my user interface, mainly because because I need to bind to
the raw data.
I want to be able to remove all the business logic into a seperate set of
classes, and then bind to the various properties instead - this will allow
me to neaten my code up and remove lots of the business logic out of my UI
(I've already done some of this by writing classes that partially handle the
logic).
I'm planning to migrate to VS2005 towards the end of the year, so I may just
wait till then before I do this.
Regards
Simon
--
================================
Simon Verona
Dealer Management Service Ltd
Stewart House
Centurion Business Park
Julian Way
Sheffield
S9 1GD
Tel: 0870 080 2300
Fax: 0870 735 0011
"Steven Nagy" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> That would work. I wouldn't be able to comment on the performance of
> reflection. I use it but have never clocked it. Wouldn't be too bad I
> suppose because you aren't talking about massive amounts of objects and
> form components right? Check out the System.Type class and all its
> methods for getting lists of fields and methods and so on to get
> started with reflection.
>
> But there might be an easier way.
>
> Perhaps you only need your object to implement an interface to
> databind. I haven't investigated this specifically, but what is the
> distinct attributes of the data table and data row that allow them to
> be data bound?
> Could your object inherit from these instead? Or is changing the object
> not possible?
>
> I assume you have checked out the BindingManager and all its uses?
>
> Steven
>