Greetings WiX Users!
Not so long ago I posted my dilemma regarding Custom Actions not persisting
session data through to UI dialogs... I modified the ExitDialog to have a
button that took you to further configuration options so that it could read
in default options from the deployed App.Config fil
with the **
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
> -Original Message-
> From: Jeremy Rimer [mailto:jeremyri...@gmail.com]
EMOVE~="ALL"
NEWERFOUND
===
Here's the dialog button I wish to hide during uninstalls:
===
SHOWMODIFYCONFIGBUTTON=0
===
On Wed, Jul 14, 2010 at 10:17 AM, Jeremy Rimer wrote:
> I have one last prob
*
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
> -Original Message-
> From: Jeremy Rimer [mailto:jeremyri...@gmail.com]
Cancel="no" Text="Modify Application
> Settings" >REMOVE=ALL
>
> -Original Message-
> From: Jeremy Rimer [mailto:jeremyri...@gmail.com]
> Sent: Wednesday, July 14, 2010 11:19 AM
> To: General discussion for Windows Installer XML toolset.
> Subject:
our
> CA.
>
> -Original Message-----
> From: Jeremy Rimer [mailto:jeremyri...@gmail.com]
> Sent: Wednesday, July 14, 2010 11:04 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Conditionally Show Dialog Button based on
> Installer
&g
tuations (remove/install), or shows NO exit
dialog, and skips that step and auto-finishes and closes the installer once
the program completes ...
-J
On Wed, Jul 14, 2010 at 12:57 PM, Jeremy Rimer wrote:
> Hmmm...
>
> I did this:
> ===
>
> OnExit="s
den if REMOVE=ALL ?
>
> -Original Message-----
> From: Jeremy Rimer [mailto:jeremyri...@gmail.com]
> Sent: Wednesday, July 14, 2010 9:25 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Conditionally Show Dialog Button based on
> Install
ntegrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
> -Original Message-
> From: Jeremy Rimer [mailto:jeremyri...@gmail.com]
> Se
uld your custom action be written such that it simply exits early with a
> success code if it doesn't find the App.Config file?
>
> -Original Message-
> From: Jeremy Rimer [mailto:jeremyri...@gmail.com]
> Sent: Wednesday, July 14, 2010 8:25 AM
> To: General discussion fo
INSTALLED" to be true for
> the initial install.
>
>
> -Original Message-
> From: Jeremy Rimer [mailto:jeremyri...@gmail.com]
> Sent: Wednesday, July 14, 2010 10:25 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users
, 2010 at 10:17 AM, Jeremy Rimer wrote:
> I have one last problem before my installer is completely working:
>
> I have a custom EXIT dialog that I created called MyExitDialog that
> contains an extra button that spawns a custom dialog to gather application
> settings from the user to
I have one last problem before my installer is completely working:
I have a custom EXIT dialog that I created called MyExitDialog that contains
an extra button that spawns a custom dialog to gather application settings
from the user to write into the App.Config file that was deployed and/or
existe
Hahaha nevermind... I see that I totally got it backwards... I reversed my
OnlyDetects below and it works great... You rock... Sorry!
-Jeremy
On Wed, Jul 14, 2010 at 9:20 AM, Jeremy Rimer wrote:
> Blair, as always, thanks for your replies! Unfortunately, this time I came
> up empty :(.
quot;yes" for those properties that you won't be
> removing (such as newer versions you use to block installation, etc.)
>
> -Original Message-
> From: Jeremy Rimer [mailto:jeremyri...@gmail.com]
> Sent: Tuesday, July 13, 2010 12:36 PM
> To: General discussion for W
I've solved my App.Config issues with help from Blair (Thanks, buddy!!!),
but now I'm running into upgrade path problems...
To set the stage, I have a WIX installer that successfully deploys an
application to it's installation directory, and takes some input from the
user that calls a CA to overwr
roperties to what you
> found as your new "defaults". Then you can write them to the App.Config
> inside of the install sequence between InstallInitialize and
> InstallFinalize.
>
> -Original Message-
> From: Jeremy Rimer [mailto:jeremyri...@gmail.com]
>
I am new to WIX and have been tasked with creating an installer that does
the following:
*Deploys a build of our application without overwriting the App.Config file
for the application
*Loads the key/values in the App.Config file and prompts the user with the
"defaults" (existing values) and allo
18 matches
Mail list logo
