hi Warne any guideline on using msistuff.exe ?
Also which setup.exe should i use in command line? the one available with
from Wix toolset?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/setupbld-setup-exe-repair-install-tp3973894p5376436.html
Sen
- Burn supports that.
- Not that I know of.
- Chained MSI detection is built into Burn. Your "UI" code you add to Burn
allows you to react to command-line options and package detection performed
by burn and allows you to order (if you wish) or decide to
include/exclude/even remove packages as part
Okay, so after digging through the code, I noticed that when generating the
bootstrapper using the -mi option, setup.exe does something interesting:
if (pPackage->dwAttributes & SETUP_INSTALL_CHAIN_IGNORE_FAILURES)
{
dwUiLevelPackage |= INSTALLUILEVEL_PROGRESSONLY; // don't throw any scary
erro
, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: JKLists [mailto:jkli...@ifm-services.com]
Sent: 02 December 2009 07:09
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] setupbld diagnosing?
John L Krupka wrote:
&
John L Krupka wrote:
> You should be able to set up preconditions on those things in the msi.
> Setupbld is not the place for that to the best of my knowledge.
>
This is where my lack of understanding how MSIs work raises its head.
My MSI has a condition where it needs .NET 3.5 SP1, and refu
You should be able to set up preconditions on those things in the msi.
Setupbld is not the place for that to the best of my knowledge.
JKLists wrote:
>
> My WiX project has a handful of prerequisites, for example, the
> application requires .NET 3.5 SP1. My WiX project correctly does not run
Don't worry. Burn will be part of WiX v3.5. Said another way, WiX v3.5 won't
release without Burn. I'm just caught up in a whirlwind of change right now
that has significantly impeded the progress of Burn. Getting all that
unblocked is my utmost priority.
On Tue, Nov 10, 2009 at 3:35 AM, warne wa
Turned out this is not so trivial.
Line in the setup.cpp file (the source for the SETUPBLD stub setup.exe) says
"hr = StrAllocConcat(&pwzProperties, L" REINSTALL=ALL
REINSTALLMODE=\"vomus\"", 0);"
this forces a minor upgrade instead of a normal install that produces the
change/r
or more simply the setup.exe version just goes straight to "Resuming install.."
instead of "Welcome to install" ?
From: warne...@hotmail.com
To: wix-users@lists.sourceforge.net
Subject: setupbld setup.exe & repair install
Date: Mon, 9 Nov 2009 15:57:31 +
Hi there,
I am using setupbld t
On Sun, Nov 8, 2009 at 10:39 PM, John Robbins wrote:
> Hello K,
>
> Glad my blog entry could help. However, I didn't go into the icon stuff as I
> figured that was common knowledge, but that was a mistake on my part, I'm
> sorry! You've done everything right so far. :)
Not common knowledge but
pe it helps!
John
Wintellect
http://www.wintellect.com
877-968-5528
>-Original Message-
>From: noopy@gmail.com [mailto:noopy@gmail.com] On Behalf Of
>kerbe...@noopy.org
>Sent: Sunday, November 08, 2009 7:26 PM
>To: John Robbins
>Cc: General discussion for Windows Installe
On Sun, Nov 8, 2009 at 1:05 PM, John Robbins wrote:
> K,
>
> Here's how I got SetupBld.exe from WiX to behave like you wanted:
> http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/02/27/creating-a-bootstrap-loader-with-wix-3-0.aspx.
Oh, I think I've got it now, or at least am getting there
On Sun, Nov 8, 2009 at 1:05 PM, John Robbins wrote:
> K,
>
> Here's how I got SetupBld.exe from WiX to behave like you wanted:
> http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/02/27/creating-a-bootstrap-loader-with-wix-3-0.aspx.
John, thanks for your response and well-written blog entr
K,
Here's how I got SetupBld.exe from WiX to behave like you wanted:
http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/02/27/creating-a-bootstrap-loader-with-wix-3-0.aspx.
Hope it helps!
John
Wintellect
http://www.wintellect.com
877-968-5528
>-Original Message-
>From: kerbe...@n
Bob Arnson a écrit :
> Frédéric Viollet wrote:
>
>> -I want to install a 64 bit product (my exes and dll are natively
>> compiled for 64bit) on a 64bit OS
>> -I build an x64 MSI (Platform=x64, Win64=yes in Components, etc...)
>> -I build a 32bit bootstrapper using setupbld
>> -This setup will b
Frédéric Viollet wrote:
> -I want to install a 64 bit product (my exes and dll are natively
> compiled for 64bit) on a 64bit OS
> -I build an x64 MSI (Platform=x64, Win64=yes in Components, etc...)
> -I build a 32bit bootstrapper using setupbld
> -This setup will be able to install the embedded x6
Bob Arnson a écrit :
> Frédéric Viollet wrote:
>
>> -do I have to install the 64bit version of Wix? I guess not...the
>> 32bit version should still be working... am I right?
>>
>
> The 64-bit WiX installer exists to support MSBuild running as a 64-bit
> process. That's all.
>
>
>> -wil
Frédéric Viollet wrote:
> -do I have to install the 64bit version of Wix? I guess not...the
> 32bit version should still be working... am I right?
The 64-bit WiX installer exists to support MSBuild running as a 64-bit
process. That's all.
> -will setupbld.exe build 64bit executables? If not, co
Fix was just checked-in. If all goes well, build that comes out tomorrow will
be much happier.
-Original Message-
From: Uwe Stump [mailto:uwe.st...@gewi.com]
Sent: Friday, January 30, 2009 01:14
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] SetupBld
17:23
An: General discussion for Windows Installer XML toolset.
Betreff: Re: [WiX-users] SetupBld and IIs Problem
I think this is a bug introduced with the large changes to IIS CA recently to
handle UAC/IIS7 better. Can you try an older build and see if the problem
reproduces there? If it does
Uwe Stump wrote:
> I do not know if attachements are allowed. So here is the critical section of
> the log file:
>
> ...
> MSI (s) (0C!4C) [09:17:43:187]: Resolving source.
>
The critical part is right before: That's where MSI identifies the
resource it needs the source for.
--
sig://boB
ht
).
Thanks.
-Original Message-
From: Uwe Stump [mailto:uwe.st...@gewi.com]
Sent: Thursday, January 29, 2009 04:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] SetupBld and IIs Problem
Dear all,
after some research I found a workaround:
I do wrap my msi
Dear all,
after some research I found a workaround:
I do wrap my msi to an exe file with setupbld now by using the command line
option -msuc (c added). c means "enable msi caching". So the whole msi gets
cached in Windows\Installer. On uninstall the msi file will be found by MSI and
the messag
40
MSI (s) (0C!4C) [09:18:35:890]: Doing action: WriteMetabaseChanges
Action start 09:18:35: WriteMetabaseChanges.
Action ended 09:18:35: WriteMetabaseChanges. Return value 1.
...
Can anyone help me to avoid the strange message?
Kind regards,
Uwe
-Ursprüngliche Nachricht-----
Von: Bob Arnson [mail
Uwe Stump wrote:
> The MSI-file has been wrapped to IIsInstallProblem.exe. The installation with
> these EXE-file works fine but on uninstall via Software I got the following
> message: "The feature you are trying to use is on a network resource that is
> unavailable. Click OK to try again, or e
dated roadmap about all of this is coming soon. I've just been
> focused on killing the last few extension bugs. Can you tell what we're
> focused on?
>
> -Original Message-
> From: carlldev [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 27, 2008 01:
his is coming soon. I've just been focused on
killing the last few extension bugs. Can you tell what we're focused on?
-Original Message-
From: carlldev [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 27, 2008 01:39
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX
ll supersede the
> functionality completely. All of the ClickThrough related work moved to
> WiX v4.
>
> -Original Message-
> From: carlldev [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 26, 2008 07:22
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-us
@lists.sourceforge.net
Subject: Re: [WiX-users] setupbld, bootstrappers and command line parameters
(msicl)
I've logged this bug on SourceForge as
Bootstrapper cannot take command line parameters with spaces - ID: 2229894
Rob has changed the Group property to v4.0. Does this mean we have to wait
for Wix 4.0 b
I've logged this bug on SourceForge as
Bootstrapper cannot take command line parameters with spaces - ID: 2229894
Rob has changed the Group property to v4.0. Does this mean we have to wait
for Wix 4.0 before we see a change to this?
--
View this message in context:
http://n2.nabble.com/setupb
2008/11/6 carlldev <[EMAIL PROTECTED]>:
>
> Has anyone noticed that the wix bootstrappers can't take command line
> parameters that have spaces in them? I have created a bootstrapper using
> setupbld, and it works fine if run as it is. But try and feed in some
> parameters like this:
> setup.
Hi Scott
I haven't tried exactly what you are describing, but I can say this:
1) Setup.exe extracts to an uniquely named folder in %TEMP%. Whatever
you have built in the setup will be extracted to there. The is MSI
placed in that same folder as well.
2) I tried to embed an MSP in a setup.exe
Frédéric Viollet wrote:
> Do you know another bootstrapper that would allow me to do this?
No but I'm sure there are some that exist.
--
sig://boB
http://joyofsetup.com/
-
This SF.net email is sponsored by: Splunk Inc.
St
Bob Arnson a écrit :
> Frédéric Viollet wrote:
>> Ok. I've just had a look at setupbld source code. And it seems that
>> REINSTALLMODE is set to vomus for a minor upgrade.
>> I guess I need it to be set to vamus to force all files to be
>> rewritten. Is there another bootstrapper that would allow
Frédéric Viollet wrote:
> Ok. I've just had a look at setupbld source code. And it seems that
> REINSTALLMODE is set to vomus for a minor upgrade.
> I guess I need it to be set to vamus to force all files to be
> rewritten. Is there another bootstrapper that would allow me to
> achieve this?
Se
Frédéric Viollet a écrit :
Bob Arnson a écrit :
Frédéric Viollet wrote:
When I perform a minor upgrade of my product using the generated
executable file, not all of the files are upgraded. Only the files
that have changed are updated.
I thought that even on a minor upgrade, all the fil
Bob Arnson a écrit :
> Frédéric Viollet wrote:
>> When I perform a minor upgrade of my product using the generated
>> executable file, not all of the files are upgraded. Only the files
>> that have changed are updated.
>> I thought that even on a minor upgrade, all the files for the
>> installed
Frédéric Viollet wrote:
> When I perform a minor upgrade of my product using the generated
> executable file, not all of the files are upgraded. Only the files
> that have changed are updated.
> I thought that even on a minor upgrade, all the files for the
> installed components would be upgrade
Hongping Lim wrote:
Does the default setup.exe that comes with setupbld.exe support both
UI and quiet installation (/q) modes in the generated .exe?
No, that's not currently supported. (You can see the source in the
setupexe directory.)
--
sig://boB
http://joyofsetup.com/
--
Josh Maletz wrote:
Thanks for the Process Monitor tip Bob. I didn't see anything showing
up in Task Manager for the setup file, but it sure showed up in
ProcMon, and yes, I was being sorta dumb.
ProcMon reveals all.
Leads me to a new question. The setup works fine if the application
is
ECTED]
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Setupbld produces file but doesn't do anything?
Josh Maletz wrote:
setupbld -out XsSetup.exe -mcst ExtendedServicesSetup.msi -setup setup.exe
-title "Extended Services Setup"
The -mt subswitch is looking for U
Josh Maletz wrote:
setupbld -out XsSetup.exe -mcst ExtendedServicesSetup.msi -setup
setup.exe -title "Extended Services Setup"
The -mt subswitch is looking for UI transforms but you aren't supplying
any. That would break it, however. How big is your package? Extracting
it might take a whi
42 matches
Mail list logo
