Change package ID prefix when submitting Metro App to Windows Store
I'm about to submit a Metro-style app to the Windows store, and when I create a package for store submission in Visual Studio, my package ID is automatically set to "XXXXXXXX.MyAppName", where XXXXXXXX is an 8-character hex string that appears to be generated automatically by Visual Studio based on my developer account.

If I change the &lt;NamespacePrefix&gt; element of Package.StoreAssociation.xml and the package ID in my manifest, and then run Store -> Create App Package, my changes are overridden (always with the same value of XXXXXXXX).

If I build an appx package externally and submit it to the store, it's rejected for not having a package id of "XXXXXXXX.MyAppName".

Does anyone know of a way to set this prefix so that it's not a random hex string, but instead (for example) "MyCompanyName"?

I've posted questions both in the MS developer forums and to MS support directly; if I hear anything through those channels I will update this question as well.  Just hoping that someone at SO has already been through this...
Change package ID prefix when submitting Metro App to Windows Store
===

I'm about to submit a Metro-style app to the Windows store, and when I create a package for store submission in Visual Studio, my package ID is automatically set to "XXXXXXXX.MyAppName", where XXXXXXXX is an 8-character hex string that appears to be generated automatically by Visual Studio based on my developer account.

If I change the &lt;NamespacePrefix&gt; element of Package.StoreAssociation.xml and the package ID in my manifest, and then run Store -> Create App Package, my changes are overridden (always with the same value of XXXXXXXX).

If I build an appx package externally and submit it to the store, it's rejected for not having a package id of "XXXXXXXX.MyAppName".

Does anyone know of a way to set this prefix so that it's not a random hex string, but instead (for example) "MyCompanyName"?

I've posted questions both in the MS developer forums and to MS support directly; if I hear anything through those channels I will update this question as well.  Just hoping that someone at SO has already been through this...