Bob,
I would prefer to use WixVariables in my source, and that's exactly what I
tried first.
I think there's some reason the UI extension wasn't seeing them. Are
there some special rules about relative paths for these variables vs. the
.wxs or the 'working directory' of the call to Light?
fyi - msi minor upgrade detection using QFEUpgrade=1 property setting condition
is no longer working for me, i.e. qfeupgrade property no longer being generated
during msi minor upgrade processing. Not yet sure what changes to my wix
sources have broke that option or how I was testing to cause
So it would seem that setting REINSTALL and REINSTALLMODE automatically within
wix works for msp small update or minor upgrade processing but not an option,
as suggested by others earlier, for msi minor upgrade processing.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
Hi, Bob.
Adding Not Installed in the condition would make the difference, because
Installed is the Installation Status Property, take a look at
http://msdn.microsoft.com/en-us/library/aa369297(VS.85).aspx.
Regards,
Denis Zavorotnyuk.
-Исходное сообщение-
От: [EMAIL PROTECTED]
Is there any way i can control the way dialogs are positioned on the screen?
-
Andy
MSI Developer
Schneider Electric:working:
--
View this message in context:
http://n2.nabble.com/WiX-UI---Spawn-dialog-position-tp1097922p1097922.html
Sent from the wix-users mailing list archive at
Hi,
Our package creates a database during installation and we only want to drop
the database during uninstall when the PROPERTIES DROPDB=1.
What i did was i've created a component:
Component Id=createDB Guid=8D0757C0-B204-4A99-8FA1-4F3235FA2CAF
CreateFolder Directory=INSTALLDIR /
This may get you going in the right direction.
http://www.microsoft.com/technet/scriptcenter/scripts/apps/user/usapvb02.msp
x?mfr=true
to install on a remote machine it's all about how you execute the msi file,
there's not much you can do once the msi has started to be processed by the
installer
Hi Denis,
thanks now i got , so adding Not Installed will make this action to trigger
only If this feature i not installed, if this feature is already installed then
it will not trigger. It makes sense now . thanks again
Thanks and RegardsBOB
From: [EMAIL PROTECTED] To:
I've got an issue where the installer gives an error when I refer to an ID for a file that wasn't
installed, even though it actually is.
I have a file called dbsview.exe, and the file ID is the same. I'm trying to launch it at the end
with a Custom Action using the file ID. When I do this I
It appears my attachment has been stripped. I've uploaded it here:
https://www.snsys.com/res/store/log.zip
Thanks for any help,
Rob
Rob Hamflett wrote:
I've got an issue where the installer gives an error when I refer to an
ID for a file that wasn't installed, even though it actually is.
Hi, Rob.
Can you show your wxs-file in which you describe your custom actions?
Btw, in your installation log-file there isn't a custom action which must
launch your dbsview.exe after installation.
С уважением,
Заворотнюк Денис.
-Исходное сообщение-
От: [EMAIL PROTECTED]
I wonder if the period is messing it up. I've run into some problems when my
File Id had a period in it. Can't remember the details, but something makes me
ALWAYS remove periods from my File Ids these days.
Might be worth a try to use
File Id=dbsviewexe
And then change any references to
Found out:
CustomAction Id='aspnetregiisi'
ExeCommand='[DOTNET20INSTALLDIR]\aspnet_regiis.exe
-i -enable' Directory='TARGETDIR'/
CustomAction Id='aspnetregiisga'
ExeCommand='[DOTNET20INSTALLDIR]\aspnet_regiis.exe
-ga [DOMAIN]\[LOGIN]' Directory='TARGETDIR'/
Directory attribute would be
Hello All,
Can Finish button on the Exit dialog trigger more than one action, such
as Install a 3rd party application and Launch my own application? My
application can be launched on the Exit dialog after I added into a
checkbox and a custom action, I am just following the same way to add in
I added feature request 2118214 to deal with this limitation.
Rob Mensching-2 wrote:
That scenario is not supported by the shortcut versions of
SetProperty/SetDirectory. You can open a feature request but right now
the behavior is known and by design (limitation).
-Original
In article [EMAIL PROTECTED],
Andy2k8 [EMAIL PROTECTED] writes:
Is there any way i can control the way dialogs are positioned on the screen?
Take a look at the HCentering and VCentering columns in the Dialog
table.
These are exposed as the X and Y attributes of the Dialog element in
WiX.
Here is my code. Currently I can launch my own application, but cannot
get the 2nd checkbox showing up. Seems like
WIXUI_EXITDIALOGOPTIONALCHECKBOX and
WIXUI_EXITDIALOGOPTIONALCHECKBOXTEXT are the required property value to
define the checkbox, i.e., they cannot be modified, so I guess my
problem
Hi,
Is there a way to specify in WIX that a group should be
created? I see that in the User element you can specify true for the
CreateUser attribute and the user will be created. However the group
element seems to not allow this as the reference says Groups cannot
be created by this element.
Thanks again Chad for your response.
I found a work around that problem. Now insted of doing every thing in one
go. We will run msiexec command twice
for the first time i will run it with the flag which will normally install
every thing and than execute that batch file and clean up every thing
Hello,
I am getting these error messages when building my installer due to
having a non-advertised shortcut:
error LGHT0204 : ICE43: Component Exe has non-advertised shortcuts. It
should use a registry key under HKCU as its KeyPath, not a file.
error LGHT0204 : ICE57: Component 'Exe' has
Look in the Wix.CHM file for the How To topic on how to create shortcuts to
applications. It shows you the steps to take to author the setup correctly to
remove these errors.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roger Yen
Sent:
Hello,
Thanks for the reply, I guess I saw this solution before as I tried
googling my problem a while ago.
I don't really like the idea of installing irrelevant registry keys(in
HKCU) unless it is really necessary, so if I leave my installer as it
was without the HKCU registry, what might be
I'll leave the answer to that up to others more knowledgeable about those
specific ICE errors. The steps listed in the How to document, however, are the
recommended way of doing this.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roger Yen
Sent:
I am trying to test patch creation with WiX. I ran through the patch
creation Using Purely WiX in wix.chm, and it worked fine. In that
scenario, a single text file, Sample.txt is installed with the 1.0
installer. In the 1.1 patch, a modified version of Sample.txt replaces
the old 1.0 version.
With Wix 2.0, I used this:
IgnoreModularization Name=OurDirectory Type=Directory/
With Wix 3.0.4429.0, I see this warning:
My.wxs(62) : warning CNDL1085 : The IgnoreModularization element has been
deprecated. Use the Binary/@SuppressModularization,
CustomAction/@SuppressModularization, or
I've been going through the forums to see if I can find if this has been
covered already but I can't seem to find one. The problem I'm having with
my install is when I uninstall the program it leaves the service behind and
the exe related to it in the install folder. I'm using the following WiX
You could have the uninstall generate a verbose log and see what it says
about this Component. Might give a hint. With some minor exceptions,
overall your code looks much like what I use for dozens of services and
they always uninstall correctly.
-Original Message-
From: [EMAIL
Kelly Leahy wrote:
I would prefer to use WixVariables in my source, and that's exactly what I
tried first.
I think there's some reason the UI extension wasn't seeing them. Are
there some special rules about relative paths for these variables vs. the
.wxs or the 'working directory' of the
Bryan Turner wrote:
With Wix 2.0, I used this:
IgnoreModularization Name=OurDirectory Type=Directory/
With Wix 3.0.4429.0, I see this warning:
My.wxs(62) : warning CNDL1085 : The IgnoreModularization element has been
deprecated. Use the Binary/@SuppressModularization,
Lucas Theisen wrote:
Is there a way to specify in WIX that a group should be
created?
Not currently supported.
--
sig://boB
http://joyofsetup.com/
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
Hi all,
I am a new user to Wix. I am using Visual Studio 2005 for development. I just
installed Wix-3.0.4318.0.
When I tried to follow the help adding reference from .NET project, it works
fine.
Then I tried to add my real projects (using Win32) references. There is
exclamation icon at new
31 matches
Mail list logo
