martin lavelle wrote:
> The Microsoft reference on the CreateFolders Actions says "The installer
> creates folders both for components that run locally and run from source".
> Doesn't this mean CreateFolders is officially approved for use during Admin
> Installations?
No. I think you're still
The Microsoft reference on the CreateFolders Actions says "The installer
creates folders both for components that run locally and run from source".
Doesn't this mean CreateFolders is officially approved for use during Admin
Installations? (See below for link)
If the AdminExecuteSequence is in
martin lavelle wrote:
> My intention is to create empty folders during an Admin Installation.
That's not how an admin installation works: It's essentially just your
source media laid out. MSI enforces restrictions on actions in the
AdminExecuteSequence table; see "Suggested AdminExecuteSequence
My intention is to create empty folders during an Admin Installation. The
deployed application can be ran by multiple users from a network location, or
be deployed locally, and the application requires empty folders in both
scenarios. I'm sorry if that was not clear.
In my opinion the produ
4 matches
Mail list logo
