MSIX Packaging Tool Default (Store) Logo

%3CLINGO-SUB%20id%3D%22lingo-sub-1886505%22%20slang%3D%22en-US%22%3EMSIX%20Packaging%20Tool%20Default%20(Store)%20Logo%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1886505%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20creating%20a%20package%2C%20the%20MMPT%20will%20create%20a%20variety%20of%20png%20assets%20under%20the%20Assets%20folder.%26nbsp%3B%20Among%20these%20are%20a%20series%20of%20pngs%20with%20names%20matching%20%22StoreLogo*png%22.%26nbsp%3B%20Most%20have%20%22.scale-%23%23%23%20added%20to%20them%20for%20systems%20with%20specific%20text%20scaling%20options%2C%20but%20there%20is%20a%20file%20created%20without%20that.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20file%2C%20without%20a%20scaling%20option%2C%20is%20created%20as%20a%20256x256%20pixel%20file%2C%20which%20is%20larger%20than%20the%20largest%20of%20the%20scale%20specific%20files%20(which%20max%20out%20at%20200x200)%2C%20and%20is%20then%20listed%20in%20the%20AppXManifest%20as%20the%20%22default%22%20for%20the%20logo.%26nbsp%3B%20More%20importantly%2C%20this%20image%20is%20a%20generic%20logo%20from%20the%20packaging%20tool%20and%20has%20nothing%20to%20do%20with%20the%20application%20being%20packaged.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20seems%20that%20either%20this%20default%20should%20be%20eliminated%2C%20or%20created%20like%20the%20others%20(from%20one%20of%20the%20shortcut%20icons%20but%20resized)%2C%20or%20it%20should%20just%20be%20one%20of%20the%20other%20created%20ones.%26nbsp%3B%20If%20that%20existing%20default%20logo%20is%20ever%20used%20under%20some%20strange%20scenario%2C%20it%20would%20look%20wrong%20no%20matter%20what.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2062737%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20Packaging%20Tool%20Default%20(Store)%20Logo%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2062737%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F146612%22%20target%3D%22_blank%22%3E%40TIMOTHY%20MANGAN%3C%2FA%3E%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20issue%20has%20been%20fixed%20in%20the%20latest%20release%20of%20the%20MSIX%20Packaging%20Tool.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fpackaging-tool%2Frelease-notes%2Fhistory%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMSIX%20Packaging%20Tool%20release%20notes%20-%20MSIX%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%2C%3C%2FP%3E%0A%3CP%3ESharla%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2063198%22%20slang%3D%22en-US%22%3ERE%3A%20MSIX%20Packaging%20Tool%20Default%20(Store)%20Logo%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2063198%22%20slang%3D%22en-US%22%3EThank%20you%20for%20this.%20It%20would%20be%20good%20to%20have%20a%20little%20more%20detail%20listed%20in%20those%20release%20notes.%20For%20example%2C%20the%20logo%20issue%20fix%20is%20listed%2C%20but%20not%20listed%20is%20that%20the%20tool%20now%20generates%20unique%20asset%20images%20for%20each%20shortcut%20--%20something%20we%20have%20been%20waiting%20for%20a%20long%20time.%20You've%20finally%20addressed%20that%20shortcoming%20and%20should%20be%20proud%20to%20let%20everyone%20know!%3C%2FLINGO-BODY%3E
MVP

When creating a package, the MMPT will create a variety of png assets under the Assets folder.  Among these are a series of pngs with names matching "StoreLogo*png".  Most have ".scale-### added to them for systems with specific text scaling options, but there is a file created without that.

 

This file, without a scaling option, is created as a 256x256 pixel file, which is larger than the largest of the scale specific files (which max out at 200x200), and is then listed in the AppXManifest as the "default" for the logo.  More importantly, this image is a generic logo from the packaging tool and has nothing to do with the application being packaged.

 

It seems that either this default should be eliminated, or created like the others (from one of the shortcut icons but resized), or it should just be one of the other created ones.  If that existing default logo is ever used under some strange scenario, it would look wrong no matter what.

 

 

3 Replies

Hi @TIMOTHY MANGAN

 

This issue has been fixed in the latest release of the MSIX Packaging Tool. MSIX Packaging Tool release notes - MSIX | Microsoft Docs

 

Best,

Sharla

Thank you for this. It would be good to have a little more detail listed in those release notes. For example, the logo issue fix is listed, but not listed is that the tool now generates unique asset images for each shortcut -- something we have been waiting for a long time. You've finally addressed that shortcoming and should be proud to let everyone know!
MSIX In this how-to video I show you the exact steps that you need take to create a custom splash screen logo for an MSIX package. Branding a virtual packag...