Does product B always install a particular component guid (or at least a
narrow set)?
-Original Message-
From: Lisa Gracias [mailto:lisathelugubri...@gmail.com]
Sent: Monday, October 18, 2010 10:38 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Prerequis
Whenever Windows Installer launches a DLL-type custom action, it does so
from a separate msiexec.exe process instance (sandboxing the custom action
code, if you will). However, because this "sandbox" process may be reused,
and because loading pre-4.x CLR runtimes "marks" the process preventing a
di
I am building an installer for Product A. Product A should not be installed
unless Product B is already installed. There are multiple versions of
Product B that are supported by Product A. Product B does not create any
registry entries. So instead I am checking for the upgrade code of Product B
in
What machine (OS/service pack) are you using to build? What language are you
trying to set the merge module to that it doesn't accept?
-Original Message-
From: sagar shinde [mailto:sagar.i...@gmail.com]
Sent: Monday, October 18, 2010 6:23 AM
To: WiX-users@lists.sourceforge.net
Subject: [W
That suggestion doesn't make sense to me. doesn't incorporate
the included file as a different fragment, it "imports" the file at the
location of the processing instruction in building the DOM actually
presented to the compiler proper, making it lay in the same fragment.
Also, merge modules don't
You may be "just a contractor" but (while I am not a lawyer nor do I play
one on TV) that may not absolve you of your liability for your role in
license violations if repackaging is not allowed by your client's license to
the repackaged product. I would seek indemnity from your client if they
insis
MsiMsp/PatchWiz will build MSP files that will never successfully be applied
and/or will cause other problems (orphaning resources, or sometimes worse)
later on without any warnings. Pyro is better at ensuring correctness.
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl
Your failures are caused by previous files having a higher version than the
ones you are trying to install.
Look at these log entries:
MSI (s) (7C:58) [12:56:47:348]: Disallowing installation of component:
{B755AE68-73F9-41F4-9777-A18D767B305B} since the same component with higher
versioned keyfi
Hi there,
I'm required to create a shortcut in Wix to launch powershell.exe so as to
execute a script as follows:
%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -NoExit "C:\My
Data\myscript.ps1".
I tried various permutations/combinations with the "Target" attribute but I
ca
You wrote: "It is a "simple" desktop app that installs into program files
(x86); with the only catch being that there is a cache directory and a data
directory that are global to all users of the application, so currently that
are placed as subdirectories below the installed directory, and the secu
I find the following sequence interesting:
MSI (s) (0C:1C) [13:22:51:678]: Transforming table Component.
MSI (s) (0C:1C) [13:22:51:678]: Note: 1: 2262 2: Component 3: -2147287038
The second line means: Stream does not exist: Component. System error:
STG_E_FILENOTFOUND.
The Component table is req
In any given build, most of the time is typically taken doing three things:
moving files, building cabs, and embedding.
For the scenario you describe, I would recommend each MSI end up with (at
least) three cabs (1. the 70 MB "common" cab, 2. the 50 MB "locale" cab, and
3. the 3MB "platform" cab).
I just bought a copy too - and have devoured the first two chapters. Thanks!
I wish it was around a few months ago!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-book-available-tp5647051p5648913.html
Sent from the wix-users mailing list arch
Adding more information as I see
We did validation of the latest patch (that has uninstall problem). This latest
patch has gone on the top of {earlier patches + base product}. The validation
(again, not used any custom ICE validators) errors are below. Any thoughts on
these errors? Note tha
I already purchased a copy as well :-). So far, it looks to be quite good.
Thanks for the effort!
John
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: Monday, October 18, 2010 4:11 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WiX book avai
Thanks for the recommendation Chris! I've been working on the thing since
January, so hopefully it will meet everyone's expectations.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-book-available-tp5647051p5648716.html
Sent from the wix-users m
Hope it helps...
http://blog.deploymentengineering.com/2010/10/new-bookebook-available-wix-developers.html
Chris
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
- Original Message -
If it works when as a per-user install, the issue might be that you're not
impersonating when installing per system (when the code is running with the
local system account).
Phil Wilson
-Original Message-
From: Michael Clark [mailto:mcl...@fullarmor.com]
Sent: Monday, October 18, 20
Hi,
I'm using the following
However when I rung the install I get
MessageQueuingExecuteInstall: Error 0x80070534: Failed to add message queue
permissions
MSI (s) (1C!F4) [14:52:00:631]: Closing MSIHANDLE (467) of type 790531 for
thread 2804
CustomAction M
Hi,
I have a project that builds 88 different flavors - the cross product of
these three variables:
Platform: x86 | x64
Configuration: Beta | Retail | Evaluation | Another Evaluation
Locale: cs, en-us, es-es, de-de, fr-fr, it-it, ja, ko, pl, zh-cn, zh-tw
A core exe (3MB) changes with both Pla
Thanks for the ideas Steve.
I tried running my code in a separate thread, like yours, but it still
hangs. I'm running on Windows Vista Business 32-bit. I noticed, by
accident, that in Process Explorer when the custom action starts up that
a new process tree is spawned:
1. msiexec.exe
2.
I don't see errors while validating the original MSI, only INFO and WARNING.
Attached is the output file. Let me know if you can't view the attached file.
(I posted the following in another email, but including here to make sure you
see it. in that email I attached the uninstall log file. it is
Do I have this correct that you want to let the user select where the install
directory is and also where the directory is that their data is stored? You
can do this in WiX by adding a user interface to your installer and make use
of the DirectoryList and DirectoryCombo controls. They'll let the u
A major upgrade, as you probably know, will completely remove the old
version. So, if your second installer does not write to the registry, it
makes sense that the value will be removed but not replaced. You shouldn't
change the UpgradeCode for the lifetime of the product, across all upgrade
scena
At first, you were using:
!(loc.License_Agreement)
which uses a localization variable. You then switched to placing all of the
RTF content inline. Did you mean to do that? Or did you still want to use
the localization variable? If so, you can put the RTF data in your .wxl
file, such as:
An
I think the ICE45 can be ignored if it only occurs on new rows added by
the patch and the attributes are set to the value for "Patch Added" -
thats a known issue with the ICE test.
The ICE03 error repeats what your original error says: that you have an
invalid database structure but Ive seen Insta
So, is your build server building the dependencies after the .wixproj
project? Is it a matter of it not invoking the correct configuration?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Project-dependencies-not-working-tp5640712p5647660.html
Sent
Another observation. There is a new file that is supposed to be laid down by
the latest patch (that is having the uninstall problems). I can't see this file
after installing this patch? Does anyone think this could cause this problem
while uninstalling?
I attached the uninstall log file, in ca
Thanks Peter for the response. I used orca to do validation on the patches. I
didn't use custom ICE validators; I mean left the field blank. It's giving
errors on valid patches also. Errors of this kind:
" ICE03 ERROR Table: MsiPatchHeaders Column: Header Missing specifications in
_Validation
Thanks for the reply...
I'm not adding any ComponentRef, so that's probably it. Just out of curiosity,
adding a under a is automatically included but file
references (bundled under a ) won't?
Thanks
Mark
-Original Message-
From: jhennessey [mailto:jack.hennes...@hyland.com]
Sent:
Hi everyone. I've just gotten a book about WiX published. A portion of the
proceeds will go to the WiX team. I'm not sure how all of that is set up, so
Rob and Bob let me know if you don't see it! Anyway, it should be a good
guide for those new to WiX. It also gets into creating UI controls, Windo
hi
I am using wix installer and want to merge new model into wxisting project,
i have done localization in project as well as in module also but
i am getting error i.e.
Unable to open merge module.Check to make sure the module language is
correct. 'The language of this installation package is not
Brian,
Thank you for the detailed explanation. I will definitely consider this
issue.
I know that the company is ISV for Miscrosoft, however, if there is only one
doubt about rights to create a single package that includes both the
application and SQL server express, my suggestion to them will
Pyro is correct. The doc should say key path rather than key file. Pyro
probably has more checks built in than msimsp.
-Original Message-
From: Tobi Ha [mailto:tob...@gmx.net]
Sent: 18 October 2010 11:02
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] what Patch Creation Process
Hello everyone,
I tried to create a patch for one of our products and stumbled across the issue
that the components key paths was changed accidentally.
It was changed because the key path is a registry key that is going to be
removed during the update.
The result is that when using wix/pyro for t
Yes. The summary info stream's "creating application" field is set to
Windows Installer XML (version number).
http://msdn.microsoft.com/en-us/library/aa372045%28VS.85%29.aspx
You can view this in InstEd/Orca/SuperOrca.
-Original Message-
From: teuf008 [mailto:teuf...@gmail.com]
Sent: 18
Property with ID 18 in _SummaryInformation table will contains string like
"Windows Installer XML (3.5.2215.0)" for every package created with WiX.
-Original Message-
From: teuf008 [mailto:teuf...@gmail.com]
Sent: Monday, October 18, 2010 11:38 AM
To: wix-users@lists.sourceforge.net
Subje
Hi.
I am wondering if it is possible to determine whenever a MSI file was
created using WIX?
Any ideas?
Regards,
teuf008
--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4
Chris,
I had a similar problem opening the windows OpenFileDialog common dialog. I
found it would work fine on Windows Server 2003 but on Windows 7 it just
hung, showing the same spinning wheel.
I ended up having to open the dialog in a new thread, then all worked fine.
My C# code was as follow
39 matches
Mail list logo
