Hi,
I have a wixproj which specifies Culturesen-us;es-es/Cultures. As you
know, compiling this wixproj will create two MSIs located in en-us folder and
es-es folder respectively.
My installer installs a UI product and need to place the corresponding resource
file to the installation folder.
I think you could simply don't user the ExitDlg.
Well, cancellation might fail, although it shouldn't, ExitDlg is just a
screen informing user the result of the cancellation.
You could define a property, that bypass ExitDlg when nothing wrong
happened.
On Fri, Jul 3, 2009 at 1:10 AM, Quinton
Another way is to use the standard utility msidb.exe from Windows
Platform SDK.
Msidb.exe -d your_MSI_package.msi -r your_transform.mst
Hope this helps.
-- Yan
-Original Message-
From: Alex Shevchuk [mailto:shevc...@live.com]
Sent: Thursday, July 02, 2009 6:51 PM
To: 'General
I don't really sure why we use system temp, but I think it is because
application for which I am writing installer was written a long time ago, when
everyone was using system temp by default. Currently application is migrating
to C#, but still some parts will be remained untouched and nobody
Hmm, that's mysterious. We've heard of issues with mergemod.dll and some
MSMs. Can you get a debugger attached and get a callstack? That would
greatly help narrow the set of things that might be causing this.
Fredrik Kauma wrote:
Hi all!
I am unable to create an installer that installs the
Shortcut/@Target is a Formatted target so you can put a Property
reference in there that resolves to the file you want. Arguments go in
Shortcut/@Arguments (I think, the WiX.chm will know for sure).
Abdullah Ahmed wrote:
Hey Guys,
I've been tasked with creating some shortcuts to the desktop
They will also never get uninstalled.
Tony Juricic wrote:
One thing that you may try is the following:
1) put all the files that may get deleted inside their own component
2) Do not set any Guid for that component
Windows Installer will ignore these files when it comes to patching so you
Sounds like a bug. WiX v3.5 is under development right now and Votive is
not necessarily stable.
John H. Bergman (XPedient Technologies) wrote:
I just installed WiX 3.5.0626 and do not have the WiX project types with
Visual Studio now. Does anyone know what happened? The 3.5.0605 has them
That error message is about the IIS Metabase, not the file system.
Probably not related.
Jirong Hu wrote:
Hi
I have a folder under C:\inetpub\wwwroot\SFS with some subfolders are not
removed SOMETIMES after uninstall. The behavior is it gets removed in the
first or two fresh
DocCompiler. Code is checked in.
zett42 wrote:
I assume you have some nifty tool to do this?
I like the style of the CHM documentation very much, so I would like to
create my own CHMs from XSDs in this way...
Thanks
--
View this message in context:
Its a warning telling you that multiple Merge Modules have had the
action that correctly CommonFilesFolder in the Merge Modules scheduled
at the same number. This is caused by a stupidity in mergemod.dll.
Have you considered .wixlibs instead of Merge Modules?
John Aldridge wrote:
I have a
This was asked pretty recently.
You don't.
zhihai guo wrote:
Hi
Can I control the UI when uninstall in the xml?
Thank you.
--
___
WiX-users mailing list
and accessibility is hosed.
Neil Sleightholm wrote:
There is a workaround for this. Create a custom exit dialog and make the
checkbox only the size of the tick, then put a label next to it. It
works but means that the user needs to click the check area only, the
label part doesn't work.
Hi wix-users,
I tried to create my own dialog. I did it as the Wix Tutorial Part 8
says. But when I build it. There are several errors, saying some dialogs
missing. I copied the necessary dialog files to my project, like
ExitDialog.wxs, FilesInUse.wxs, and cleaned some build errors. At last,
I
Hello,
I am wondering if it is possible to execute an MSI within the MSI that I create
using Wix.
I need to do it because a provider delivers me an MSI to install part of a
solution and I need to bundle everything within an MSI.
Thanks,
David
Rob Mensching wrote:
Its a warning telling you that multiple Merge Modules have had the
action that correctly CommonFilesFolder in the Merge Modules scheduled
at the same number. This is caused by a stupidity in mergemod.dll.
Sorry, I don't understand this: there's only one merge module
As far as I know, we cannot call an MSI inside an other MSI.
Anyone Correct me if I'm wrong.
What we can do is generate wxs from the msi(reverse engineering), which we need
inside our msi.
Then generate an MSI including those wxs.
Thanks Regards,
Srivardhan.
-Original Message-
From:
I searched in the maillist archive and found some one had the similar question
some time ago. The advice was to add mergemode.cub and mergemod.dll.
When I search in C:\Program Files\Windows Installer XML v3\bin\ , I found these
two files are already there. I don't need to add them again.
Could
This is my code,
DirectoryRef Id=Installdir
Component Id=EnvironmentVariables Guid=
{2A40FB98-59EC-4b87-97F2-B36856A98FA2} Win64=yes KeyPath=yes
Environment Id='test' Name='test' Action='set' Part='all' Value='
[INSTALLDIR]' System='yes' Permanent='no'/
/Component
/DirectoryRef
Due to some
Hello all,
I need to run bcp.exe (Bulk Copy Program) in my installation and I have to
pass parameter to it - the path to the sql script to run. This script is not
on the local machine, it is in my package. So, I gather, I have to copy this
script to the hard drive somehow, maybe - to the Temp
Is it possible to catch click events on labels on a custom dialog?
If so, would it be possible to bind a click event on the label that puts
focus on the checkbox and checks/unchecks it?
Or is that too advanced for MSI?
Thomas
-Original Message-
From: Rob Mensching
The files are present on the machine after the InstallFiles action in
the InstallExecute sequence, but youll have to make your bcp custom
action deferred.
-Original Message-
From: Natalia [mailto:natalia.gladk...@arcadia.spb.ru]
Sent: 03 July 2009 10:47
To:
Hi,
it is definitely not possible to call another MSI when an installation
process is already running. Windows Installer takes care of that.
You can either reverse engineer the MSI as already suggested, which I
would not do - you have to do so every time you get a new MSI from
your provider.
I
Sunkesula, Srivardhan wrote:
As far as I know, we cannot call an MSI inside an other MSI.
Anyone Correct me if I'm wrong.
You can, but not in a very nice way. You can run pretty much anything as an
arbitrary custom
action. I think there was a custom action for running another MSI file, but
Srivardhan is correct, chaining MSI's isn't supported by Windows Installer (as
far as I know but my knowledge is limited to v3.1 since it's the only version
widely supported from XP onwards. v4.5 or v5 may have different functionality
but until they're provided for Windows XP through automatic
Or you could check with your provider to see if he can deliver a merge module
instead?
Thomas
-Original Message-
From: Dirk Räder [mailto:d...@raeder.cc]
Sent: 3. juli 2009 12:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Execute an MSI within
Quinton I also reported the same issue in the WiX bug tracker on
Sourceforge on issue 2025677 a while ago was told the same thing as
you can see from the notes on it.
As I wrote on that issue, the workaround Neil outlined below is what
I've implemented and if it works for companies like Perforce
Well, under MSI evaluation logic, if you just use MYFLAG as your
condition, that will evaluate to true as long as MYFLAG has any value
at all. If you wanted to support MYFLAG=false on the command line and
have the condition evaluate to false, then you would need to check
MYFLAG against a value
Hello,
I experience some strange behaviour when using the MFC 9 SP1 merge module in my
setup.
The msm itself has about 4 MB, but when including it in an msi its size
increases by about 12 MB, nearly doubling the size of my setup.
It seems like the MFC dlls are packaged multiple times under
Hi Wix-users,
The full error message is:
D:\Documents and Settings\aa028704\Local
Settings\Temp\5zuz0mdr\VP6Wix.msi(0,0): error LGHT0204: ICE31: ICE Internal
Error 4. API Returned: 6.
I searched the path D:\Documents and Settings\aa028704\Local
Settings\Temp\5zuz0mdr\VP6Wix.msi. But there is
That's strange. The smart-cabbing feature in WiX should reduce the size
of your cabs rather than increase them.
I've just checked a small plug-in installer of ours which puts the same
12 files (3 DLL's. 1 .BMP, 8 .GIF;s) in 2 different locations based on
feature conditions. The cab has 2 copies
I found that every time when I do the rebuild of the project, there will be a
new folder name in the error message under \Temp\. And the new folder doesn't
exist at all.
I don't know if it is the reason caused the error. But why Light.exe will
create a new folder under \Temp\ every time of
Eric Napier wrote:
I need to install and invoke an executable file. I also need to specify the
file name at installation time (some of the arguments are taken from the
file name).
There's no support in MSI for that.
--
sig://boB
http://joyofsetup.com/
Quinton Tormanen wrote:
(1) How can I get the installer to exit immediately after the user
answers Yes to the confirmation.
Don't reference the UserExit dialog; it self-schedules to be shown after
cancellation.
(2) Is there a good reason why I should keep the final cancellation
screen?
Sebastian Brand (Instyler Software) wrote:
I got it working. I compiled winterop.dll as 64-bit.
Note that extensions also run in the light.exe process and might expect
to always be running in a 32-bit process.
--
sig://boB
http://joyofsetup.com/
jnewton wrote:
Yeah, I meant to put 'yes' or 'no' in the post, but it doesn't matter. The
wix compiler always says the value is invalid according to its datatype.
What's the actual error message? Is it coming from the compiler or
Visual Studio?
--
sig://boB
http://joyofsetup.com/
kezhong zhou wrote:
The origin calculation is not accurate. Such as an installation of 100M, the
actual space taken would be 100.4M. So, I want to tell the user, if he just
have merely enough space to pass DiskSpaceCheck step, that he would fail.
The simplest way to do this, seems to be use
Lian Jiang wrote:
This is obvious a bad solution since it packs all locales resources for any
locale's MSI. I would like pack only the corresponding locale resource for
one MSI. But how can I dynamically get the current locale that the MSI is
built? Is there any global variable exposing
It's a temporary directory created by light during run time for processing
files. It is deleted when light finishes its current process.
Set the environment variable WIX_TEMP to specify your own directory but it has
nothing to do with your ICE error.
Have you searched MSDN for ICE31? I get the
Quinton Tormanen wrote:
I am using WiX 3.0.5217.0 with WixUI_InstallDir. If I put the installer
in maintenance mode and click the Remove option, then on the verify page
(Ready to remove RMCTools 3.33.0d), the Remove button is missing the
elevation shield.
Assuming the right button is being
Quinton Tormanen wrote:
my existing project, I see duplicates of every dialog form, one for the
Admin sequence and one for the standard sequence. For example,
UserExitForm and AdminUserExitForm, WelcomeForm and AdminWelcomeForm.
They didn't come from WixUI: It's never supported admin-UI
I can't see the files on the disk after InstallFiles... (I've put custom
action displaying message box just after InstallFiles)
Installation fails with the message
Error 1721. There is a problem with this Windows Installer package. A
program required for this install to complete could not be
Bob Arnson wrote:
Quinton Tormanen wrote:
I am using WiX 3.0.5217.0 with WixUI_InstallDir. If I put the
installer
in maintenance mode and click the Remove option, then on the verify
page
(Ready to remove RMCTools 3.33.0d), the Remove button is missing the
elevation shield.
Assuming
Hi Pally,
Thank you for your nice suggestion. I read the link as you suggested. It sounds
that ICE31 is related to TextStyle setting. I thought probably the error is
caused by:
Property Id=DefaultUIFontDlgFont8/Property
When I defined the DlgFont8 before I called it in Property, the error is
Hi,
I have a wixproj which specifies Culturesen-us;es-es/Cultures. As you
know, compiling this wixproj will create two MSIs located in en-us folder and
es-es folder respectively.
My installer installs a UI product and need to place the corresponding resource
file to the installation folder.
Here are a few suggestions that might help:
That error could mean that the program starts but is returning a
non-zero error. Change Return=check to Return=ignore to test this.
You need to specify the full path to the program to run and put it in
quotes. The Directory attribute just specifies
Hello,
Does anyone know of a way to create an installation using WiX where the
user can specify a particular instance for the installation and for this
to be controlled at the WiX level rather than delving down into the
murky depths of MSI?
In other words supposing we have an installer
No it isn't 'cos I missed a bit! You still set the text of the checkbox
to the same value as the label the Alt-key access then still works.
Tabbing to it still works as well.
Neil
-Original Message-
From: Rob Mensching [mailto:r...@wixtoolset.org]
Sent: 03 July 2009 09:01
To: General
Alex,
Excellent suggestion. I've implemented the suggestion (see below). Is
this essentially deferring an install action until the moment that the
uninstall starts? The CustomAction events fire correctly (caInstall on
install, and caUninstall on uninstall) and the command line options
are
hi all,
using wix 3.0.5217.0
i am trying to build a 64 bit version of my installer but i am running into
problems. been looking into this for the better half of the week and am
stuck stuck stuck!
So my installer is pretty simple - dumps a few files and installs a legacy
complus application. As
Personally I would like to see this as the default, the current
implementation look rubbish.
Neil
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 03 July 2009 11:43
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Option
Its not a bug in WiX. Its the way Windows Installer works. If you
want that level of control over the UI, that's why they provide the
CustomUI option. You either live with the restrictions of the UI
model provided by Windows Installer, or you do a custom UI.
--
The Direct3D Graphics Pipeline
Bob Arnson wrote:
Assuming the right button is being shown, MSI can still not show the
shield, if the user running the uninstall already has elevated
privileges.
As you suggest, Bob, I found that the right button is being shown, but
MSI isn't showing the shield. It appears to be because
53 matches
Mail list logo
