On 07/03/2013 19:37, Alain Forget wrote:
> 2) I only want the InstEXEs to run during installation (and not when
> uninstalling). Thus, since there is the special REMOVE="ALL" to
> denote "do this only if uninstalling", is there an equivalent I need to use
> to specify "do this only if installing"
Hi All dev
I just need to understand how can i use xmlconfig to validate xml element
values & add the same if not found.
for example
ABC
XYZ/
how do i add one more element user & check BDC user is there or not.
if not it should add BDC
Please reply ASAP.
Thanks
--
Thank you. You bought up something I hadn't considered: repairs. So on a
repair, I would like the uninstall exes AND the install
exes to run. Suggestions on how to make that happen with inner text conditions?
Alain
-Original Message-
From: Rob Hamflett [mailto:rob_hamfl...@sn.scee.net]
There's more than just Install, Uninstall & Repair to consider for your custom
actions. dblock (creator of dotnetinstaller) has a handy WiX include you can
use to save time writing all the conditions yourself ->
http://code.dblock.org/msi-property-patterns-upgrading-firstinstall-and-maintenance
Cool, thanks for the link to Runtime.wxi . That definitely should save lots of
time, effort, and aggravation in figuring all those
properties out.
Regarding "using Custom Actions is an admission of failure" (
http://robmensching.com/blog/posts/2007/8/17/zataoca-custom-actions-are-generally-an-adm
Hi,
You're sure your key and value exist ?
To me -2147287038 means : not exist
Le %:Date:, Sean Farrow a écrit:
> Hi,
> I need to access the hklm key from a per-user install from a registry
> search element
> My property looks like:
>
>
>
>
>
> The log looks a follows:
Hi,
Here is a sample :
Le %:Date:, Jack
What does the verbose log file say is the state for the SC5RegistryKeys
component during uninstall?
On Thu, Mar 7, 2013 at 1:36 AM, Cosmin Petrenciuc <
cosmin.petrenc...@star-storage.ro> wrote:
> Hello,
>
> I have created a setup program using WIX 3.7. I need the setup to create a
> registry key
If you wrote a custom bootstrapper application then it's more a question
for the technology you used to create the UI. You'll be better served
asking on a forum that supports the technology, in your case it sounds like
WPF.
On Thu, Mar 7, 2013 at 2:19 AM, Tomas Köhn wrote:
> Hi
>
> We have creat
Hi:
The key definitely exists on my test system, exporting the key from the
registry editor gives:
[HKEY_LOCAL_MACHINE\SOFTWARE\Freedom Scientific\JAWS\14.0]
The Target value exists underneath.
If I author a custom action, this can open the top level "software\freedom
scientific\jaws" key but car
Gabriel Thanks!
As I said I am just getting into install programming. I usually work on
backend and middle-tier server infrastructure so I know I am asking stupid
questions but where does this go? do I just put it after the
componentgroup or part of it?
also the "vc_red.cab" and "vc_red.msi"...
From the documentation...
RegistrySearch Element (Util Extension)
Attributes
Name
Type
Description
Required
Win64
YesNoType
Instructs the search to look in the 64-bit registry when the value is 'yes'.
When the value is 'no', the search looks in the 32-bit registry. The default
value is '
Hi:
I'm not using th util extension--this is just in msi as tandard!
Cheers
Sean.
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: 08 March 2013 19:15
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] acces hklm from a curre
Then I assume you have Package/@Platform assigned as anything other than x86?
@Win64 on the default RegistrySearch element instructs the search to look in
the 64-bit registry when the value is 'yes'. When the value is 'no', the search
looks in the 32-bit registry. The default value depends on th
The platform attribute is x64.
Cheers
Sean.
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: 08 March 2013 19:40
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] acces hklm from a current user installer
Then I assume you h
Hi guys,
Using Burn aka the bootstrapper is their a way to show the user what
software will be installed?
i.e. create a new page before the Progress page to display what pre
requesites will be installed and what our company software is going to be
installed?
thanks,
Steve
--
View this message
Yes, the "Plan()" action will report back the action states for all
packages to your BA. You'd need a custom BA, the wixstdba doesn't have
anything like that today.
On Fri, Mar 8, 2013 at 12:18 PM, StevenOgilvie wrote:
> Hi guys,
>
> Using Burn aka the bootstrapper is their a way to show the us
Be patient and read wix.chm. Nick's book is also a must have :
http://www.packtpub.com/windows-installer-xml-3-6-developers-guide/book
Also, i remember redist's msi and wix to be problematic. Those msi are bad but
wix don't help either. You need to use exe file.
Jack Sojourn a écrit :
>Gabr
Hi,
As of now I can install same version of Installer of a product twice (I mean
Installer Product Version is same for both MSI packages but content of the
both packages are not same).
1) Can I force the Installer not to install same version if same version is
already installed on the machine an
http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization/checking-for-oldies
Look for "SELFFOUND". I believe that page discusses how to prevent
re-installing the same version.
Alain
-Original Message-
From: chennam [mailto:chatrapathi.chen...@gmail.com]
Sent: March 8, 2013 17:1
Not sure yet how to check if the value is already written in the file. But to
write it, you could use something like:
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-change-xml-element-value-tp7
Yep, after a number of trials and errors, this was bang on. For the record (and
anyone in the future trying to do something
similar), here's the snippet I ended up with:
...
...
Thanks,
Alain
-Original Message-
From: Hoover, Jacob [mailto:jac
22 matches
Mail list logo
