I want to data bind a user control and a business object, using a
BindingSource control. The control has a 'Priority' property that takes a
'Priority' enum (High, Normal, Low). The business object has a property with
the same name, which takes an identical enum.
Data binding isn't working, and I think it's because the two enums are
different. Even though they have the same name and the same elements, they
are declared under different namespaces.
Why two enums? It lets the control and the business object be developed
independently of each other, and it reduces the coupling between them. But
apparently, it's killing the data binding between the control property and
the object property. The ability of a data binding to perform implicit
conversions does not extend this far.
Has anyone else run into a problem like this? Any suggestions? I'd like to
be able to perform a cast or a conversion as the data moves between the
control and the object, but I don't see any way to do that. Thanks in
advance.
--
David Veeneman
Foresight Systems