The XML file is extracted to the same folder as your BA/UX.
string fileName = "BootstrapperApplicationData.xml";
string path =
Path.Combine(Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location),
fileName);
using (FileStream stream = new FileStream(path, FileMode.Open))
Hello? Anyone know how to get at that file? I've never seen it anywhere,
neither in my wixproj project nor in any output folder. I'm setting these
DisplayName values in a wxs file, within MsiPackage elements...
-Original Message-
From: Alexander Krivács Schrøder [mailto:alexander.schro.
I wrote a wix project that generates a msi to execute my exe.
Part of the installer, I collect data from users that I pass on to my exe. It
works fine when I run the installer UI.
Is there a way to run the installer from cmd without launching the UI, but
still collect the data from users through
Thanks Peter for the response!
I got it working by doing this.
Thanks,
Senthil.
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Tuesd
It looks more to me like a permissions issue with Windows Installer. You might
want to try (http://support.microsoft.com/kb/319624):
Method 1: Unregister and re-register the Windows Installer
Click Start, click Run, type MSIEXEC /UNREGISTER, and then click OK. Even if
you do this correctly,
Take a look in 'License_Server_20121010133953_0_License_Server.msi.log' and see
what that says, search for "value 3" the error is probably near that.
Neil
-Original Message-
From: Kelly Graus [mailto:kelly.gr...@toltech.net]
Sent: 10 October 2012 19:47
To: General discussion for Windows
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
Hi all,
I feel like a dork asking but...
If a property is a assigned value 'x' and then a custom action changes the
value to same ('x') will the MSI log file just show that the custom action
was run? i.e.
MSI (s) (CC:90) [12:48:12:634]: Doing action:
CA_TITUS_FOUNDPRODUCTPLATFORM.SetProperty
Act
Hi all,
I have a scenario in which i have a driver feature as part of my
installer...But this driver can be installed manually as well..I want to
mute/hide the driver feature if it is installed manually and *not through
the installer*..i know the conditions to see if this driver is
running(checking
The condition is: < ! [ C D A T A [ T I T U S _ F O U N D P R O D
U C T P L A T F O R M = " x 8 6 " ] ] >
I had to put spaces in since NABBLE wipes out the C D A T A
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/silly-question-re-properties-tp7
If you want to "transform" an MSI that's already installed then generate a
patch to do it. Transforms must be applied at the same time the MSI is
installed.
Phil
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: Tuesday, October 09, 2012 4:38 AM
To: 'Gener
The preprocessor is single pass today so this does not work.
On Wed, Oct 10, 2012 at 2:27 AM, wrote:
> How can I resolve $(var.Feature) as "ProjectName" part of
> $(var..TargetPath) in the following example?
>
> VS error:
> Error 157Ill-formed preprocessor function
> '$var.($(var.Feature))M
You probably need WixUI_Mondo or WixUI_FeatureTree, not WixUI_InstallDir.
That has nothing to do with major upgrades though.
-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com]
Sent: 10 October 2012 11:48
To: 'General discussion for Windows Installer XML toolset.'
Subject
This is my 1st msi...
My 2nd msi.
There iam able to remove and repair only but iam not getting change option
what to do
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 10 October 2012 15:16
To: Gen
On 10/10/2012 04:54, Bob Arnson wrote:
> On 09-Oct-12 13:43, Marco Peretti wrote:
>> light.exe : error LGHT0001: The filename, directory name, or volume
>> label syntax is incorrect. (Exception from HRESULT: 0x8007007B)
>> [C:\a\src\LockIt\MMC.Setup\MMC.Setup.wixproj]
> Try getting a verbose log so
For what ? If you mean a major upgrade, you just double-click the MSI file.
-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com]
Sent: 10 October 2012 08:45
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] upgrade code
Can u show me thr
How can I resolve $(var.Feature) as "ProjectName" part of
$(var..TargetPath) in the following example?
VS error:
Error 157Ill-formed preprocessor function
'$var.($(var.Feature))Module.TargetPath'. Functions must have a prefix (like
'fun.'), a name at least 1 character long, and matching o
Create a custom action like this:
Then schedule a custom action like this:
DBVERS
Cheers,
Rob
On 09/10/2012 17:01, Justin Hull wrote:
> We have a situation where the original install uses a property named 'DBTYPE'
> to determine optional nstall of files. On the base install, some properties
Can u show me through command line...
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 09 October 2012 20:04
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] upgrade code
It is not possible to run two installers at the same
19 matches
Mail list logo
