On Tue, Dec 23, 2008 at 12:53 PM, Curt Hagenlocher wrote:
> Given that there are clean APIs for pulling the data out, what are your
> objections to using the installer data?
Oh, nothing too convincing - just an irrational aversion to using
"sekrit" information. Also, the WMI query is a bit slow.
Given that there are clean APIs for pulling the data out, what are your
objections to using the installer data?
On Tue, Dec 23, 2008 at 11:40 AM, Jeff Hardy wrote:
> Hi,
> Thanks for the tips! To add a little bit more info, I'm working in
> Powershell for various reasons, so P/Invoke is out of th
Hi,
Thanks for the tips! To add a little bit more info, I'm working in
Powershell for various reasons, so P/Invoke is out of the question.
Using WMI is easy enough, but I'd prefer not to be mucking around
inside Windows Installer if I can help it.
Is there any reason to not include an entry (e.g.
Console.WriteLine(mo["InstallLocation"]);
>
> }
>
>
>
> --
>
> Oleg
>
>
>
> *From:* users-boun...@lists.ironpython.com [mailto:
> users-boun...@lists.ironpython.com] *On Behalf Of *Curt Hagenlocher
> *Sent:* Tuesday, December 23, 2008 9:28
(mo["InstallLocation"]);
}
--
Oleg
From: users-boun...@lists.ironpython.com
[mailto:users-boun...@lists.ironpython.com] On Behalf Of Curt Hagenlocher
Sent: Tuesday, December 23, 2008 9:28 AM
To: Discussion of IronPython
Subject: Re: [IronPython] Detecting IronPython Installation
Looking at the WiX source (is that included in the source distribution?), it
doesn't appear that we're deliberately writing this information into the
registry. But the MsiProductInfo function should be able to retrieve it
from the sekrit Windows Installer stash.
http://www.pinvoke.net/default.aspx
Jeff Hardy wrote:
Hi,
Does the IronPython 2.0 installer write the installation directory to
a registry key (besides the WIndows Installer keys)? If not, could
that be added to a future release? Or, is there another way to get the
installation directory?
-Jeff
