Provide a version of the MRT resource management & packaging system even for unpackaged applications. While MUI is supported, MRT is more powerful and supported directly by various "visual" tooling, and generates code for direct use by apps.
Rationalehttps://docs.microsoft.com/en-us/windows/uwp/app-resources/ is a powerful system for packaged applications to deliver resources (images, XAML, html, xml, or any other data) to enable localization or customized content for form factors. Unpackaged applications would benefit from the same ability to easily use Visual Studio and other tools to build and consume resources. https://docs.microsoft.com/en-us/previous-versions/windows/apps/jj552947(v=win.10) describes the Resource Manager in depth.
Scope Capability Priority Use .PRI files in unpackaged applications Must Use the same API surface for resources between packaged, unpackaged, UWP, and Win32 Must Let developers use custom-defined resource qualifiers in their apps Should Provide sample hooks for common app frameworks (WinUI3, Electron, CEF, Flutter, React*) Could Provide drop-in replacements for the Win32 *Resource family of APIs Could Require apps to get packaged to use the features Won'tSamuel12321 and MarkIngramUK
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4