Hello,
I am creating patches for my application using the WIX patch build system. I
have encountered (so far) 2 (two) big problems related to 'wix.section.xx'
in the Wix pdbs.
First problem was that my patch included many components which I have not
specified in my Patch.wxs file. Debugging pyro I
各位老总：您们好！
诚祝：您们在2008年里；有鼠不尽的快乐！鼠不尽的收获！鼠不尽的钞票！
鼠不尽的幸福！鼠不尽的美满生活！愿：您们阖家欢乐！幸福安康！
我是（深圳市珊湖岛进出口有限公司）的负责人；可以提供：出口报关单，
核销单等等一系列手续；代理：出口报关，商检，境内外运输..等等；还可
以代办
I use the following Quiet execution CA to run an EXE during install
NOT
Installed
NOT Installed
Installer fails with the following error in the verbose log:
CAQuietExec: Command string must begin with quoted application name.
MSI (s) (30!FC) [15:03:41:856]: Closin
Thanks for the help
Donal
--
View this message in context:
http://www.nabble.com/product-search-using-product-code--tp16306215p16395618.html
Sent from the wix-users mailing list archive at Nabble.com.
-
Check out the ne
obsessed about coming
Unbelievable 1-3 full inches gained in less than 2 months.
http://www.cimpoteo.com/
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything O
Hi,
I'm using wix-2.0.5805.0 to generate an installer for an application
which uses the DirectX. So far, I have successfully embedded the DX9
Redist files and they do get installed, however, I need to run the
dsetup.exe binary at the end of the installation. I've tried various
calls, ending up
8 (9OЗ) 7 O 7 9 2 9З
[EMAIL PROTECTED] ПРЕДЛОЖЕНИЕ
реклама по юридическим и физическим адресам Москвы
4,63 миллиона писем
или
реклама по юридическим адресам Москвы и России
3,95 миллиона писем
ВСЕГО 3999 РУБ.*
две рассылки
ВСЕГО 5500 РУБ.*
три рассылки
ВСЕГО 6999 РУБ.*
при оплате яндекс
I am a new to Wix and am having trouble with two basic things.
One: I'd like to change the default install directory from C:\ to something
else.
Two: The Merge Module which I include puts files in module retargetable folder
(subfolder) of the directory I specify.
I am using WixUI_InstallDir as
I know this should not be a complicated problem but i am not proficient in
Conditions settting.
The following is myThings:
Not REMOVE="ALL"
The result is myAction can run well in Setup and Repair, but meet an "end up
prematually" problem in Remove. In fact, i don't want myAction run in Rem
I briefly searched the archive for an appropriate post and nothing I found
was quite right, but I apologize if this issue has been previously discussed
here.
Using WiX v3 (candle.exe version number is 3.0.2925.0).
I have a WiX installer project that builds a MSI file for an IE toolbar/bho
exten
Hi,
I am trying to create a shortcut to a file in another merge module. I
have tried the following:
However I get the following errors:
Error 141 ICE03: Not a valid foreign key; Table: Shortcut, Column:
Target, Key(s): MdiShellDesktopShortcut C:\Development\MMAA\Main
Riyaz Mogharabin wrote:
Is it possible to use this with "WiXUI_INSTALLDIR" and WiX-2.0? I've
used them for my software, and I prefer not to change it, but it seems
that this is one of the features of WiX-3.0. Is that right?
You'll have to replace InstallDirDlg to also do the validation. Ther
Please keep /wix-users/ on the thread so everyone can participate.
Arthur Curvello wrote:
I got another problem now.. uninstalling..
MSI doesn't record property values so you need to save it so it's
available at uninstall time. The typical way is to write it to the
registry using RegistryVa
Chad Blomquist wrote:
> I have a WiX installer project that builds a MSI file for an IE
> toolbar/bho extension. When installing on Windows Vista with the User
> Access Control (UAC) turned *off* (ie, on install UAC does not ask you
> to confirm), there seems to be a permissions problem when wr
Anteru wrote:
> Impersonate='no' ExeCommand='[INSTALLDIR]DX9\dxsetup.exe' />
>
> scheduled using
>
>
> NOT
> Installed
>
>
> which always fails on Vista.
DirectX updates system files and therefore needs to be elevated. To be
elevated, a custom action must be deferred (using Execute="deferred
Bob Arnson schrieb:
> Anteru wrote:
>> > Impersonate='no' ExeCommand='[INSTALLDIR]DX9\dxsetup.exe' />
>>
>> scheduled using
>>
>>
>> NOT
>> Installed
>>
>>
>> which always fails on Vista.
>
> DirectX updates system files and therefore needs to be elevated. To be
> elevated, a custom action mu
Is this a typo or is it really called Vaidate.exe?
>>> Value="[INSTALLDIR]Vaidate.exe INSTALL"/>
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anidil
Sent: Monday, March 31, 2008 2:44 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-us
Can someone point me to any documentation available for creating
upgrades/Service packs using Wix 3.x ?
The tutorial on Wix2.0 says "For some strange reason, small updates and minor
upgrades cannot be run simply by clicking on the .msi file-they give the
error: "Another version of this product is
>
> The File element doesn't write any registry values. How are you creating
> the values that go to the wrong place?
>
If values aren't being set automatically, then I'm not sure how a Windows XP
install, or a Vista install with UAC turned on winds up having values in the
CLSID section to indicat
Using the Class element (etc) in WiX generates Registry table entries that
go to HKCR. That in turn follows the setting of ALLUSERS: if not set, it
goes to HKEY_CURRENT_USER\Software\Classes, while if ALLUSERS=1, it goes to
HKEY_LOCAL_MACHINE\Software\Classes. This was true in Windows XP for
packag
Can someone point me to the place in the documentation where it explains what
files need to go on the command line for candle and what do not?
Thanks!
Siegfried
From: Mike Dimmick [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 29, 2008 11:46 AM
To: Siegfried Heintze (Aditi); wix-users@lists.sour
Hey Guys,
For an install we have a custom action in our wixscript performing Regasm in
windows xp x64 environment. The install periodically fails at that point.
Sometimes it works..sometimes it doesnt. When I try to run regasm manually
using the command prompt on the same dll it always works.
Her
Hi,
I have the following line in wxi file:
How can I make this comparison case-insensitive?
Thanks,
Stas
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Ope
I have a problem with some wxs files and the corresponding msi files.
I can install the msi files fine. I can uninstall them fine if I say "msiexec
/x abc.msi SETUPDIR=C:\SETUPHERE".
If I don't specify the extra parameter on the command line, the uninstall will
fail. This is a problem I am supp
According to wix.chm, comparisons are case-sensitive.
You'll have to use 'Or', eg.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stas Klyachkovsky
Sent: Monday, March 31, 2008 12:53 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] case-insensitive comparison in inclu
I am attempting to read the list of web sites from the
applicationHost.config (IIS7 configuration file) file using a vbscript
function and present the user with a screen that allows them to choose
the web site onto which they want to install our web app (set up a
vdir, etc). But there seems to
Anteru wrote:
> Still no luck. I added the Execute="deferred" to the CustomAction and
> changed the schedule to Before='InstallFinalize' -- now it still
> fails, but it roll backs properly at least.
Check a verbose log. However, in my experience installing DirectX, it
sometimes returns a failur
Jordan Fitzgibbon wrote:
According to wix.chm, comparisons are case-sensitive.
Doc's not always perfect. ~= is available but undocumented. I just
submitted a review request to add it.
--
sig://boB
http://joyofsetup.com/
-
Siegfried Heintze (Aditi) wrote:
So I decided it would be good to store the value of SETUPDIR in the
registry and define a property with that value in uninstall process.
That's the typical way. Write it with RegistryValue and read it
RegistrySearch.
--
sig://boB
http://joyofsetup.com/
-
Stas Klyachkovsky wrote:
How can I make this comparison case-insensitive?
If you're using a current WiX v3 build, try ~=.
--
sig://boB
http://joyofsetup.com/
-
Check out the new SourceForge.net Marketplace.
It's t
ArunKumar ArcotVijayaKumar wrote:
msiexec /i SampleUpgrade2.msi REINSTALL=ALL REINSTALLMODE=vomus"
Is this still true in Wix 3.x or did things change in this regard in
new wix versions ?
That's how MSI works. WiX isn't involved at install time (other than
with custom actions).
--
sig://
Abdullah Ahmed wrote:
> For an install we have a custom action in our wixscript performing
> Regasm in windows xp x64 environment. The install periodically fails
> at that point. Sometimes it works..sometimes it doesnt.
That's a great reason to not use custom actions to self-register stuff.
Us
Chad Blomquist wrote:
> If values aren't being set automatically, then I'm not sure how a
> Windows XP install, or a Vista install with UAC turned on winds up
> having values in the CLSID section to indicate "InprocServer32" path,
> etc. I never explicitly write those, but they show up in the
Bad idea. Best practice is to run regasm /regfile:myasm.reg myasm.dll and
turn the resulting registry file into RegistryKey and RegistryValue
elements.
I believe tallow (v2) and heat (v3) can detect an assembly to be registered
for COM and generate Registry (tallow) or strongly-typed COM elemen
34 matches
Mail list logo
