setting property to All Users, Re: Removing "Just Me" from dialog

[David]

Phil,

Thanks for the information, I also found that one can use MsiOpenDatabase,
MsiDatabaseOpenView, etc to set any property in an MSI installation
file/deployment package. This works well to automate the build process of a
deployment project.

There's a post in installshield.iswi.general (header follows) that has a C
program that does it. One can then create a post build project and rule
(which cannot be in the deployment project itself) that invoke the C program
executable with the name of the MSI file, the property name
FolderForm_AllUsers, and the value ALL.

This is so much better than using Orca to hand edit the MSI file after
building it to specify "all users" instead of "just me" each time.

Microsoft really could have made this so much easier. I hope they do in
future releases of Visual Studio.
- allow one to specify the "all users" or "just me" property in the
deployment package build in Visual Studio 2003.
- allow one to specify pre-build and post-build rules in all project types,
not just utility projects.
- have a wizard in VS 2003 that can create a utility project.

cross-posted to the two .msi newsgroups.

header of post that includes C program example to set a property and make
the default user all users instead of just me:
From: Robert M. Dickau \(InstallShield\)
(i_wish_i_had_time_to_answer_individual_questions_through_e-mail_but_i_don't
@installshield.com)
Subject: Re: MsiOpenDatabase problem ... crappy microsoft



Newsgroups: installshield.iswi.general
Date: 2001-07-20 08:06:13 PST

 

[Phil Wilson]

Thanks for the information, I also found that one can use
MsiOpenDatabase,MsiDatabaseOpenView, etc to set any property in an MSI
installation file/deployment package. This works well to automate the build
process of a deployment project.>>>>

That's what that VBScript does, except that it uses the automation interface
instead of the APIs, but the overall way it works is the same.