ArithmeticException is thrown on RadSaveFileDialog's ShowDialog call, when the device model profile of the OS (from the Color Management menu) is set to sRGB virtual device model profile.

The profile should be set through the Change system defaults menu. This setting is accessed by opening the Color Management menu in the OS, then select the Advanced tab, then click on Change system defaults... In the newly opened dialog click Advanced again and change the Device profile to sRGB virtual device model profile.

This is actually a bug in the WPF framework that is reported here.

The important part of the exception stacktrace is the following:

System.ArithmeticException: Overflow or underflow in the arithmetic operation.
--- End of inner exception stack trace ---
at System.Windows.Media.Imaging.ColorConvertedBitmap.FinalizeCreation()
at System.Windows.Media.Imaging.ColorConvertedBitmap..ctor(BitmapSource source, ColorContext sourceColorContext, ColorContext destinationColorContext, PixelFormat format)
at System.Windows.Media.Imaging.BitmapSource.CreateCachedBitmap(BitmapFrame frame, BitmapSourceSafeMILHandle wicSource, BitmapCreateOptions createOptions, BitmapCacheOption cacheOption, BitmapPalette palette)
at System.Windows.Media.Imaging.BitmapFrameDecode.FinalizeCreation()
at System.Windows.Media.Imaging.BitmapFrameDecode..ctor(Int32 frameNumber, BitmapCreateOptions createOptions, BitmapCacheOption cacheOption, BitmapDecoder decoder)
at System.Windows.Media.Imaging.BitmapDecoder.SetupFrames(BitmapDecoder decoder, ReadOnlyCollection`1 frames)
at System.Windows.Media.Imaging.BitmapDecoder.get_Frames()
at System.Windows.Media.Imaging.BitmapFrame.CreateFromUriOrStream(Uri baseUri, Uri uri, Stream stream, BitmapCreateOptions createOptions, BitmapCacheOption cacheOption, RequestCachePolicy uriCachePolicy)
at System.Windows.Media.ImageSourceConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
at System.Windows.Baml2006.TypeConverterMarkupExtension.ProvideValue(IServiceProvider serviceProvider)

The following exception is thrown when a new file dialog is created on a separate thread and its ShowDialog method is invoked.
InvalidOperationException: "The calling thread cannot access this object because a different thread owns it."

This happens also if you define an ExplorerControl in any Window opened on another UI thread.


To work this around make sure that you use RadFileDialog and ExplorerControls only on the main UI thread. For example:

App.Current.Dispatcher.BeginInvoke(new Action(() =>
{
     RadOpenFileDialog openFileDialog = new RadOpenFileDialog();
     openFileDialog.ShowDialog();
}));

Currently, the RadFileDialogs does not provide an API option for applying additional filtering of the already filtered files.

We could extend the filtering functionality of the RadFileDialogs control.

Create a property that allows to show the UNC name instead of just the drive's letter or change the implementation of the control so this can be achieved by code.

A binding error is thrown in RadOpenFolderDialog when it is shown.

 System.Windows.Data Error: 40 : BindingExpression path error: 'IsSearchActive' property not found on 'object' ''OpenFolderDialogViewModel' (HashCode=65514185)'. BindingExpression:Path=IsSearchActive; DataItem='OpenFolderDialogViewModel' (HashCode=65514185); target element is 'FileDialogSearchPane' (Name=''); target property is 'IsSearchViewActive' (type 'Boolean')