my approach is to backup files when a user loads up a file which already exists in the filesystem.
I took a look at the online documentation as well as in the DBContentProvider - but without meaningful documentation it would really mean a lot of time to figure out what parameters to pass where.
And if I see constructors with 7 parameters like for DirectoryItem it is pretty hard to develop something without documentation.
And by the way - the example (DBContentProvider) deals with slashes - as well for url's (normal) as for filepaths (where I would use backslashes for the file system).
A lot of parameter are simply give as string.Empty...
So the idea of writing an own provider is good - and since the FileExplorer does not offer server methods like the RadUpload to handle uploading (storing) files it seems to be the only possible method.
BUT - due to the poor documentation it is impossible for me to build such a thing within a timeframe that seems to be acceptable.
Is there any sample for a filesystem provider?
The approach is nothing less or more than:
If a file gets deleted - create a backup copy.
If a file will be overwritten - create a backup copy.
someone asked a member to provide code in the Code Library - but the Library does not even have a section for FileExplorer.