Roberto Almanza wrote:
I tried passing in the INSTALLDIR as a parameter to the call, but it is
being passed in as the empty string.
If INSTALLDIR is coming from the .msi package that consumes the .msm,
it's not going to work: Merge modules are supposed to be self-contained,
so their IDs are
Dmitry Berkovich wrote:
My question is how I can add an additional attributes to File
element?
Take a look at the source code for WixGamingExtension in
src\ext\GamingExtension. It adds custom attributes and elements.
--
sig://boB
http://joyofsetup.com/
John Gilbert (MBS) wrote:
In this instance, the errors relate to a common merge module included in both
a 32bit and 64bit MSI. Everything had been working just fine on 64 bit
machines, (with MSIs built with build 1502), so it appears that I can ignore
this error.
ICE warnings are
Hi Rohit,
I suggest you to print (echo) the values for INSTALLDIR and SOURCEDIR and
try to run the script directly from the command shell, this will give you
exactly the error during the copy operation.
Reasons could be: target folder already exists, it's read only, source not
found, etc...
I just started using WIX build 3.0.2420.0, (I was using
3.0.1502.0). When Light.exe runs it performs the ICE validations.
Some of those, I want to ignore. However, I have not been
able to figure out how to do so.
I tried the following SW command line parms for Light.exe,
but they
Thanks for the suggestion Eitan!
At first I thought it didn't work - but it actually does!
There seems to be a bug in WiX 3 (or Windows Installer). If the new msi has
a different filename than the old one, it fails to find the new package
during the install process. It logs the old filename in
Hi Mattias,
This is a Windows Installer issue. If you are doing a minor upgrade, you
must keep the same msi file name:
See:
http://helpnet.acresso.com/robo/projects/installshield12helplib/MajorMinorSmall.htm
Rgrds,
Eitan
On Tue, Aug 5, 2008 at 11:38 AM, Mattias Åslund [EMAIL PROTECTED]
I could be wrong but without looking at your MSI, here goes.
The strings you're seeing are probably in the Control table; so you might see
something like
{\WixUI_Font_Bigger}this is my text being displayed
If you have something like that, you can remove or replace the
{\WixUI_Font_Bigger} with
No I couldn't be sure but if you look at the dialog in Orca or some sort of
MSIPreviewer get the dialog name, then go to the Control table sort the
Dialog_ column, then look for that Dialog name, all the strings being displayed
in the dialog should be there.
If its not, I'm not sure what else
Try running the script from the command line to debug it:
Dim fso, dest, src
Set fso = CreateObject(Scripting.FileSystemObject)
dest = Session.Property(C:\InstallDir)
src = Session.Property(C:\SourceDir)
fso.CopyFolder src, dest
On Tue, Aug 5, 2008 at 1:06 PM, Rohit Lodha
[EMAIL
Hi,
Is it possible to use property values in the Path attribute for the
DirectorySearch element? E.g.
Property Id='RB3CLIENT' Value='0'
DirectorySearch Id='RBDirectory' Path='[TARGETDIR]'
FileSearch Id='RainbowExe' Name='rainbow.exe'/FileSearch
I think it's the /qb uninstall dialog.
But I didn't define it in my wix file, so I cannot find it in Orca.
Pat Higgins wrote:
No I couldn't be sure but if you look at the dialog in Orca or some sort
of MSIPreviewer get the dialog name, then go to the Control table sort
the Dialog_
Thanks for the reply.
Do you know the control's name?
I searched in orca, but cannot find string anywhere.
Pat Higgins wrote:
I could be wrong but without looking at your MSI, here goes.
The strings you're seeing are probably in the Control table; so you might
see something like
Hi All,
Is there a way from the XmlConfig action to format the XML to put line
breaks after the beginning of XML nodes. I know this sounds
ridiculous but I have a problem with my app.config file which is a bug
in .NET. I am updating the dynamic URL for a few web services I have
in app.config
Eitan Behar wrote:
Hi Rohit,
I suggest you to print (echo) the values for INSTALLDIR and SOURCEDIR and
try to run the script directly from the command shell, this will give you
exactly the error during the copy operation.
Reasons could be: target folder already exists, it's read only, source
Thanks Alex. This is just what I needed.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alexander
Shevchuk
Sent: Monday, August 04, 2008 1:46 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] custom action
See
yixie wrote:
I think it's the /qb uninstall dialog.
But I didn't define it in my wix file, so I cannot find it in Orca.
Basic UI is controlled by MSI, not authored in your dialog. I'm not
aware of any way to control the fonts it uses.
--
sig://boB
http://joyofsetup.com/
Jeff Eldridge wrote:
Is it possible to use property values in the Path attribute for the
DirectorySearch element?
Yes, at least according to the DrLocator Table doc in the MSI SDK. Is it
not working as expected?
--
sig://boB
http://joyofsetup.com/
Hi. I've been diving into the amazing world of wix and I just came to the
point where I could use some help (newbie alert).
We have a setup with two solutions. One that builds merge modules. The other
that picks the previously generated msm:s and creates msi:s.
My problem occurs when I use the
You're probably facing the same issue I did.. There's currently a bug that
binder variables need the fully modularized id in merge modules. I don't
know if there's a way to pass this in to SnapIn extension, but you can try
modularizing the file key yourself as a workaround.
Chris
On Tue, Aug
Thank you. I'm just about to read up on modularization. Do you mean
something like this?:
File Id=MyModule.MyFolder.MyAssembly.dll
On Tue, Aug 5, 2008 at 4:45 PM, Christopher Karper
[EMAIL PROTECTED] wrote:
You're probably facing the same issue I did.. There's currently a bug that
binder
I'm attempting to install a service and receiving the dreaded 1923 error.
Along with the service I'm also creating the user that the service will log
on as in the same install. I then assign the created account and password
to my service.
The confusing part (to me) is that if I run the install
Usually you want to specify domain\account for the Account attribute I
believe.
On Tue, Aug 5, 2008 at 10:56 AM, MarkZune [EMAIL PROTECTED] wrote:
I'm attempting to install a service and receiving the dreaded 1923 error.
Along with the service I'm also creating the user that the service will
No.. That would be normal.
http://sourceforge.net/tracker/index.php?func=detailaid=2034934group_id=105970atid=642714
You need to add the Module GUID to the file ID.
Wix does a lot of nice things for us, including handling the ID redirection
that occurs with modularization. When you refer to
It's amazing how many samples I looked at which didn't have that (or I just
missed). That did the trick. Thanks!
cemiles wrote:
Usually you want to specify domain\account for the Account attribute I
believe.
--
View this message in context:
I try to assign GenericRead in FileSharePermission. Somehow it doesn't work.
It would create the acct over the share only.
However GenericAll works fine. Is it a bug in WIX?
Thanks,
Richard
util:FileShare Id =ShareHitchEXLT Name=HitchEXLT
util:FileSharePermission GenericAll=yes
26 matches
Mail list logo
