indeed when I open the original MSI file with Orca ALLUSERS property is missing
(i.e. it is per-user mode).now I open the MSI file with the merge module inside
and I see ALLUSERS property is set to 1 (i.e. per-machine)there is no other
change in the WiX file so it must have been set automatical
Some of those VC merge modules have a Property table with ALLUSERS=1, so that
will do it. If you're using a bootstrapper maybe you could run the VC9 redist
executable instead of using merge modules.
Phil Wilson
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas.
David suggested that you check a verbose log. That really should be everybody's
first step to determining why an install (or uninstall) didn't work as
expected. Always, always, always check a verbose log first.
Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-06
Sounds like your original package was per-user. The VC9 merge module very
likely accesses per-machine locations. That merge module must have required
that you change the package to per-machine so that it compiled successfully.
If your source control system does not show any other changes then pe
So I have WIX 3.6 and latest and gratest windows server 2008 r2 sp1 with
windows updates installed.
My installer does not throw any error but it does not create application
pool or does not create website.
But everything works fine in windows server 2008 R2 . I don't know is it SP1
issue or with
So I guess you were right. Here is excerpt of the log: MSI (c) (D8:18)
[14:49:27:908]: Doing action: FindRelatedProducts
MSI (c) (D8:18) [14:49:27:908]: Note: 1: 2205 2: 3: ActionText
Action 14:49:27: FindRelatedProducts. Searching for related applications
Action start 14:49:27: FindRelatedProd
Glad to help. I was merely pointing out where you could look to find the
history of the changes so if you are still seeing a bug then go ahead and
file one for the devs.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-BA-can-t-parse-unknown-a
Recently upgraded by version of wix and when I now build the Wix MSI I get
the following error
The Data element's value, 'DS Apps', is not a legal identifier.
The wix source code is:
adppmdl.dll
DS Apps
I'm guessing it doesnt now like the space in DS Apps...but I want this field
to ha
Setting the Column to PrimaryKey="no" seems to have solved this problem for
me and this is fine for my use.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Data-element-error-tp6867114p6867167.html
Sent from the wix-users mailing list archive at Nabb
Is there a way to replace the prerequisite .Net install UI with just an
notification to the user that they need to install a particular version of
.Net before they can install the bundle?
Thanks,
Shruthi
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.c
Two entries in Add/Remove Programs usually means you tried to upgrade a
per-system product with a per-user install, or vuice versa (all other things
being correct to do the upgrade). A verbose log will say something near the
FindRelatedProducts action.
Phil Wilson
-Original Message-
Hello,
Any thoughts about this? Is "z-ordering" of UI controls something which is not
possible in WIX, or did I miss some trick?
Thank you for any suggestion
Jan Krivanek
-Original Message-
From: Jan Krivanek [mailto:jan.kriva...@microsoft.com]
Sent: Thursday, September 22, 2011 6:26 P
Upgrading to a newer version (v3.6.2019) fixed this issue. Thank you!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-cleanup-folder-created-by-Burn-in-temporary-directory-tp6848834p6866287.html
Sent from the wix-users mailing list archive at
Thanks for your email and the link!
That fix only fixed it in the native interface to BA. It is still an issue
with the C# interface. I still repro the problem on build v3.6.2019.0
Please let me know if I should go ahead a log a bug.
Thanks!
Shruthi
--
View this message in context:
http://wind
A typo. A simple typo mistake.
-Original Message-
From: Brian Lemke [mailto:brian.le...@apihealthcare.com]
Sent: Thursday, October 06, 2011 7:36 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action Fails when InsertingTemoporaryRows.
Tha
Thanks Jacob. With some help from your post I seem to have gotten it to at
least now not error. It seems to add all the records however now its time to
figure out why it is not actually deleting any of the files
--Brian
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@
Check the feed: http://wix.sourceforge.net/releases/wix3.6.feed
http://wix.sourceforge.net/releases/wix3.6.feed . The bug you mentioned was
fixed in v3.6.1929.0.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-BA-can-t-parse-unknown-args-wit
Hi Guys,
I am fairly new to wix and am trying to write an installer to install a web app
into iis 7 using wix 3.5. This app needs to be installed into an existing
website, is there a good way to verify the site exists using wix? I know I can
put the stanza outside a Component and if it exists
So I verified that digitally signing the MSI does NOT break MajorUpgrade
process and product gets upgraded just fine.Also adding the MSM Merge module
DOES break MajorUpgrade process.When I add the following two lines Merge and
MergeRef I end up with two installations of my product:
...
Hey John,nice to hear from you :) Yes, I did change the Product Id and Version.
I used to publish 3 more upgrades already. However when I digitally signed the
MSI, integrated a merge module and changed the Package InstallerVersion from
200 to 300 now the upgrade is not recognizing the old versi
20 matches
Mail list logo
