In appxmanifest editor, Store Logos can be package-relative paths to file or MRT Keys for resource validation.
More details...
MRT supports "string" and "path"
String can be...
...literal => DisplayName="foo"
...MRT resource lookup, if prefixed with "ms-resource:" => DisplayName="ms-resource:whatever"
Path is always...
....assumed to be potentially virtual so run it through MRT
...if found then return the localized value
...if not found then return the string as the answer
Thus foo.png can resolve to bar.jpg or what/ever/matches/in/resources.pri/per/the/context/qualifiers if "foo.jpg" is a key in resource.[merge]pri
and only if not found by MRT is it foo.png
Additionally...
The Store Logo help sub-text has 4 bugs
"Relative path" - should say "Package-relative path"
"path to the image" isn't necessarily true, if it's just a string key to resolve via MRT/.pri - but not sure how to phrase this
50x50 pixel - the names are gross misnomers due to historical reasons and compat. The name doesn't meant "50 pixel by 50 pixel" it means "whatever Shell means it to mean" **
The numbers were actual sizes in win8. Then mobile came along with similar concepts but different sizes
We eventually threw in the towel and say "then name is just a string and shell can decide whatever it means to them"
's Square50x50Logo was called Square30x30Logo in Win8. Renamed in TH1
The other names are likewise misnomers e.g. Square70x70Logo doesn't mean 70 pixels...
"relative to the manifest file location" - better to cut and start off "Package-relative path or key in resources.pri..."
In appxmanifest editor, Store Logos can be package-relative paths to file or MRT Keys for resource validation.
More details...
MRT supports "string" and "path"
String can be...
...literal => DisplayName="foo"
...MRT resource lookup, if prefixed with "ms-resource:" => DisplayName="ms-resource:whatever"
Path is always...
....assumed to be potentially virtual so run it through MRT
...if found then return the localized value
...if not found then return the string as the answer
Thus foo.png can resolve to bar.jpg or what/ever/matches/in/resources.pri/per/the/context/qualifiers if "foo.jpg" is a key in resource.[merge]pri
and only if not found by MRT is it foo.png
Additionally...
The Store Logo help sub-text has 4 bugs
"Relative path" - should say "Package-relative path"
"path to the image" isn't necessarily true, if it's just a string key to resolve via MRT/.pri - but not sure how to phrase this
50x50 pixel - the names are gross misnomers due to historical reasons and compat. The name doesn't meant "50 pixel by 50 pixel" it means "whatever Shell means it to mean" **
The numbers were actual sizes in win8. Then mobile came along with similar concepts but different sizes
We eventually threw in the towel and say "then name is just a string and shell can decide whatever it means to them"
's Square50x50Logo was called Square30x30Logo in Win8. Renamed in TH1
The other names are likewise misnomers e.g. Square70x70Logo doesn't mean 70 pixels...
"relative to the manifest file location" - better to cut and start off "Package-relative path or key in resources.pri..."