We're in the process of updating our telerik controls to the new 2013 Q1 binaries. Since RadDragAndDropManager is deprecated, we're converting our code to use the DragDropManger.
One of the ways we use drag-n-drop is to allow the user to drag an excel icon on the screen to a control, such as a RadGridView or Listbox, and export the data from that control to an Excel or CSV file. All we do is display a SaveFileDialog after the user drops the icon on the control. After replacing RadDropAndDropManager with DragDropManager, we now get the security exception that says "Dialogs must be user-initiated." The only additional code we added between the user releasing the mouse and displaying the dialog is a single line to retrieve what control is the target of the drop from the DragDropPayloadManager. Is there something fundamentally different with the DragDropManager that makes Silverlight treat its events as not user-initiated?
One of the ways we use drag-n-drop is to allow the user to drag an excel icon on the screen to a control, such as a RadGridView or Listbox, and export the data from that control to an Excel or CSV file. All we do is display a SaveFileDialog after the user drops the icon on the control. After replacing RadDropAndDropManager with DragDropManager, we now get the security exception that says "Dialogs must be user-initiated." The only additional code we added between the user releasing the mouse and displaying the dialog is a single line to retrieve what control is the target of the drop from the DragDropPayloadManager. Is there something fundamentally different with the DragDropManager that makes Silverlight treat its events as not user-initiated?