Message from discussion Is Install Per User or Per Machine?

From: "Phil Wilson" <pdjwil...@nospam.cox.net>
References: <266bedb4.0408231518.62377a82@posting.google.com>
Subject: Re: Is Install Per User or Per Machine?
Date: Mon, 23 Aug 2004 21:41:11 -0700
Lines: 30
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Message-ID: <#cC7BRZiEHA.3996@tk2msftngp13.phx.gbl>
Newsgroups: microsoft.public.platformsdk.msi
NNTP-Posting-Host: ip68-96-84-20.oc.oc.cox.net 68.96.84.20
Path: g2news1.google.com!news1.google.com!news.glorb.com!newsfeed00.sul.t-online.de!t-online.de!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl

Why can't ALLUSERS be used?
-- 
Phil Wilson
[MVP Windows Installer]
"Dennis Bareis" <dbar...@labyrinth.net.au> wrote in message
news:266bedb4.0408231518.62377a82@posting.google.com...
> Hi,
>
> This is either a hole in the API or I'm missing something obvious.
>
> During an install how can I tell if the install is per-user or
> per-machine?
> Windows Installer obviously makes this decision at some stage.
> The ALLUSERS property can't be used.
> A verbose log doesn't show any likely properties.
> There appears to nothing in the condition syntax to support it.
> The Mode method of the session object doesn't supply it.
> No other objects seem to supply it.
>
> Any ideas?  At this stage I'll call this a limitation (if only in
> documentation)...
>
> I probably wouldn't care too much if it wasn't for the limitation in
> the "Environment" table where unlike the "Registry" table I can't
> leave the per-user/per-machine decision up to Windows Installer.
>
> Thanks for any info,
> Dennis