OK I'm new to MSI and MSP concepts. What is bringing me here now is Win7 (really Vista) and UAC elevation.
Our users are accustomed to installing our patches without the need for elevated privileges. In WinXP we would install into the Program Files folder (our EXE and supporting files), plus into Common App Data (our changeable data files) and Common Documents (the user's data files). We got around the permissions/elevation by giving them an option within our old installer to run CACLS to open up the permissions on the those folders to allow for the easiest monthly update user experience. That's pretty much not going to be allowed by Win7 and future releases as I understand it. And the only way to prevent the consent.exe (or UAC elevation) is to a) install per-machine, b) code-sign our setups and c) have an Administrator do the initial full setup.
Now, how to go about this? I would prefer to do what we are already accustomed to doing with our old installer which is to provide our users with a Full Setup (for their initial install) and then monthly Updates; the Update releases contain the same files as the Full Setup (except that bug fixes and enhancements are added, and the required run-times, windows OCXs and DLLs are excluded). So our Update release is typically about 30-40% of the size of the full setup; and includes only the files that we own/create (no system files).
I feel confident I can get my AI projects to produce a Full Setup MSI and an Update MSI to mirror what we have done in the past --that is, two projects (full setup project) with all of our files + runtimes + windows system files and (update project) with just our files, but:
1) will doing it this way allow us to do patching without elevation?
2) what will be the ProductCode ramifications for this sort of scenario?
Thanks.
FOLLOW US
Get the latest news in Application Packaging