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.
[No sense in breaking bad habits now]
The associated PowerShell commands could use some work:
1) Get-SharedPackageContainer. It will be necessary to be able to query for all container sets previously added without knowing their names. It may be possible this in the intent with this cmdlet and it should be documented as [-Name [name]], possible the functionality should be added to this cmdlet, or perhaps as a new cmdlet like Get-SharedPackageContainers
2) The Add-SharedPackageContainer cmdlet should probably allow the path to be specified [-Path] <path>
- Dian Hartono
Microsoft
Hi, thanks for the feedback, we are looking into this.
