Is there native support browsing multiple local drives or is a synthetic root the recommended pattern?

[Nick Shaw]

Use case: We'd like to give users the ability to browse the local file system the way Windows Explorer does aka see all local drives (C:, D:, E: etc.) at the top level and navigate into any of them within a single FileManager instance.

The FileManager's path and rootAliasName settings appear to expect a single rooted hierarchy.
 Questions:

1. Is there a built-in way to enumerate multiple drive roots at the top level of the file manager?
2. Is there a "system browse" mode equivalent to Windows Explorer's "This PC" view?
3. If not natively supported, is the recommended approach to construct a synthetic root on the backend that returns drives as top-level directory entries (with custom path parsing on the backend to detect the drive segment in incoming requests)? Or is there a different recommended pattern?

Currently we're using a custom backend (PhysicalFileProvider-style) and have a single configurable root path. We could implement multi-drive support ourselves but want to confirm there isn't an out-of-the-box mechanism we've missed.

[Praveen Sellappan]

Hi Nick ,

Greetings from Syncfusion Support.

We have considered your requirement (Support for Multiple Root folder in Blazor FileManager ) as a feature from our end, but we do not have any immediate plans to implement this feature. At the planning stage for every release cycle, we review all open features and implement them based on feature rank, customer request count, and volume wish-list.

The status of implementation can be tracked through the feedback portal link below:

Provide support for Multiple Root folder in Blazor FileManager component in Blazor | Feedback Portal

As progress unfolds, any pertinent updates regarding the feature's implementation will be relayed to you via the feedback link. We welcome any additional feedback or commentary you wish to share through this channel.

Regards,
Praveen Sellappan