Web Deployed patches with passwords

[paul.fitzpatrick@avondata]

I have a problem whereby I cannot build patches; I have finally managed to sort this problem out and it is because I specified a password on original base installer.
To test this out I created a small test IA Project, and produced a Web Depolyed project with a password, on attempting to perform a patch I get an error. If I rebuild the web deployed project without a password and create a patch - It works.

This leaves me with potentially a BIG problem. If I rebuild my project again now without a password, will the patch I create against it work for all my customers who have already installed my base installer???

[MichaelNesmith]

Password protected setups cannot be patch references because there is no way to deduce what password might have been used in them.

However, using the same setup without a password will yield a patch that works successfully. The actual password values are immaterial, as long as the packed data is accessible.

[paul.fitzpatrick@avondata]

In doing another build, will this not re-create fresh MSI tables, possibly with different names that the MSI will choke on in the future?

I have already released by base installer, and hundreds of users have installed it!

I need to know that I can rebuild the original setup without a password, and create a patch that will then work absolutly fine with the original password protected version.

[MichaelNesmith]

When you re-build the installer from the same sources, as long as the revision code stays the same, and the setup script is the same, you should be fine.

You may also try manually extracting the files, and feeding them in as a patch reference as an alternative, if the above is not possible.

[paul.fitzpatrick@avondata]

Thanks for the reply, I think I may have to go for the later suggestion. Can you give me some brief instructions on how to go about manually extracting the files and feeding them in

Thanks