I have an application that does some document handling as part of its functionality. I would like to implement a "Drive" emulator that would allow users to navigate and manage documents as if they were on a local drive. In my mind, this would be similar to how a remote session can access a local drive. But I'm not sure what the proper approach is. I don't see needing direct access to local hardware, so a driver doesn't seem quite right. But I would like users to see the root drive in File Explorer and to be able to access it in a command window via a drive identifier (i.e. MYAPP:\). File metadata is stored in SQL Azure and the files, themselves, are stored in Azure Blob containers. The folder structure would be defined by the underlying database and would not be alterable by end users. I would want to preserve our current soft delete and history retention, implemented through the application. And users would have to be authenticated.
Thoughts on most appropriate approach?
