They don't handle patching very well either. The Welcome Dialog refers
to a Resumed install when running a patch (MSP) and the Progress Dialog
is devoid of all text except the ActionText. Exit Dialog could probably
do with more specific text to Patching too.
Unfortunately the WiX extensions
bump,
anyone know how adding a bootstrapper could cause comboboxes to freeze on a
custom ui dialog?
cheers,
barry
barry wrote:
Hi,
I am having a strange problem with my installer.
Basically i have an installer for a c# com office addin. It uses a custom
UI that has a combo box on it.
Sorry if this has been asked before, but is there a way not to display
the licence agreement when using WixUI?
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal
views which are not the views of the BBC unless specifically stated.
If you have
I think this is pretty good for a how to by Neil Sleighthom..
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
Med vennlig hilsen /Regards
Brian
2009/4/23 Mike Scott mike.sc...@bbc.co.uk
Sorry if this has been asked before, but is there a way not to display
the
Retrieving msiexec command-line options
Anyone knows how to retrieve the command-line options used to start
installer? I understand how to pass/retrieve properties like
PROPERTY=PropertyValue via command line but I have no idea how to retrieve
options like /quiet /passive etc.
Example:
msiexec
http://msdn.microsoft.com/en-us/library/aa372096.aspx
Palbinder Sandher
Software Deployment IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited.
Perfect. Except of course I'm using WiX 2.
Can anyone point me to a differences between 2 and 3 page?
-Original Message-
From: Brian Bakkebo [mailto:bbakk...@gmail.com]
Sent: 23 April 2009 14:56
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Turn off
thanks, but I specifically need to know when the user supplies the /passive
command-line switch. By default my uninstall is done at UIlevel=3 (or
INSTALLUILEVEL_BASIC) witch is the same as using the /passive switch.
So how can i differentiate between the user doing msiexec /passive /x
*Bump
Sorry for the bump but I'm really interested to know if this is even
possible...
Thank you.
dkijc wrote:
Hi everyone!
I'm trying to to make a dialog with two options (radio buttons):
1. Fetch thumbnails from the WebServer
2. If not, I want the user to specify a directory where
Sorry, Can you not upgrade up to wix 3? I think I read you can do it in
Wix 2.0 but it is more limited I think in what you can do..
Med vennlig hilsen /Regards
Brian
2009/4/23 Mike Scott mike.sc...@bbc.co.uk
Perfect. Except of course I'm using WiX 2.
Can anyone point me to a differences
Here's a snippet of what you want to do:
!-- Embed Version target into the build process --
PropertyGroup
Version;
$(CoreBuildDependsOn)
/PropertyGroup
!--Get Subversion Revision here-you must use MSBUILDCommunityTasks:--
Target Name=Version
SvnVersion
Correction:
PropertyGroup
Version;
$(CoreBuildDependsOn)
/PropertyGroup
Should be:
PropertyGroup
CoreBuildDependsOn
Version;
$(CoreBuildDependsOn)
/CoreBuildDependsOn
/PropertyGroup
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office:
Hello,
Is there any easy way (attribute/property to be set) how to disable
Files In Use dialog which pops up during the uninstallation process. I
simply don't want to bother user with this dialog even if all of
installed executables are running.
Thanks for your help.
Regards,
Jan
Hi Pally,
Thank you so much for your response! That gives me hope haha.
I was actually reading the blog by Neil and had a question.
I understand I can get the directory to be set but that's an installation
directory.
Can I create a custom directory OR can I actually use the INSTALLDIR (or
http://www.installsite.org/pages/en/msifaq/a/1042.htm
-Brian Simoneau
-Original Message-
From: Jan Bilek [mailto:bil...@gmail.com]
Sent: Thursday, April 23, 2009 2:58 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to disable/bypass FilesInUse dialog
Hello,
Is there
Hi,
In 3.0.4923, I used to get the following output (note how the Interface
element is *outside* of the File element):
Component Id=DisplayFridayListUI.dll
Guid={C4773BDF-6383-423D-BB34-BBB961BFD6DF}
File Id=DisplayFridayListUI.dll
Name=DisplayFridayListUI.dll
I have two publisher policy assemblies (i.e. lets say one for version 8.6 and
one for version 8.7). Both policy assemblies use the same config file. In
order to successfully install these publisher policy files, MSI/fusion
requires that the policy assembly and the config policy file are in the
Roy,
One question on this however. From the code you sent the Interface /
element is actually under the TypeLib / which is legal. Are you sure that
it is that actual line and not some where else?
Thanks,
Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com
On Thu,
Hi Brian,
The bug is:
https://sourceforge.net/tracker/?func=detailaid=2779893group_id=105970atid=642714
I've attached a DLL you can use to test with in case you don't have one to
reproduce the issue.
Thanks!
Roy
Brian Rogers wrote:
Hey Roy,
Please file a bug.
Thanks,
Brian
Roy
The interface element is inside the TypeLib element, I have just
checked my code and this is valid and has been the same for a while, so
the error doesn't really make sense. When you raise a bug is it possible
to include the DLL you are scanning?
Neil
-Original Message-
From: Brian
Running heat and candle against the file you attached to the bug doesn't
generate the error you reported could you give more details of the
command lines you are using?
Neil
-Original Message-
From: Roy Abou Assaly [mailto:royass...@gmail.com]
Sent: 23 April 2009 22:18
To:
Both of you are correct. I have an XSLT that massage the XML that heat
generates in order to ensure certain shortcuts are added and changes a few
other things as well. In the process, the XSLT is not doing its job. I
would cancel the bug as it looks like like it's a data issue on my end.
Hi All,
I run into a stange problem. Forgive me if this question is a bit of long. I
try to make it shorter.
I need your hlep.
We're using WiX version 3.0.4805.0.
The problem is:
---
I have 3 builds. They have exactly the same feature set. They are just built at
different time.
Still kind of stuck. I was able to generate the exact xml as Brian did.
Candle compiled fine, but light is complaining. I'm trying to generate a
merge module out of it. Getting this error:
[exec] D:\Builds\PRISM XP\Build 11.51.\Bin\PrismShell.wxs(18) :
error LGHT0130 : The primary
Sorry, I forgot to attach the screen shot of the testing matrix.
Here it is in the attachment. Hopefully you can see it.
Thanks you all.
/Brian
__
Be smarter than spam. See how smart SpamGuard is at giving junk email the
Oh, and one more:
00020420---C000-0046
After that, I was able to build my merge module and link them and create my
MSI which contains 129 vb6 com DLLs and various OCXs. Again, my experience
in this area is weak, but the product seems to install and uninstall without
issues even
I tried looking through the digests on sourceforge but couldn't find a way to
search, and didn't see this question answered so I apologize if it's a
duplicate.
I am trying to create patches for a product that will each be all encompassing
of the previous ones, and want anybody at any version
27 matches
Mail list logo
