Patch Using Version 9 R2

[CPSS]

I am trying to create a patch using the new Cache feature.
In the help it says that the Product Code should be the same, The Revision Code should be different, and the Upgrade Code should be the same.
In Project Properties there is not a Upgrade Code, where can I find this?

In testing we created an Install & did an uncompressed build with the Cache box checked. (the install works fine).
The Uncompressed folder was renamed 2.1.0.1.
In our .net project we modified just the rev to 2.1.0.2 and date then rebuilt the solution.
In the folder that holds the required files for our install as well as the Installaware project folder we replaced the required files (as we always do).
Next the Installaware project was opened and we updated the files in the Target directory, changed the Product Version and Revision code (Product Code Remains the same).
Then we went to the build settings and made sure Uncompressed was chosen and the Cache was checked.
Finally went to the Patches section of deployment and added "2.1.0.1/MyProj.exe" then built the patch.

What am I missing?

Thank you,
Robert Hinds

[MichaelNesmith]

Click the InstallAware button and then choose Project Settings to enter in the upgrade code.

The patching whitepaper would also be a helpful read.

[CPSS]

The only white paper on patching that I have been able to find is for older versions of Installaware and it does not reference the cache install feature.
If there is a white paper for version 9 that has a step by step how to patch using the new cache install feature I would like the link.
Note: Our customers are sent the Install & or Patch files so we are not using "Web Media Blocks".

The reason I went with version 9 was because of the new "Cache setup" feature which allows patching without the user having to select the old install file.
Reference the Installaware press release:
"Also new in InstallAware 9 setups is the ability to force setup source caching on the target system. Setups with cached sources never prompt for original installation media during patch installations, or repairs/updates of an existing installation – reducing support costs, and improving end-user satisfaction."

I have verified that the Revision, Product, & Upgrade codes are as they should be.
When I try to patch I get an error that the file ... in folder .. in cabinet can't be found.
I have a release of my software that needs to be sent out, but it is being held up until we can make sure we can patch it in the furutre.

[MichaelNesmith]

The patching whitepaper applies to version 9 R2 equally. Nothing has changed, except the addition of new source caching functionality. You should be able to follow the steps there to build and test an elementary patch. Once you have gotten that working, you will be able to narrow the issue in your current project down further. Also, if you are patching older installation projects, be sure to read the help file "upgrading from" section which contains some information on compiler variables you can use to improve compatibility with older projects.