...for .NET 4.5. Anyone has a more detailed walkthrough?
I am trying to figure out the nw tracingmechanism for a windows service we
distribute to various computer as a HPC cluster (so they do processing jobs in
the background). I would love to use ETC:
I have created a tracing class in a
I had those two lines already, but like I said they were in Fragment element
instead of in Bundle element. When I moved them to Bundle element the
problem was gone. My question is if this is requirement or a bug? Do
WixVariable elements must reside in Bundle element?
--
View this message in
I would really appreciate some help with this. As it is, I can't
upgrade to Burn because the installer no longer has privileges to
write to ProgramFiles in per-user mode.
I found this post from 2009:
http://stackoverflow.com/a/678190
Sadly, the Windows Installer doesn't support that. Some
That Windows for you. Existing CMD consoles don't get updated environment
variables. Happens with no installer involved, too. For example, open a CMD
Prompt. Then go to your Environment variables and alter your Path. The altered
Path won't show up in the running CMD Prompt, but new CMD Prompts
The issue appears to be this from the log:
=
Product registered: entering maintenance mode
Determined that existing product (either this product or the product being
upgraded with a patch) is installed per-machine.
==
..meaning that the same product is being
I had a vaguely similar problem; I had to remove and existing installation that
didn't work in a way that was compatible with burn. To solve I wrote some code
(a console app) to uninstall the old code and clean up and then just scheduled
it with burn, I was able to detect that it hadn't run by
Could you not change your product code of your MSI, and enforce this new one is
per machine only? Then with burn, you could detect the previous product code
and uninstall it if found (this would only work if the same user was installing
the per machine as the one who installed it per user). Or
I have an installation package that seems to be working on all of the
machines we've tested on so far except one.
The errors indicated in the log are:
06F4:1D44][2012-12-18T14:05:28]e000: Error 0x80070643: Failed to install
MSI package.
[06F4:1D44][2012-12-18T14:05:28]e000: Error 0x80070643:
You need to look in the log file for RapidFETAppSetup.msi that should show the
actual error (search for value 3 and look near there).
Neil
-Original Message-
From: Dave Gilmour (FET) [mailto:d...@fetcorp.com]
Sent: 18 December 2012 21:15
To: General discussion for Windows Installer XML
That's the generic ERROR_INSTALL_FAILURE - Fatal error during
installation. error code. Take a look at the appropriate MSI log file to
see why the MSI is failing.
On Tue, Dec 18, 2012 at 1:14 PM, Dave Gilmour (FET) d...@fetcorp.comwrote:
I have an installation package that seems to be working
I'm converting some InstallShield installers to Wix. I was planning to use
Heat to harvest the dynamic directories so our process can remain the
same. I wanted to use the -ag flag to generate component guids at compile
time.
The directory is to be installed under the IIS wwwroot folder.
I have a 32 bit installer, it can run on a 32 bit or a 64 bit OS...
On the 32 bit OS only the 32 bit pre requisites are run, but on the 64 bit
OS both 32/64 bit pre requisites are run.
The installer verifies that the pre requisites are installed (ya its
overkill but that is another story)...
On
Yes, feature is good to go now.
On Tue, Dec 18, 2012 at 2:14 PM, john.burak john.bu...@telvent.com wrote:
I'm converting some InstallShield installers to Wix. I was planning to use
Heat to harvest the dynamic directories so our process can remain the
same. I wanted to use the -ag flag to
I always use a verbose log file to check the values of Properties since
that where I usually make my mistakes.
On Tue, Dec 18, 2012 at 3:14 PM, StevenOgilvie sogil...@msn.com wrote:
I have a 32 bit installer, it can run on a 32 bit or a 64 bit OS...
On the 32 bit OS only the 32 bit pre
I have a 3rd party merge module (MSM) which consists of an SDK. I want to be
able to detect that the SDK is already installed (which i've done with
RegistrySearch).
Is it possible for WIX to decide either to install the MSM if the
RegistrySeach returns false and to not to install if the
The thing is... its windows7 32 bit, so that registry key won't be there which
means the value should be 0 and that VersionNT64 is false so my logic is
incorrect but I have tried multiple things :(
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent:
Oops I should have said as well...
The 32 bit version is checked and correct since it is installed so the logic is
correct for the 32 bit check of Property Id=SQLSYNCX86SEARCH Value=0 it's
the 64bit check that is failing on the 32 bit OS
-Original Message-
From: Rob Mensching
You could Condition the Feature the Merge Module is merged into.
On Tue, Dec 18, 2012 at 5:48 PM, vlicaros vlica...@counterpath.com wrote:
I have a 3rd party merge module (MSM) which consists of an SDK. I want to
be
able to detect that the SDK is already installed (which i've done with
18 matches
Mail list logo
