Sorry for repeating, but does anyone have any clues?
-Original Message-
From: Vadym Verba
Sent: Friday, November 11, 2011 11:37
To: 'wix-users@lists.sourceforge.net'
Subject: Burn: disk space usage calculation
Hello.
I have a bundle with several packages of .msi and .exe types, plus add
Any suggestion what could be wrong? I found in this forum that users hit
different kind of errors with WriteIIS7ConfigChanges with error code
0x80070103, which means ERROR_NO_MORE_ITEMS
What does this error indicate in this context?
- Original Message -
From: Zhisheng Huang
To: John Co
Thanks for your reply. I have finally identified the issue, seems the
property name is case-sensitive.
Thanks,
Fangbai
On Wed, Nov 16, 2011 at 5:41 PM, Peter Shirtcliffe wrote:
> Those properties should work fine in Wix 2. I'd suggest looking at your MSI
> with Orca or instead to see if they ar
Well, it should. Unfortunately it doesn't. There is neither
Product.Generate.wxs not _ProjectName.wxs what is usually generated.
I managed to uninstall version 3.6.2221.0 and could install version
3.5.2519.0
Now the Votive plugin spawns Heat to harvest the application project's
output and gener
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Enable-disable-Next-button-tp6998152p7001589.html
Sent from the wix-users mailing list archive at Nabble.com.
--
All the dat
Absolutely possible. Wouldn't be much fun if all files on installation
media had to be in the same folder. Wouldn't even work for files with
the same names that should go into different subfolders like you are
asking about.
On your hard drive just set up the folders the way you ultimately want
the
Hello!
Do you have any hints for me, how a can get the package names from my
custom bootstrapper, to show a package list to the user?
Best regards
Nikolaus Keuth
--
Hello!
I'm currently writing my own MBA with wix3.6.
I have a very simple question:
How can I
Hi,
I have authored an installation package using Votive in VS2010. The
package is supposed to install a web application. On my development
machine, which is Windows 7 Ultimate with IIS 7.5.7600.16385, I can install
the package properly. However, on our test web server, which is Windows
Server
Hi,
I use a trick now and it works, but it's not the fine way, I think.
In
I have to place my property containing the full path to my folder.
I have an action where I set this property.
Now I have a second action where I clean this property, or set a stupid
value. ;-)
In the ExecuteSeq
Can you elaborate a bit more? I've tried several permutations of adding
with no success.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Enable-disable-Next-button-tp6998152p7000868.html
Sent from the wix-users mailing list archive at Nabble.com.
>From the point of view of the installation sequence, user input from custom
forms and command line are the same thing.
Blair
--
All the data continuously generated in your IT infrastructure
contains a definitive record
Blair,
Thanks for the input and pointing me to relevant documentation. I had to read
this a few times to understand, but what I get is that because of the nature of
the inifile element and its relationship with a table, we need to store off the
user data on install, then on upgrades, retrieve
Hi,
after some discussions I've changed my mind and have implemented the code
to support major upgrades.
But when I now launch the second package to upgrade the first I get no
hint that this will be an upgrade installation.
How could I bring up a message or change the welcome dialog to ask the
On 16/11/2011 12:06, Harper wrote:
> What's wrong? How can I get information, why it failed? And how can this be
> fixed? One thing that's different from a successful installation is that it
> failed on a computer that's a member of a domain. But I am not aware of
> policies that disallow software
Hi,
It is an exe because it is a bundle installer (it is installing multiple
MSI files I assume). A bundle can't be an msi, it is because of the
limitations of the msi format.
- The exact same problem happened to me when my Windows Installer service
got broken. You should try re-registering it:
m
I tried to install WiX 3.6.2221.0 on a computer. After some seconds the
message "*Failed to install*" appears in the UI. I can "Try Again", but this
does not gives any better result.
Due to boot manager I could try this with Windows7(64) as well was with
Windows XP(32) SP3. Unfortunately the insta
Those properties should work fine in Wix 2. I'd suggest looking at your MSI
with Orca or instead to see if they are present in the Property table. If so,
then generate a verbose installation log and see what happens in there. If
you still have a problem, let us know what specifically goes wrong.
Yes case matters. Specifically, all upper case denotes a public property that
can be set on the command line.
For the Product/Version only, the 4th field is stored but not used for
version calculations.
-Original Message-
From: Justin Hull [mailto:justin.h...@assetpoint.com]
Sent: 15 Nove
18 matches
Mail list logo
