did u try: msiexec /i "setupfile.msi" /qn REINSTALL=ALL REINSTALLMODE=vomus
?
On Tue, Oct 7, 2008 at 5:02 AM, Sandeep Gautam (HCL Technologies Ltd) <
[EMAIL PROTECTED]> wrote:
> Hi ,
>
> How can I do silent repair. I am running msiexec with option /f nothing is
> happening.No Custom action is n
I am also having the same issue, can any body please tell us how to
implement repair without UI.
Regards,
Raj
On Tue, Oct 7, 2008 at 8:32 AM, Sandeep Gautam (HCL Technologies Ltd) <
[EMAIL PROTECTED]> wrote:
> Hi ,
>
> How can I do silent repair. I am running msiexec with option /f nothing is
Arun Kumar A V wrote:
> How can I avoid Substituded drives (Subst DOS Command) from showing up in
> Volume Select combo?
The MSI UI doesn't offer that option.
--
sig://boB
http://joyofsetup.com/
-
This SF.Net email is
Robert O'Brien wrote:
> Any insights on how I might still use a $(var.Platform) derived value for the
> Win64 attribute and also suppress the generic warning generated by every
> instance where I do this so that my project build doesn't break building when
> the treat warnings as errors quality
Mattias Åslund wrote:
> The Browse Dialog (http://msdn.microsoft.com/en-us/library/aa367836.aspx)
> only seems to let the user browse local drives, not the network and its
> shares (as with network neighborhood) . Does anyone have an idea on how to
> do this?
>
MSI UI doesn't support it. You'd
If anyone has the code for detecting whether visio 2007 is installed or not
in the system using wix, plz reply me.
Any help appreciated.
Thanks
Anuj
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Hi Rob,
I guess I am not clear on something.
I created my .msi file by setting the property "showRequirementsDlg" to 0, so
installer does not check IIS and others. Once I get to the last dialog and
click install, the installer goes thru installation but aborts with an error on
server with
How can I avoid Substituded drives (Subst DOS Command) from showing up in
Volume Select combo? The installation fails on substitued drives with an
Invalid File Path error, so I am hoping atleast I could fix UI from showing
Subst drives in the volume select dropdown. I have Remote=no and Remova
Hi Robert,
In my wxs for IIS components I have all those elements separate such
that I can choose based on the user selections what components to
install. Note that if the condition for the
CreateWebsiteWithPortAnonymous component are met, then the
WebApplication is the MainWebApplication (at the
what is the recommended way for setting the AppPool associated with a new
iis:WebSite? Lots of samples on this for the case of an iis:WebVirtualDir but
nothing that made sense in the case of an iis:WebSite where creating a child
iis:WebApplication doesn't make sense given that's typically a vd
The documentation is wrong. PUT-GUID-HERE will fail with a friendly error
message saying something to the affect, "Silly, you must actually put a GUID
here." Please do file a doc bug if you think the documentation is wrong or
misleading.
-Original Message-
From: Robert O'Brien [mail
the "How To: Generate a GUID" document (excerpt below) suggests that wix
supports compiling with PUT-GUID-HERE tokens vs actual Guid values or where
allowed "*" token autogenerated Guid values defined...but the PUT-GUID-HERE
tokens case isn't working with the latest install
"All examples in the
First because, I am beginner with WIX. But I did try going that way. I have
about 50-60 COM DLL and one EXE.
So, this is what I have done so far:
1. Use RegSpy2 tool to gather registry information from the COM, and then saved
it in foo.reg file.
2. Passed foo.reg file through tallow to get
Background
--
A while ago I raised an issue to do with a warning being generated when using a
variable for the Component Win64 attribute value. Below you'll see the an
excerpt of the logic I'm using so that in the case of all managed code
deliverables I can create one set of wix so
By using heat, you can harvest the COM information from the file and add
that to your wix file. This works very well and also get removed correctly
when the product is uninstalled. Beats having to write custom actions for
install & uninstall.
-Original Message-
From: Jim Williams [mailto:[
Yes, as Robert suggested, you could register the COM stuff using the
element.
Jim Williams
-Original Message-
From: Kapoor, Anupama [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2008 10:38 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] invoking batch file insid
Uhh, why don't you just author the registry keys in the .wxs file? A batch
file won't rollback correctly.
-Original Message-
From: Kapoor, Anupama [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2008 10:38
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] invoking batch
Hi Jim,
I have already tried "deferred" but even that seems to fail. This batch file
basically tries to register the COM components on the target machine.
So, I want the batch file to run after the installer script has run, i.e after
creating the installer, this script has to run to register t
Nope, no one has added that functionality to smoke or some other similar tool.
Sounds kinda' interesting though.
-Original Message-
From: Jon Seanor [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2008 10:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [Wi
I'm looking for something that detects violations of the
feature/component authoring rules (i.e changes that that will break
minor upgrade).
InstallShield has a tool which you pass the path to the build output +
the paths to one or more previous releases.
Their tool compares the build output a
Thanks. Wix.chm | search "global assembly cache" -> returned one hit for "File
Element" documentation which did detail use of the Assembly attribute for
install/remove of managed dlls in %systemroot%\assembly\gac_msil. So the
addition of just Assembly and KeyPath to File element as shown here
You might want to try deferred execution instead of immediate. This will run
the custom action after InstallFinalize when the install script is run.
Immediate causes it to be run when it is encountered when creating the
installation script.
Jim Williams
-Original Message-
From: Ka
Hi,
I am trying to invoke a batch file from my
foo.wxs, which I want it to "run" after my installer has been
installed. So, I am doing something like this:
I am running into issues with this. Can you please let me know what is
incorrect here?
Thanks much,
Anu
---
Been a while since I used the old way. I'll give it a try and get back to you
all. But my suspicion is that you will have to expose the preprocessor in some
way.
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2008 8:03 AM
To: General discus
In article <[EMAIL PROTECTED]>,
Mukesh Agrawal <[EMAIL PROTECTED]> writes:
> I am using Wix V2. Is there a way I can disable a Next Button on the
> Feature-Sel
ection Dialog if no features are selected at all.
> Currently, I am throwing a warning message after the NEXT button is pressed
>
Yeah, you have to search for "global assembly cache" in the WiX.chm to find it.
"GAC" only finds the NativeImage element. Probably should tweak the
documentation to catch both.
-Original Message-
From: Robert O'Brien [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2008 03:58
To:
I'll update the bug report to include this.
Neil
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 18 November 2008 16:02
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation
That's the bug. I bet this is a regress
I'm not aware of a work around. How would you do this with XslPattern using
MSXML 3?
-Original Message-
From: Scott Sharpe [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2008 17:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XmlFile does not s
What validation are you expecting in particular?
-Original Message-
From: Jon Seanor [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2008 17:35
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Wix 3 minor upgrade validation tool?
Hi
Is there a WIX tool
That's the bug. I bet this is a regression from trying to get all those other
.wxl bugs fixed in .wixlibs that we addressed a couple months ago.
-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2008 23:36
To: General discussion for Windows
A verbose log file will show you all the actions and why they were/were not
executed.
-Original Message-
From: Mazin Sayid Ali [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2008 07:43
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Full UI while uninstalling from Add/Remo
Get a verbose log file and take a look at the properties. They will explain
why your condition is firing/not firing.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2008 05:38
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Proper
Encapsulating the expression in CDATA as you suggested worked perfectly.
Thanks,
-Jonathan
-Original Message-
From: Pally Sandher [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2008 9:37 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Properly
Hi
I'm new to WIX. I'm using 3 immediate Custom actions which run after
IntallFinallize. Unfortunately only one custom action gets called when
removed from add/remove but it works fine when removing directly using the
MSI
Thanks in advance
Mazin
---
I use:
Which works fine for us as far as I know.
Try using the CDATA tag for the condition & get the user to test it
again.
Also if you only want it to install on the 32-bit versions XP & Vista,
you should modify your condition to something like
The brackets may not be strictly necessary
> Take a look here:
> http://neilsleightholm.blogspot.com/2008/10/how-to-create-wix-build-mach
> ine.html this should document what you need to know to build WiX.
>
> Also, you don't actually need to rebuild WiX to do what you want to do,
> I have outlined the process here:
> http://neilsleightholm
The software I develop has an installation requirement of running only
on Windows 2000, XP, and Vista. To enforce this requirement, I have a
Condition clause on the Product element of my top-level WiX file like
so:
VersionNT >= 500
This appears to work correctly on my Windows 2000 deve
I looked under the current wix help file how to section and could only find
"How To: NGen Managed Assemblies During Installation".
This appears to cover having wix generated msi's install/uninstall to
%systemroot%\assembly\gac_32 & %systemroot%\assembly\gac_64 but does not appear
to have an opt
http://msdn.microsoft.com/en-us/library/aa367559.aspx
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151
You can have as many QtExec Properties as you like. All you need to do
is create a Property with your command in the Value which is named the
same as the Id of the QtExec CustomAction as is described in the "Quiet
Execution Custom Action" page in the WiX documentation (it's under
"Standard Custom A
Not directly, but if you use v2 tallow to generate the wxs you can then
use v3 wixcop to update it.
Neil
-Original Message-
From: Yu, Brian [mailto:[EMAIL PROTECTED]
Sent: 18 November 2008 09:45
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] how to convert
Bit of google and found the following
wix 2.0 -> Tallow.exe -reg reg_file.reg
Is there a way for wix 3 to do the same?
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg17985.htm
l
Brian Yu
EasyScreen
155 Bishopsgate
London
EC2M 3TQ
0207 650 4410
---
Take a look here:
http://neilsleightholm.blogspot.com/2008/10/how-to-create-wix-build-mach
ine.html this should document what you need to know to build WiX.
Also, you don't actually need to rebuild WiX to do what you want to do,
I have outlined the process here:
http://neilsleightholm.blogspot.com
Hello all,
Because I wanted to remove the license agreement dialog from the Wix_Mondo
UI, I'm trying to build the WiX sources from scratch (to create a new
WixUIExtension.dll). However, I'm running into problems.
When building I run into the following error messages (core.inc):
[exec]
C:\
Hi
I am using Wix V2. Is there a way I can disable a Next Button on the
Feature-Selection Dialog if no features are selected at all.
Currently, I am throwing a warning message after the NEXT button is pressed to
handle this scenario.
Thanks and Regards
Mukesh Agrawal
---
45 matches
Mail list logo
