Hello,
I'm currently in the process of setting up a bootstrapper using Burn. In the
past, we've signed our MSI files so that we don't get the yellow unknown
publisher warning dialog when prompted to elevate. However, signing the
executable generated by Burn doesn't seem to work - it looks lik
I'm very interested in the answer to this also. I will be working on
internationalizing our installer in the next couple of weeks, and I was worried
that we would have to go with the multiple MSI file route. If the localization
files can be loaded at runtime that would be great!
Kelly
On Jan 9
Hello all,
I am seeing a couple different errors on a customers machine when running a
burn based setup. The setup is about as simple as you can get - the
bootstrapper just wraps a single MSI.
Initially the customer was getting the following error: "0x800705ib - This
security ID may not be a
What version of Burn are you using? Those sound like old errors that I
> think were fixed in more recent builds of Burn. The security ID issue could
> be a problem if they mucked up the permissions of %ProgramData% or certain
> parts of the registry.
>
> The full line from the log fi
A related question: how do you support the option to change the installation
directory? I'm guessing its passed to the msi as a variable? I'm sure it's
probably easy, but my google skills are failing me :-).
Kelly
On Sep 30, 2012, at 10:02 PM, Rob Mensching wrote:
> Yes, see the WixStandardBo
Hello,
I have a customer who is receiving error 0x80070660 when running a Burn based
installer on Windows Server 2008 R2. Below is the log file. I have verified
that both the temp directory (pointed to from the TMP and TEMP environment
variables) and the c:\ProgramData directory are writable
6 matches
Mail list logo