NOTE: We are still working on this manual, so the information presented here is incomplete and subject to change.

To prepare update for WebsitePanel in Web Application Gallery you can use a test feed file that can be found in attachments to this post. This feed contains only single record that has exact structure and data that Web App Gallery requires product vendors to supply in order to be listed in the feed.

Prerequisites:

Once finished with prerequisites, we can proceed with editorial routine. So, this test feed file should be opened up in Visual Studio or your favorite XML editor in order to adjust some values to be able to test the record data correctness before sending it for publishing.

First, you need to change value of <productId /> element value to string something like WebsitePanel<version number> for testing purposes only (!). This step is required because Web Platform Installer requires every product to have a unique id (see highlighted text) otherwise you won’t be able to do any testing. Here is the snippet from my test feed after this step:

image

Then we should adjust <title /> and <version /> elements correspondingly to reflect the change in product’s version number. Here is the snippet from my test feed:

image

Afterwards, we need to take care of <updated /> and <published /> elements representing the dates when product published and updated. In case of testing or releasing both elements would be referencing the same date. These elements are very important as they help to track changes made to the product and they are in use of Web Platform Installer. Here is the snippet from my test feed:

image

Finally, we need to adjust the information buckets related to the product installers of x86 and x64 flavors as there are two corresponding <installer /> records. Very important to set this information correctly…

image

Elements <fileSize /> and <installerURL />  are self-describing and we can easily find correct values, however <sha1 /> element is somewhat we need to figure out with some additional tools, like Microsoft File Checksum Verifier. We run this tool against the installer distributive and the output  is the key that we are looking for. Here is the snippet from console output:

Last edited Jan 16, 2012 at 6:17 PM by ptsurbeleu, version 2