A bit but ends up being very convenient given how important paths are to an
installer.
On Sat, Jan 22, 2011 at 5:38 AM, Wilbert van Dolleweerd <
wilb...@arentheym.com> wrote:
> 2011/1/21 Rob Mensching :
>
> > It's kinda' tricky. Properties can be treated like Directories. So name a
> > Directory/
2011/1/21 Rob Mensching :
> It's kinda' tricky. Properties can be treated like Directories. So name a
> Directory/@Id the same as your Property/@Id for the search. This might be
> useful:
> http://blogs.msdn.com/b/robmen/archive/2006/10/17/deciphering-the-msi-directory-table-part-7-directories-are
It's kinda' tricky. Properties can be treated like Directories. So name a
Directory/@Id the same as your Property/@Id for the search. This might be
useful:
http://blogs.msdn.com/b/robmen/archive/2006/10/17/deciphering-the-msi-directory-table-part-7-directories-are-properties.aspx
On Fri, Jan 21, 2
Hello,
I wrote an installer that installs my application in Program
Files\[Company Name]\[Product Name].This is a plugin for Git. I need
to install my plugin *and* add the correct hook to the Git directory.
Where Git is installed, is found out by using a registrysearch.
I'm using the registrysear
4 matches
Mail list logo