Download RegSpy2 from
http://www.installsite.org/pages/en/msi/tips.htm
You'll need to do some work to convert it to Wix code. Search this list for
regspy2
-Original Message-
From: Anil Patel [mailto:apatel...@googlemail.com]
Sent: 07 July 2011 10:57
To: wix-users@lists.sourceforge.net
Thanks Peter.
I'll try that.
Anil.
On Thu, Jul 7, 2011 at 11:08 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote:
Download RegSpy2 from
http://www.installsite.org/pages/en/msi/tips.htm
You'll need to do some work to convert it to Wix code. Search this list for
regspy2
-Original
Hi,
I'd like to follow up this thread, because I found out a issue, the
example here seems not working:
http://wix.sourceforge.net/manual-wix3/run_program_after_install.htm
In this tutorial, it said The Value property uses the special #
character to tell WiX to look up the full installed path of
You can find links to RegSpy2 at
http://www.installsite.org/pages/en/msi/tips.htm (scroll down to the heading
Capture Self-Registration Information)
Use it to generate .reg file which you can then pass to heat.exe to transform
into a WiX fragment. You will probably want to clean up the WiX
http://msdn.microsoft.com/en-us/library/aa368609.aspx says the following:
.If a substring of the form [#filekey] is found, it is replaced by the full
path of the file, with the value filekey used as a key into the File table. The
value of [#filekey] remains blank and is not replaced by a path
I just wanted to report that writing a BA with .NET 2.0 and WinForms works very
well. That was the requirement I just completed and I had no troubles at all
with a very complicated BA.
The only drawback was that I was so used to .NET 4 constructs that I felt naked
going back to .NET 2.0. :)
Hi Rob,
I added the two standard actions into the InstallExecuteSequence as you
described (without attributes), but the result is the same. Those merge module
files are still not getting registered when feature Server is not selected for
installation. It seems the registration of the files is
Hello,
Our WIX setup installs a windows service after asking logon account through
a custom UI dialog..
The service starts after installation succeeds.
Entire setup requires elevated privileges.
Hoping for any pointers regarding couple of questions:
*Question 1*
On attempting Repair from
A repair is basically a reinstall, and it can't do that unless you can arrange
to supply those credentials again. They're not remembered on your behalf.
Phil Wilson
949-639-1680
-Original Message-
From: Sameer Arora [mailto:arora...@gmail.com]
Sent: Thursday, July 07, 2011 9:49 AM
Are the Components that contain the registration being installed? A verbose
log file will tell all.
On Thu, Jul 7, 2011 at 9:26 AM, Wang, Miaohsi miaohsi.w...@invensys.comwrote:
Hi Rob,
I added the two standard actions into the InstallExecuteSequence as you
described (without attributes),
Dude, exactly! smile/
On Thu, Jul 7, 2011 at 8:48 AM, John Robbins j...@wintellect.com wrote:
I just wanted to report that writing a BA with .NET 2.0 and WinForms works
very well. That was the requirement I just completed and I had no troubles
at all with a very complicated BA.
The only
How are you adding the registry key? By default, any registry keys defined
in your MSI should be removed at uninstall.
On Thu, Jul 7, 2011 at 3:05 AM, Valentin Bogdanov
valen...@serendipity-interactive.com wrote:
Hi
I have the following problem. I am adding a registry value to
Thanks Pally!
I have figured the caused reason:
I do changed the INSTALLDIR after CostFinalize, so does the Wix sample.
but I forgot to call MsiSetTargetPath or publish SetTargetPath
ControlEvent, it caused the installer doesn't resolve.
after I add it, it works now.
thanks!
William L.
On Thu,
13 matches
Mail list logo
