I'd like to setup the drop target ghost using some standard Silverlight controls, but I cannot because its type is a UserControl, which means I must define a custom control to use as the ghost.
To see if it didn't need to be a UserControl I changed it to be a UIElement, and everything worked fine. Is there a reason why it's currently defined as a UserControl?
If you agree that it can be UIElement, I can supply you with my changes, though as it's just a search and replace on UserControl for UIElement in DropTarget.cs (3 occurrences), it's a very simple change.
This allows me to define the drop target in XAML like this:
<Toolkit:WrapPanel Orientation="Horizontal" />
Aug 24, 2009 at 3:42 PM
that's indeed a shortcoming of the current release. However, in the latest version (sourcecode), I changed this to be a FrameworkElement - so in the next release, the behaviour you're looking for will be built in! :-)