Thanks Nicholas, I will give that a try when I get home and if it
works I'll post the solution; if not, there will be more lamentations
and gnashing of teeth.

Regards,

Anthony

On Jan 16, 11:52 am, "Nicholas Paldino [.NET/C# MVP]"
<m...@spam.guard.caspershouse.com> wrote:

Hey Nicholas,

The link you sent was an excellent resource and when I read through it
the lightbulb switched on and I thought to myself "Of course, why
didn't I think of that?!"

In the end it turned out to be simpler than what you mentioned in your
email; there's no need to specify a callback at all, the only thing we
need to do is create the same dependency property on the user control
as follows :

public class MyUserControl : UserControl
...
public DateTime ExposedDateTimeValue
  {
  get
     {
     return SomeClass.DateTimeValue;
     }
  set
     {
     SomeClass.DateTimeValue = value;
     }
  }

Register it as follows (notice that I use AddOwner method here so as
not to re-create the same type of dependency property; we just want to
re-use it) :

public static readonly DependencyProperty ExposedDateTimeValueProperty
= SomeClass.DateTimeValueProperty.AddOwner(typeof(MyUserControl), new
FrameworkPropertyMetadata(new DateTime?(),
FrameworkPropertyMetadataOptions.BindsTwoWayByDefault));

and then in the constructor of my user control I do as follows :

Binding binder = new Binding("DateTimeValue");
binder.Source = this;
binder.Mode = BindingMode.TwoWay;
BindingOperations.SetBinding(helper, SomeClass.DateTimeValueProperty,
binder);

So the solution to it all was to create a simple binding between the
two properties... duh! However, I would like to say that there should
be some mechanism built into the CLR that generates this binding
automatically sort of the way it hides the complexity behind
delegates.

Thanks for your assistance Nicholas!

Regards,

Anthony

On Jan 16, 11:52 am, "Nicholas Paldino [.NET/C# MVP]"
<m...@spam.guard.caspershouse.com> wrote: