New to Telerik UI for ASP.NET AJAX? Download free 30-day trial

Use RadFileExplorer with physical and shared folder paths


The basic steps needed to implement a custom provider, that works with files and folders from a physical (or shared) file system are shown in the attached demos. A GenericHandler.ashx is used in the examples in order to serve the files to the browser. The different file types should be handled in this .ASHX file in order to force the browser to download or open a file.


The provider supports shared folder's paths like "\\Path\Folder" as well. The mapping is done in the MappingFile.mapping file as shown in the attached demo.


The main problem in this case is that we are working with physical paths that we do not want to pass (show) to the client. In the address bar of the RadFileExplorer we need to show custom paths, which uniquely identify the items in the FileExplorer (and on the server). In this case, a strong mapping between the physical path and the virtual path (that will be shown in the address bar) is necessary.
In the example, which you can download from here, the mapping is specified in the MappingFile sfile. You can add another mapping in the .mappingfile and then use the mapped physical paths in the ViewPath, DeletePath or UploadPath collections of the FileExplorer. In the demo, the GetPhysicalFromVirtualPath function is widely used, and this function gets the mapped physical path from the passed virtual path.

This is an example configuration using CustomFileSystemProvider:

protected void Page_Load(object sender, EventArgs e)
string[] viewPaths = new string[]

string[] uploadPaths = new string[]

string[] deletePaths = new string[] 

    RadFileExplorer1.Configuration.ViewPaths = viewPaths;
    RadFileExplorer1.Configuration.UploadPaths = uploadPaths;
    RadFileExplorer1.Configuration.DeletePaths = deletePaths;
    RadFileExplorer1.Configuration.SearchPatterns = new []{"*.*"};
    RadFileExplorer1.Configuration.ContentProviderTypeName = typeof(CustomFileSystemProvider).AssemblyQualifiedName;

When a custom provider is used, the security part needs to be implemented as well - for example : the upload and delete logic depending from the path set.


A GenericHandler is used in order to serve the files to the browser. Please note that the different browsers handle the file types in a different manner. You can control browsers' action, specifying the Response.ContentType and adding a header with the Response.AddHeader method before writing the file to the browser. This is a common programming task and needs to be done in the used GenericHandler. The implemented code in the demo, forces the browser to download files with .jpg and .docx extensions.


Please, read the comment in the beginning of the MoveDirectoryfunction. Also, in the earlier versions of the control the CheckDeletePermissionsmethod does not exist and needs to be removed. Also, a new method is added in the FileBrowserContentProvider - CheckReadPermissions (starting from version 2010.2.286) and It should be overridden as well in order to ensure that the content provider will work properly.

You can download the sample files from here. There are both C# and VB.NET versions inside the archive.

In this article