Improved StorageFile APIs

# Proposal: Improved file-access APIs for UWP and AppContainer ## Summary Provide an updated version of `StorageFile` that fixes performance and usability issues in the current `Windows.Storage.Storage*` set of types. Support apps that think in terms of file paths & handles instead of StorageFile objects. ## Rationale The current `Windows.Storage.Storage*` types are designed to give programmatic access to regular files, shell namespace items, and other Windows entities backed by files. A single abstraction over all those spaces is interesting but comes with high costs - namely performance and impedence-mismatch with existing application code. Project Reunion should clearly explain why StorageFile is important and - where possible - provide lower-level access to the user's files. * The `BroadFileAccess` capability is "scary" to customers but required even for limited UWP scenarios. * Many libraries and helpers take file paths instead of objects (even instead of handles) * Apps observe serious performance costs related to using StorageFile's built in functionality * Low-level code can access the `...FromApp` API variants, but higher-level code (JS, C#) interop for them is very limited. ## Scope <!-- Please include a list of what the feature should and shouldn't do by filling in the table below. 'Must' implies that the feature should not ship without this capability. 'Should' is something we should push hard for, but is not absolutely required to ship. 'Could' is a nice-

Posted by jonwis on May 18, 2020, 9:10 PM

Tags

• support (Other)

Related issues

• some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
• I think of this as the kiosk economy.
• What a goofy comment.
• There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
• Compose support in WSLc
• [RFC] Roadmap to v2.0