Forum Discussion
Shared Package Container XML Format feedback
Some feedback on the new Shared Package Container:
We always love a schema file. Just saying...
In addition to the previous feedback, the documentation currently is not to the level of other x...
[Yeah, replying to my own post...]
Additional feedback. The need to specify the PackageFamilyName does cause the issue of having to install the package to find out the name. It appears that the only way to determine the PublisherId (the hash) used in the PackageFamilyName is to install the package to get the value out or powershell, or write some C++ code to perform the encoding of the publisher field. We should be able to provide the PackageName and Publisher field.
Additional feedback. The need to specify the PackageFamilyName does cause the issue of having to install the package to find out the name. It appears that the only way to determine the PublisherId (the hash) used in the PackageFamilyName is to install the package to get the value out or powershell, or write some C++ code to perform the encoding of the publisher field. We should be able to provide the PackageName and Publisher field.
Dian Hartono
Microsoft
MicrosoftThanks for the feedback, yes IT Pros will need to know the PackageFamilyName in order to populate the .xml file to define the Shared Package Container. This is currently how we identify packages in the platform. Note that this is not dependent on the version of the app.