Since the issue was internal, there is no workaround other than avoid using the TreeListViewRow.DropPosition property. The only way to do it is to determine the position yourself, and use that in the drag drop logic.
Hope this makes sense!
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>