Hi,
seems I should open bug/feature request in wix website ?
please let me know if the issue bellow not working for me since I dont know
how to use or it just missing feature ?
Thanks in advance,
Fadi
On Nov 25, 2007 10:44 PM, Fadi Haik [EMAIL PROTECTED] wrote:
Hi
I am trying to update on
Снижение рисков ведения бизнеса правовыми и финансовыми методами
(или ошибки оптимизации налоговых издержек организации)
АВТОРСКИЙ ПРАКТИЧЕСКИЙ СЕМИНАР
7 ДЕКАБРЯ 2007 ГОДА г. Санкт-Петербург
ТЕЛ: / 812 / 9 48 _ 2 _ 69 9
В ПРОГРАММЕ:
10.00 - 17.00
СПИКЕР:
Hello, developers!
I am trying to change xml file using wix passing some parameters to it,
using this sample:
?xml version=1.0?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
Product Id=88DC12AD-74D8-415a-AFE7-83C1BE05A3EB
As I previously said (though in private mail) the solution is rather
simple:
SelfRegCost='1'
Anything else is just a waste of your life by overcomplicating simple
things and reinventing the wheel :D
János
Andrew Sampson wrote:
I've had a similar problem - our Wise MSIs were previously using
As I previously said (though in private mail) the solution is rather
simple:
SelfRegCost='1'
Anything else is just a waste of your life by
overcomplicating simple things and reinventing the wheel :D
Except that the MSI documentation strongly suggests that you shouldn't:
Installation
John Hall wrote:
As I previously said (though in private mail) the solution is rather
simple:
SelfRegCost='1'
Anything else is just a waste of your life by
overcomplicating simple things and reinventing the wheel :D
Except that the MSI documentation strongly suggests that you
John Hall wrote:
As I previously said (though in private mail) the solution is rather
simple:
SelfRegCost='1'
Anything else is just a waste of your life by
overcomplicating simple things and reinventing the wheel :D
Except that the MSI documentation strongly suggests that you
Fadi,
This information has been put onto my wix wiki as a working example. Here
is the link:
http://wix.mindcapers.com/wiki/XmlConfig_Example
Julie Campbell
[EMAIL PROTECTED]
--
Message: 4
Date: Wed, 28 Nov 2007 11:19:52 +0200
From: Fadi Haik [EMAIL PROTECTED]
Do you mean installing my app under System folder? Nope.
As for the merge modules, they are installed into their default folder. If I
have to install the 71 dlls into my app's folder, I need to modify them by hand
using Orca, right?
Actually MFC71 wasn't a typo, actually I need VC2003
Albert,
From the wix.chm (v3) file, see the page titled WiXUI dialog library
guide. Here is the copy paste:
---
Specifying a license file
WixUIExtension.dll includes a default, placeholder license agreement. To
specify your product's license, override the default by specifying a WiX
variable
FWIW, I was just trying to install the 71 dlls using msm myself the other
day and never got it to work properly. Then someone on the internet
suggested that the merge modules were broken and that you just should
extract the dlls and install them as regular files into your app folder.
So that's
Hi,
I'm including the msvc9 crt merge module and its related policy merge
module, after doing so I am turning up the following errors:
main.wxs(323,0): Warning LGHT1055: The InstallExecuteSequence table contains
an action 'SxsInstallCA' which cannot be merged from the merge module
Keeping Wix users on the list...
It's not clear to my why the 7.1 Dlls would be in use by Explorer unless
you are installing them into a folder where Explorer is using them from,
so you'll have to explain exactly where they are installed to. I don't
know what your default is because the 71
Without seeing your code I can't be sure of this, but many custom
actions are woefully short of error checking. Calling APIs and not
checking the result is unfortunately common, so you need to check these
things.
You can log errors into the MSI log with something like this in your
custom action:
Hi all,
I'm experiencing some problems when I try to create a WIX installer for my
project which consist of the following parts:
*ComSrv.dll is a com component written in c++ which should be installed as a
COM+ application.
* NetAsm.dll is a .net assembly written in C# that will be
Hello everyone,
up to now I used the last official build, build 2925 for my installs. I want
to use the patching feature as described in Peter Marcu's Blog and tried to
build my installs with the latest weekly build. Unfortunately, I now get
very strange CNDL1054 errors. I tried to find out what
I have an executable x.exe that I need to install over x.exe if it
already exists. I want to replace an existing executable which may or
may not be there. I want to do that overwriting no matter what :D. If it
is there it is not through MSI installation but through manual copying.
How can I do
Siz hayal edin,biz gerçekleştirelim...
Bir düşünün... Zaman öyle hızlı akıyor ve biz öyle büyük bir koşturmacanın
içindeyiz ki... Ev, iş, çocuklar, okul.. Bir durun ve düşünün.Biraz olsun ara
verin,kendinize de vakit ayırın.Sevdiklerinizle paylaştığınız zamanın ve
kendinize ayırdığınız zamanın
Hi all,
After installing a service using the ServiceInstall table/element,
MSCONFIG reports the manufacturer as unknown.
If I use the self-registering code of the service executable (i.e.
myservice.exe /i), the manufacturer field is populated correctly.
Is this a known issue with MSI's
19 matches
Mail list logo
