Thank you. While examining that site and the ones it has links to (recursive) I
found a broken
Link:
http://wix.sourceforge.net/manual-wix3/authoring_burn_package_manifest.htm
> Date: Wed, 29 Jun 2011 17:13:51 +
> From: Dan Puza
> Subject: Re: [WiX-users] Documentation for Burn
> To: Gene
I've been googling the net, off and on, for 3 weeks now, and I can't find any
documentation for Burn.exe anywhere. I understand that
it is still under development (and has been for almost a year now), but unless
the developers are planning to wait till the last minute
(BIG mistake in my opinion)
> From: David Amey
> Subject: [WiX-users] Language support
> Hello all,
>
> Simple question (I think); Is there a list of all currently supported
> languages
> for wix?
Yes. http://wix.tramontana.co.hu/tutorial/localization .
---
Please forgive me if this question is a repeat of someone else's question. I
looked but didn't find anything that seemed to provide a
workable solution.
I have an application I need to build localized install packages for using
WIX/Votive VS2010. The app is localized for 9 languages. I have
the
e happy to be able to just break the string into 4
pieces ##, #, , and the rest. The problem
is, I haven't seen (or don't remember seeing) any way to parse/substring the
contents of a property.
Dane Anderson
ACRO Service Corp.
---
that node, but I had a
legitimate, reasonable, and necessary reason (which the owner
of that needed software package knew about, and approved of at the
time).
Dane Anderson
ACRO Service Corp.
Message: 5
> Date: Fri, 5 Mar 2010 10:13:53 +0530
> From: Lisa Gracias
> Subject: Re: [WiX-users
properly
too.
Dane Anderson
ACRO Service Corp.
-Original Message-
From: wix-users-requ...@lists.sourceforge.net
[mailto:wix-users-requ...@lists.sourceforge.net]
Sent: Thursday
can make this work?
Dane Anderson
ACRO Service Corp.
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel
Bob Arnson Wrote:
>Dane Anderson (Volt) wrote:
>> I am trying to use the Certificate element to install a certificate file
>> (.pfx). The problem is
>> that Wix barfs on it.
>> When I try building the MSI, I get a message about the Certificate element
>> bei
I am trying to use the Certificate element to install a certificate file
(.pfx). The problem is that Wix barfs on it.
When I try building the MSI, I get a message about the Certificate element
being unexpected. The Sourceforge
documentation (http://wix.sourceforge.net/manual-wix2/wix_xsd_certific
OK. That's what I needed to know. Thank you.
It might be nice for that little piece of information to get
into the wix docs for the VBScriptCall attribute. It would
have saved me 2 days of hunting for ANY other documentation
about it.
Message: 2
Date: Wed, 30 Jul 2008 09:54:05 -0700
From: Alexand
[EMAIL PROTECTED] wrote
> Message: 5
> Date: Wed, 30 Jul 2008 14:13:11 +0100
> From: "Ryan O'Neill" <[EMAIL PROTECTED]>
> Subject: Re: [WiX-users] Passing parameters to a VB Script function
> Via the VBScriptCall attribute
> To: "'General discussion for Windows Installer XML toolset.'"
>
OK, yes, I know that using VBScript for custom actions is not recommended.
However I have
no choice in the matter. This is how my boss wants it done. That said, I need
to pass some
parameters to the function being called, and I can't find any (documented) way
to do it. I've
found (via google) LO
Bob Arnson <[EMAIL PROTECTED]>
Subject: Re: [WiX-users] Custom UI Dialog errors
To: "General discussion for Windows Installer XML toolset."
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Dane Anderson (Volt) wrote
Please bear with me, I'm relatively new to Wix (only worked with it for 6 months
2 years ago)and it was only up to V2 something at that time.
I am attempting to create a trial Custom UI (my first). Nothing spectacular,
just a single dialog box
with a single edit control, and a next button (fancy
o you actually return that 3? If
not, MSI is seeing your code fail and returning it for you.
Phil Wilson
-Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dane
Anderson
Sent: Thursday, November 16, 2006 4:40 PM
To: wix-users@lists.sourceforge.net
Sub
rty(S): CLIENTUILEVEL = 0
Property(S): CLIENTPROCESSID = 1688
Property(S): USERNAME = Dane Anderson
Property(S): COMPANYNAME = Intava Corporation
Property(S): VersionDatabase = 100
Property(S): ROOTDRIVE = C:\
Property(S): EXECUTEACTION = INSTALL
Property(S): ACTION = INSTALL
Property(S): IN
The problem: The install package I created works. HOWEVER, the customer
runs this under SMS
in some unattended mode. There is no way to control whether our
application or another application
which uses our application is running at the time of install, or not. If
it is running, it causes msiexec
to
Title: Suppressing Reboot
I have an install package that I wrote a few weeks ago. As long as conditions are right it
properly installs and uninstalls the software package. What constitutes wrong conditions
you ask? Sometimes the application or some parts of it are running at the time of
in
Have you tried the tutorial at http://www.tramontana.co.hu/wix/ ?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Walton
Sent: Tuesday, October 31, 2006 9:18 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] HELP. Can someone send me a COM
anything
on that particular subject).
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dane Anderson
Sent: Tuesday, October 17, 2006
2:06 PM
To:
wix-users@lists.sourceforge.net
Subject: [WiX-users] Setting
Permissions
OK,
I know that file/directory permissions are
Title: Setting Permissions
OK, I know that file/directory permissions are set using the element. However I must be using
It wrong, because it not only did NOT set the permissions I told it (or thought I was telling it) to, it cleared
ALL permissions. The Wxs File contains:
e key.
Many thanks for your help.
> -Original Message-
> From: Dane Anderson
> Sent: Monday, October 16, 2006 12:09 PM
> To: 'wix-users@lists.sourceforge.net'
> Subject: RE: [WiX-users] Uninstall Custom action
>
> Sorry to be bending your 'ears&#x
nstall Custom action
>
> REMOVE="ALL" is the right syntax. Must be time for a log:
>
> Msiexec /x {your productcode guid} /l*v somepathtoalog.log
>
>
> Phil Wilson
>
>
> -----Original Message-
> From: [EMAIL PROTECTED]
> [mailto:
e-
> From: Wilson, Phil [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 16, 2006 10:18 AM
> To: Dane Anderson; wix-users@lists.sourceforge.net
> Subject: RE: [WiX-users] Uninstall Custom action
>
> Properties are case-sensitive in that syntax you're using. Try "ALL&
users@lists.sourceforge.net
> Subject: Re: [WiX-users] Uninstall Custom action
>
> A condition of REMOVE="ALL" should be fine for uninstall CAs.
>
> Rob
>
> Dane Anderson wrote:
> > I have an install package that I am attempting to put together. In
the
> &
26 matches
Mail list logo
