avoid custom provider

[John Hadjioannou]

Is there any way of setting something in web.config or IIS (or anywhere) to fool FileExplorer into thinking that a file path "c:/aaa/fff" is "~/fff" so as to avoid using a custom provider?

John

[Fiko]

Hi John,

In your case you can map the desired folder to the IIS as a virtual folder. Then you can set its virtual path to the RadFileExplorer's configuration properties.

Best wishes,
Fiko
the Telerik team

[John Hadjioannou]

Thank you, Fiko

This helps enormously, it is just what I need.

John

[David]

How did it help "enormously"? Is a custom provider slower than the default Telerik provier?

[John Hadjioannou]

It helped enormously (for me) because it meant I didn't have to write a custom provider and it seemd from the documentation that the example custom provider needed extending - I don't now remember exactly how.

John

[David]

Thanks, John.

We are using a custom provider, but its not the cuase of the issues we are facing. We currently have approx. 4000 records (representing "files" and "folders") in a DB as the basis for the file system. Our issue is that it takes about 45 seconds for the page to load.

Why can't the treeview load on demand? Its recursive nature is slowing down performance. It seems that the Treeview used in the File Explorer is not the same implementation as the Treeview control. It is constantanly resolving folder contents; particularily on

ResolveRootDirectoryAsTree.

[Petio Petkov]

Hello David,

The RadFileExplorer control uses RadTreeView, and you can get its reference by RadFileExplorer's TreeView property, e.g.

RadTreeView tree = RadFileExplorer1.TreeView;

The RadTreeView is populated via the "Load On Demand" functionality, and the demand mode is ServerSideCallback. More about RadTreeView's "Load On Demand" functionality is available here:
http://demos.telerik.com/aspnet-ajax/treeview/examples/programming/loadondemandmodes/defaultcs.aspx

On each RadTreeView's load, the FileExplorer will process two levels of directories from the current directory, e.g. /Root/Level1/Level2.
1 level: All directories which should be shown in the current folder (ROOT) -ResolveRootDirectoryAsTree method is invoked
2 level: Process all 1st level directories children - ResolveRootDirectoryAsTree method is invoked. This is needed to see whether a directory from "1st level" should have a "+" sign or not.

In case that you have several directories set for RadFileExplorer's ViewPaths property, it will process all the directories from the RadFileExplorer's ViewPaths property as described before.

To decrease the load time, please reduce the ViewPath's directories and the directories in level1 and level2.

Hope this helps.

Sincerely yours,
Petio Petkov
the Telerik team