Re: [WiX-users] setupbld setup.exe & repair install

[Sagar1111]

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
Sent from the wix-users mailing list archive at Nabble.com.

--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] SETUPBLD and BURN, multiple uninstalls

[Blair]

- 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 of your installation.

-Original Message-
From: Simon Topley [mailto:simon.top...@mwhsoft.com] 
Sent: Friday, July 23, 2010 3:21 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] SETUPBLD and BURN, multiple uninstalls

...

I guess this will be more of a request for burn... will(does) it:

- have only one item in the uninstall list that represents many msi's
chained.
- allow a post install script to be run so I wouldn't need this second
lightweight installer at all
- check for the presence of any of the chained msis before attempting to
install, and react according to some command line option?

...


--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] SETUPBLD and BURN, multiple uninstalls

[Simon Topley]

Hi Team,

It's been a while. I've recently given up on trying to find ways to trick the 
installer into working where a service needs to be started that relies on a 
copy of the CRT or .NET that the installer has to put on..An age old tale of 
mystery.

I've finally produced a bootstrapped installer, I've always suspected that it 
will cause me a headache, but the generation of it was pretty simple.. I have 
my main installer, then a second installer that just has an exe and the service 
control stuff in it. Sadly the user now has to uninstall 2 programs, and I just 
know users will forget to do this. It seems that the bootstrapper (I used 
setupbld) doesn't notice that one of the packages it is about to install is 
already on the system, so carries on anyway.



I guess this will be more of a request for burn... will(does) it:

- have only one item in the uninstall list that represents many msi's chained.
- allow a post install script to be run so I wouldn't need this second 
lightweight installer at all
- check for the presence of any of the chained msis before attempting to 
install, and react according to some command line option?

one day we'll get this right I'm sure .whatever happened to that portable 
executable idea, I liked that.

Simon

Disclaimer: This electronic communication and its attachments may contain 
confidential, proprietary and/or legally privileged information which are for 
the sole use of the intended recipient. If you are not the intended recipient, 
any use, distribution, or reproduction of this communication is strictly 
prohibited and may be unlawful; please contact the sender and delete this 
communication. MWH Soft does not warrant or make any representation regarding 
this transmission whatsoever nor does it warrant that it is free from viruses 
or defects, correct or reliable. MWH Soft is not liable for any loss or damage 
that occurs as a result of this communication entering your computer network.

The views expressed in this message are not necessarily those of MWH Soft. This 
communication cannot form a binding agreement unless that is the express intent 
of the parties and they are authorized to make such an agreement. MWH Soft 
reserves all intellectual property rights contained in this transmission. MWH 
Soft reserves the right to monitor any electronic communication sent or 
received by its employees.

MWH Soft Limited is registered in England with number 6975921. Its registered 
office is Terriers House, 201 Amersham Rd, High Wycombe, HP13 5AJ.

--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] SetupBld - quiet install defaults to passive install

[Jacques Eloff]

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
error dialogs
}
My C++ is very rusty (haven't done any coding in it since 1998), but to me
it seems that removing this line should fix the problem I'm running into at
the moment. I did try a debug version of my modified EXE, but it keeps
exiting with: EXEC : error 0x80070002: Failed to CreateSetup.

Also, I haven't setup NANT yet, so I'm just trying to get the project to
build in VS2008

Thanks,
Jacques



On Thu, Mar 4, 2010 at 3:46 PM, Jacques Eloff  wrote:

> Hi
>
> I create a chained installer using SetupBld using a commandline like the
> one below
>
> setupbld.exe -mi MSI1.msi -mi MSI2.msi -mi MSI3 -title "Foo" -setup
> obj\chained\tempsrc\setup.exe -license docs\EULA.rtf -out MySetup.exe
>
> When I launch the exe using /quiet, I still get a progress bar and the
> installer dialog with the cancel button. From what I can tell, this dialog
> should only appear when launching in passive mode. I've looked at the WiX
> 3.0 sources for setupexe.cpp and found the following when it parses the
> command line arguments
>
> else if (CSTR_EQUAL == ::CompareStringW(LOCALE_INVARIANT,
> NORM_IGNORECASE, &argv[i][1], -1, L"quiet", -1))
> {
> dwUiLevel = INSTALLUILEVEL_NONE;
> }
>
> Based on what I read on MSDN (
> http://msdn.microsoft.com/en-us/library/aa370389(VS.85).aspx),
> INSTALLUILEVEL_NONE is a quiet install
>
> Any idea how I can suppress the progress bars for the UI completely when
> launching the EXE?
>
> Jacques
>
>
>
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] SetupBld - quiet install defaults to passive install

[Jacques Eloff]

Hi

I create a chained installer using SetupBld using a commandline like the one
below

setupbld.exe -mi MSI1.msi -mi MSI2.msi -mi MSI3 -title "Foo" -setup
obj\chained\tempsrc\setup.exe -license docs\EULA.rtf -out MySetup.exe

When I launch the exe using /quiet, I still get a progress bar and the
installer dialog with the cancel button. From what I can tell, this dialog
should only appear when launching in passive mode. I've looked at the WiX
3.0 sources for setupexe.cpp and found the following when it parses the
command line arguments

else if (CSTR_EQUAL == ::CompareStringW(LOCALE_INVARIANT,
NORM_IGNORECASE, &argv[i][1], -1, L"quiet", -1))
{
dwUiLevel = INSTALLUILEVEL_NONE;
}

Based on what I read on MSDN (
http://msdn.microsoft.com/en-us/library/aa370389(VS.85).aspx),
INSTALLUILEVEL_NONE is a quiet install

Any idea how I can suppress the progress bars for the UI completely when
launching the EXE?

Jacques
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld diagnosing?

[Pally Sandher]

Use a LaunchCondition in your MSI to detect for .NET 3.5 SP1 and deny
installation if it's not present. See
http://wix.sourceforge.net/manual-wix3/check_for_dotnet.htm

Also the following page may be of use to you if you're trying to create
a bootstrapper to install .NET 3.5 SP1 before running your MSI ->
http://wix.sourceforge.net/manual-wix3/install_dotnet.htm

Both the above pages are also in the WiX.chm installed with the WiX v3.0
& v3.5 toolsets.

Personally I use dotnetinstaller (http://dotnetinstaller.codeplex.com/)
for my bootstrapper needs as I find it is very powerful but also very
simple to understand and configure the behaviour you require. However
you may find something like ClickOnce or Setupbld suits your needs.
Until Burn (WiX v3.5 toolset bootstrapper) is finished you'll need to
look outside of the WiX toolset to fulfil your bootstrapper
requirements.


Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, 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:
> 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 refuses to run
if it is not installed. I need trigger the .NET setup in that case. 
There are also a couple of other installs that need to be run before
mine.

I'm under the impression that I need a bootstrapper for these things,
but don't fully understand how these things work yet.




--
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld diagnosing?

[JKLists]

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 refuses to run 
if it is not installed. I need trigger the .NET setup in that case. 
There are also a couple of other installs that need to be run before mine.

I'm under the impression that I need a bootstrapper for these things, 
but don't fully understand how these things work yet.



--
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld diagnosing?

[John L Krupka]

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 
> unless SP1 is installed. I understand that this needs to be done in a 
> bootstrapper. However, after a couple of hours of reading on the 
> Internet and experimenting, I'm feeling like I'm not getting anywhere.
> 
> So... I tried something simple, to use setupbld to wrap a test MSI. When 
> I run the created setup.exe either from the command line or by 
> double-clicking on it, nothing seems to happen. Is there debugging 
> information for the created setup.exe?
> 
> Here's the command line that I use to build:
> 
> PS O:\projects\TestInstall\bin\Debug> setupbld -o setup.exe -msu 
> TestInstall.msi -title "Test Setup.exe" -setup "C:\Program Files\Windows 
> Installer XML v3\bin\setup.exe"
> 
> This is what I see when I run:
> 
> PS O:\projects\TestInstall\bin\Debug> .\setup.exe
> PS O:\projects\TestInstall\bin\Debug>
> 
> In other words, I immediately get back the command prompt.
> 
> 
> --
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing. 
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

-- 
View this message in context: 
http://n2.nabble.com/setupbld-diagnosing-tp4096073p4097434.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] setupbld diagnosing?

[JKLists]

My WiX project has a handful of prerequisites, for example, the 
application requires .NET 3.5 SP1. My WiX project correctly does not run 
unless SP1 is installed. I understand that this needs to be done in a 
bootstrapper. However, after a couple of hours of reading on the 
Internet and experimenting, I'm feeling like I'm not getting anywhere.

So... I tried something simple, to use setupbld to wrap a test MSI. When 
I run the created setup.exe either from the command line or by 
double-clicking on it, nothing seems to happen. Is there debugging 
information for the created setup.exe?

Here's the command line that I use to build:

PS O:\projects\TestInstall\bin\Debug> setupbld -o setup.exe -msu 
TestInstall.msi -title "Test Setup.exe" -setup "C:\Program Files\Windows 
Installer XML v3\bin\setup.exe"

This is what I see when I run:

PS O:\projects\TestInstall\bin\Debug> .\setup.exe
PS O:\projects\TestInstall\bin\Debug>

In other words, I immediately get back the command prompt.


--
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld setup.exe & repair install

[Rob Mensching]

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 warne  wrote:

>
>
>
>
> 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/repair/remove dialog.
>
>
>
> For anyone interested there is a modified version of a tool out there
> called msistuff.exe which comes with another setup.exe stub (your msi is
> added to this as a resource).
>
>
>
> msistuff.exe setup.exe /d MySetup.msi /v 200 /o INSTALLUPD /b MySetup.msi
> /p REINSTALLMODE=omus
>
>
>
> Although similar to SETUPBLD the difference is the /p switch which allows
> you to control MSIEXEC. I read somewhere else this might appear in the next
> version of SETUPBLD whenever.
>
>
>
> I really do hope "Burn" someday sees the light. This I think would be the
> last hurdle before WIX runs over Installshield and the rest.
>
>
>
>
>
>
>
>
> From: warne...@hotmail.com
> To: wix-users@lists.sourceforge.net
> Subject: RE: setupbld setup.exe & repair install
> Date: Mon, 9 Nov 2009 16:13:48 +
>
>
>
> 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 to create a setup.exe from my msi. Using the command:
> SETUPBLD -title "MyApp" -ms MyAppSetup.msi -setup setup.exe -out
> MyAppSetup.exe
> However, I get a strange difference between the exe & msi installer
> version.
> Running the installer with the application already installed:
> with MyAppSetup.msi it shows up the "Change, Repair, Remove" dialog as
> expected.
> with MyAppSetup.exe it proceeds to a repair install and no "Change, Repair,
> Remove" dialog like I got when I ran the msi installer.
> Any ideas why this is so anyone or is this normal ?
> Would be slightly concerned releasing setup.exe showing this behaviour.
> Also, is it possible to add external cabs to my setup.exe using setupbld?
> thanks very much!
>
>
>
> Download Messenger onto your mobile for free. Learn more.
>
>
> New Windows 7: Simplify what you do everyday. Find the right PC for you.
> _
> Got more than one Hotmail account? Save time by linking them together
>  http://clk.atdmt.com/UKM/go/186394591/direct/01/
>
> --
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld setup.exe & repair install

[warne warne]

 

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/repair/remove dialog.

 

For anyone interested there is a modified version of a tool out there called 
msistuff.exe which comes with another setup.exe stub (your msi is added to this 
as a resource).

 

msistuff.exe setup.exe /d MySetup.msi /v 200 /o INSTALLUPD /b MySetup.msi /p 
REINSTALLMODE=omus

 

Although similar to SETUPBLD the difference is the /p switch which allows you 
to control MSIEXEC. I read somewhere else this might appear in the next version 
of SETUPBLD whenever. 

 

I really do hope "Burn" someday sees the light. This I think would be the last 
hurdle before WIX runs over Installshield and the rest.

 

 

 


From: warne...@hotmail.com
To: wix-users@lists.sourceforge.net
Subject: RE: setupbld setup.exe & repair install
Date: Mon, 9 Nov 2009 16:13:48 +



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 to create a setup.exe from my msi. Using the command:
SETUPBLD -title "MyApp" -ms MyAppSetup.msi -setup setup.exe -out MyAppSetup.exe
However, I get a strange difference between the exe & msi installer version.
Running the installer with the application already installed:
with MyAppSetup.msi it shows up the "Change, Repair, Remove" dialog as expected.
with MyAppSetup.exe it proceeds to a repair install and no "Change, Repair, 
Remove" dialog like I got when I ran the msi installer.
Any ideas why this is so anyone or is this normal ? 
Would be slightly concerned releasing setup.exe showing this behaviour.
Also, is it possible to add external cabs to my setup.exe using setupbld?
thanks very much!



Download Messenger onto your mobile for free. Learn more. 


New Windows 7: Simplify what you do everyday. Find the right PC for you.
  
_
Got more than one Hotmail account? Save time by linking them together
 http://clk.atdmt.com/UKM/go/186394591/direct/01/
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld setup.exe & repair install

[warne warne]

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 to create a setup.exe from my msi. Using the command:
SETUPBLD -title "MyApp" -ms MyAppSetup.msi -setup setup.exe -out MyAppSetup.exe
However, I get a strange difference between the exe & msi installer version.
Running the installer with the application already installed:
with MyAppSetup.msi it shows up the "Change, Repair, Remove" dialog as expected.
with MyAppSetup.exe it proceeds to a repair install and no "Change, Repair, 
Remove" dialog like I got when I ran the msi installer.
Any ideas why this is so anyone or is this normal ? 
Would be slightly concerned releasing setup.exe showing this behaviour.
Also, is it possible to add external cabs to my setup.exe using setupbld?
thanks very much!



Download Messenger onto your mobile for free. Learn more.   
  
_
New Windows 7: Simplify what you do everyday. Find the right PC for you.
http://www.microsoft.com/uk/windows/buy/
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] setupbld setup.exe & repair install

[warne warne]

Hi there,

I am using setupbld to create a setup.exe from my msi. Using the command:

SETUPBLD -title "MyApp" -ms MyAppSetup.msi -setup setup.exe -out MyAppSetup.exe

However, I get a strange difference between the exe & msi installer version.

Running the installer with the application already installed:

with MyAppSetup.msi it shows up the "Change, Repair, Remove" dialog as expected.
with MyAppSetup.exe it proceeds to a repair install and no "Change, Repair, 
Remove" dialog like I got when I ran the msi installer.

Any ideas why this is so anyone or is this normal ? 

Would be slightly concerned releasing setup.exe showing this behaviour.

Also, is it possible to add external cabs to my setup.exe using setupbld?
thanks very much!
  
_
Download Messenger onto your mobile for free
http://clk.atdmt.com/UKM/go/174426567/direct/01/
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld and -bitmap not supported? -title not supported?

[kerberos]

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 admittedly outside of working with C#/.NET
for a bit to get my company going I am clearly a neophyte when it
comes to the ins and outs of the Windows Installer.  :-)

> The icon for SETUP.EXE is defined in the in a .RC (resource compiler) file. 
> What I copy .\inc\wix.rc to into the same directory as setup.rc and changed 
> the name of the file to Wintellect.rc. Opening up setup.rc in a text editor, 
> I change the #include line from wix.rc to Wintellect.rc. In Wintellect.rc, I 
> changed all the values to reflect my information and added a line:
>
> 1 ICON .\Resources\Wintellect.ico

Perfect advice and now my .exe does exactly what I want.  The only
changes I had to make to the above were for:
  - my company name.
  - removing header files from my.rc that weren't needed or relevant.
  - changing names and versions in winver.h, etc.
  - making sure that 'ICON' was enclosed in quotes to ensure that C++
compiler didn't choke on ".." in its provided location.

Again, thanks!

-- 
K

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld and -bitmap not supported? -title not supported?

[John Robbins]

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. :)

The icon for SETUP.EXE is defined in the in a .RC (resource compiler) file. 
What I copy .\inc\wix.rc to into the same directory as setup.rc and changed the 
name of the file to Wintellect.rc. Opening up setup.rc in a text editor, I 
change the #include line from wix.rc to Wintellect.rc. In Wintellect.rc, I 
changed all the values to reflect my information and added a line:

1 ICON .\Resources\Wintellect.ico

That'll have the .EXE to use your icon. I've attached my setup.rc and 
Wintellect.rc. I didn't include the header files that just define the macro 
values needed by Wintellect.rc as that's just standard C preprocessor stuff. 

Hope 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 Installer XML toolset.
>Subject: Re: [WiX-users] setupbld and -bitmap not supported? -title not
>supported?
>
>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.  I
>re-reread your blog and managed to create both release and debug
>versions of setupexe.exe per your instructions.  I copied setupexe.exe
>to my stubs directory and ran with an argument of -setup
>Stubs\setupexe.exe to test setupbld against my newly-generated build
>of setupexe.exe.  That worked fine.
>
>Now the question is: per your instructions how do I define a custom
>title and icon?  I'm looking at wixver.h, WixDistribution.h and
>setup.RC and I'm not seeing any #define that would explicitly allow me
>to define an icon or title for my .exe.
>
>What am I missing?  I'm sure it's something trivial.  Thanks again for
>your response and excellent tutorial!
>
>--
>K
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld and -bitmap not supported? -title not supported?

[kerberos]

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.  I
re-reread your blog and managed to create both release and debug
versions of setupexe.exe per your instructions.  I copied setupexe.exe
to my stubs directory and ran with an argument of -setup
Stubs\setupexe.exe to test setupbld against my newly-generated build
of setupexe.exe.  That worked fine.

Now the question is: per your instructions how do I define a custom
title and icon?  I'm looking at wixver.h, WixDistribution.h and
setup.RC and I'm not seeing any #define that would explicitly allow me
to define an icon or title for my .exe.

What am I missing?  I'm sure it's something trivial.  Thanks again for
your response and excellent tutorial!

-- 
K

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld and -bitmap not supported? -title not supported?

[kerberos]

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 entry.

However, I still don't see my title or bitmap image when I run the
following command:

  C:\My Product>setupbld -title "My Application 1.0.0" -bitmap
Images\some-real.bmp -msu MyInput.msi -out MySetup.exe -setup
Stubs\Setup.exe

Interestingly, it *looks* like setupbld checks that -bitmap (file)
actually exists as setupbld will error out if it doesn't exist.  I
just don't see some-real.bmp appear as the icon for my .exe when I'm
through with setupbld.  I also don't see "My Application 1.0.0" appear
anywhere when I try to install from the .exe.

-- 
K

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld and -bitmap not supported? -title not supported?

[John Robbins]

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...@noopy.org [mailto:kerbe...@noopy.org]
>Sent: Sunday, November 08, 2009 9:12 AM
>To: General discussion for Windows Installer XML toolset.
>Subject: [WiX-users] setupbld and -bitmap not supported? -title not
>supported?
>
>Hello,
>
>I am running the most current stable build of Wix 3.0.  I'm delighted
>with the product on the whole but I've reached a sticking point in
>distributing packages of my product.
>
>Basically, I preferred to have "fancy" electronic packaging for my
>product and as such preferred not to use the default icon for .msi.
>To get around this I decided to wrap my .msi in a .exe file -- as I
>assumed this would allow me to use a custom icon for my package.  I
>grabbed the setup stub for setup.exe from my Wix binaries directory
>and put it in a local Stubs directory; I refer to the stub when I run
>setupbld.exe.
>
>Unfortunately when I follow Jon Torresdal's instructions for using
>setupbld.exe I am unable to either specify a -bitmap or -title.  When
>I specify -title, my setup.exe is built but I cannot run it (nothing
>happens).  When I specify -bitmap, my image does not appear next to
>setup.exe in Explorer.  When I omit -title and just specify -bitmap I
>can run my .exe but I still get the default .msi icon.
>
>Does anyone know what might be wrong or if -bitmap is supported at all?
>
>--
>K
>
>
>--
>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-
>Day
>trial. Simplify your report design, integration and deployment - and
>focus on
>what you do best, core application coding. Discover what's new with
>Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>___
>WiX-users mailing list
>WiX-users@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/wix-users

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] setupbld and -bitmap not supported? -title not supported?

[kerberos]

Hello,

I am running the most current stable build of Wix 3.0.  I'm delighted
with the product on the whole but I've reached a sticking point in
distributing packages of my product.

Basically, I preferred to have "fancy" electronic packaging for my
product and as such preferred not to use the default icon for .msi.
To get around this I decided to wrap my .msi in a .exe file -- as I
assumed this would allow me to use a custom icon for my package.  I
grabbed the setup stub for setup.exe from my Wix binaries directory
and put it in a local Stubs directory; I refer to the stub when I run
setupbld.exe.

Unfortunately when I follow Jon Torresdal's instructions for using
setupbld.exe I am unable to either specify a -bitmap or -title.  When
I specify -title, my setup.exe is built but I cannot run it (nothing
happens).  When I specify -bitmap, my image does not appear next to
setup.exe in Explorer.  When I omit -title and just specify -bitmap I
can run my .exe but I still get the default .msi icon.

Does anyone know what might be wrong or if -bitmap is supported at all?

-- 
K

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Setupbld - bitmap option seems to be ignored (WiX 3.0.5217.0)

[Jacques Eloff]

Hi

I'm using setupbld and the default stub (setup.exe). When I run the command
using the -bitmap switch, the dialog in the EXE that displays the license
has a large option piece of real estate on the left. Is this where the
bitmap is intended to go? I've tried using the bitmaps that's part of the
UIExtension\wixlib in the source distribution. Documentation on setupbld
seem to be limited.

Has anyone managed to get the -bitmap option working?

Thanks,
Jacques
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld bootstrapper & 64bit

[Frédéric Viollet]

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 be able to install the embedded x64 MSI.
>>
>> Am I right?
>>   
>> 
>
> Yes or at least, I'm not aware of any bugs that would prevent it. MSI 
> has both 32-bit and 64-bit install engines.
>
>   
Ok. Thank you very much for your help.
I'll try this out.

Fred

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld bootstrapper & 64bit

[Bob Arnson]

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 x64 MSI.
>
> Am I right?
>   

Yes or at least, I'm not aware of any bugs that would prevent it. MSI 
has both 32-bit and 64-bit install engines.

-- 
sig://boB
http://joyofsetup.com/



--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld bootstrapper & 64bit

[Frédéric Viollet]

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.
>
>   
>> -will setupbld.exe build 64bit executables? If not, could this be a 
>> problem in installing a 64bit product? Can a 32bit bootstrapper 
>> install 64bit products?
>> 
>
> No, no, yes. This all assumes you're talking x64, not IA64.
>   
Thanks for your reply. I am indeed talking about x64 components.
So to be sure I'm not getting mixed up, let me summarize:
-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 x64 MSI.

Am I right?
Thanks again for your help.

Fred

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld bootstrapper & 64bit

[Bob Arnson]

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, could this be a 
> problem in installing a 64bit product? Can a 32bit bootstrapper 
> install 64bit products?

No, no, yes. This all assumes you're talking x64, not IA64.

-- 
sig://boB
http://joyofsetup.com/



--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] setupbld bootstrapper & 64bit

[Frédéric Viollet]

Hi,

I'm currently using setupbld (in Wix V3) as a bootstrapper for managing 
my product upgrades.
My team is willing to build a native 64 product. Compilation will be 
done on a 64 bit OS.

My questions are :
-do I have to install the 64bit version of Wix? I guess not...the 32bit 
version should still be working... am I right?
-will setupbld.exe build 64bit executables? If not, could this be a 
problem in installing a 64bit product? Can a 32bit bootstrapper install 
64bit products?


Thanks for your help.

Fred
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] SetupBld and IIs Problem

[Rob Mensching]

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 and IIs Problem

Rob, I think, you are right. The problem does not occur in WiX 3.0.4827.0.
So I will try to open a bug. Be warned ;-)

Kind regards and many thanks for your help,
Uwe

-Ursprüngliche Nachricht-
Von: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Gesendet: Donnerstag, 29. Januar 2009 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 repro with older builds then please open a bug 
with as much information as possible (especially the info below).

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 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 message box: "The feature you are trying to use is on a network resource 
that is unavailable. Click OK to try again, or enter an alternate path to a 
folder containing the installation package 'IIsInstallerProblem.msi' in the box 
below."  doesn't  appear.

I don't know if this is ok. What's your opinion?

I don't know why I need the switch in this case (reference to IIsExtensions) 
but in the other cases (without IIsExtensions) not.
("Resolving source" between -Action ended 09:17:40: CommitMetabaseTransaction 
and -Action start 09:18:35: ConfigureIIsExec.)

Many thanks to Bob, he gave me a good starting point ("Check a verbose log to 
see what resource MSI is looking for from the original database").

Kind regards,
Uwe

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] SetupBld and IIs Problem

[Uwe Stump]

Rob, I think, you are right. The problem does not occur in WiX 3.0.4827.0.
So I will try to open a bug. Be warned ;-)

Kind regards and many thanks for your help,
Uwe

-Ursprüngliche Nachricht-
Von: Rob Mensching [mailto:rob.mensch...@microsoft.com] 
Gesendet: Donnerstag, 29. Januar 2009 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 repro with older builds then please open a bug 
with as much information as possible (especially the info below).

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 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 message box: "The feature you are trying to use is on a network resource 
that is unavailable. Click OK to try again, or enter an alternate path to a 
folder containing the installation package 'IIsInstallerProblem.msi' in the box 
below."  doesn't  appear.

I don't know if this is ok. What's your opinion?

I don't know why I need the switch in this case (reference to IIsExtensions) 
but in the other cases (without IIsExtensions) not.
("Resolving source" between -Action ended 09:17:40: CommitMetabaseTransaction 
and -Action start 09:18:35: ConfigureIIsExec.)

Many thanks to Bob, he gave me a good starting point ("Check a verbose log to 
see what resource MSI is looking for from the original database").

Kind regards,
Uwe

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] SetupBld and IIs Problem

[Bob Arnson]

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
http://joyofsetup.com/



--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] SetupBld and IIs Problem

[Rob Mensching]

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 repro with older builds then please open a bug 
with as much information as possible (especially the info below).

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 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 message box: "The feature you are trying to use is on a network resource 
that is unavailable. Click OK to try again, or enter an alternate path to a 
folder containing the installation package 'IIsInstallerProblem.msi' in the box 
below."  doesn't  appear.

I don't know if this is ok. What's your opinion?

I don't know why I need the switch in this case (reference to IIsExtensions) 
but in the other cases (without IIsExtensions) not.
("Resolving source" between -Action ended 09:17:40: CommitMetabaseTransaction 
and -Action start 09:18:35: ConfigureIIsExec.)

Many thanks to Bob, he gave me a good starting point ("Check a verbose log to 
see what resource MSI is looking for from the original database").

Kind regards,
Uwe

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] SetupBld and IIs Problem

[Uwe Stump]

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 message box: "The feature you are trying to use is on a network resource 
that is unavailable. Click OK to try again, or enter an alternate path to a 
folder containing the installation package 'IIsInstallerProblem.msi' in the box 
below."  doesn't  appear.

I don't know if this is ok. What's your opinion?

I don't know why I need the switch in this case (reference to IIsExtensions) 
but in the other cases (without IIsExtensions) not. 
("Resolving source" between -Action ended 09:17:40: CommitMetabaseTransaction 
and -Action start 09:18:35: ConfigureIIsExec.)

Many thanks to Bob, he gave me a good starting point ("Check a verbose log to 
see what resource MSI is looking for from the original database").

Kind regards, 
Uwe

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] SetupBld and IIs Problem

[Uwe Stump]

 Processing net source list.
MSI (c) (4C:B0) [09:17:44:265]: Note: 1: 1706 2:  3: IIsInstallProblem.msi 
MSI (c) (4C:B0) [09:17:44:280]: SOURCEMGMT: Processing media source list.
MSI (c) (4C:B0) [09:17:44:312]: SOURCEMGMT: Trying media source ;.
MSI (c) (4C:B0) [09:17:44:327]: Note: 1: 1706 2:  3: IIsInstallProblem.msi 
MSI (c) (4C:B0) [09:17:44:343]: SOURCEMGMT: Processing URL source list.
MSI (c) (4C:B0) [09:17:44:390]: Note: 1: 1402 2: UNKNOWN\URL 3: 2 
MSI (c) (4C:B0) [09:17:44:405]: Note: 1: 1706 2: -2147483647 3: 
IIsInstallProblem.msi 
MSI (c) (4C:B0) [09:17:44:437]: Note: 1: 1706 2:  3: IIsInstallProblem.msi 
MSI (s) (0C!4C) [09:18:35:562]: SOURCEMGMT: Failed to resolve source
MSI (s) (0C!4C) [09:18:35:609]: Closing MSIHANDLE (395) of type 790531 for 
thread 4940
MSI (s) (0C!4C) [09:18:35:624]: Closing MSIHANDLE (392) of type 790540 for 
thread 4940
MSI (s) (0C!4C) [09:18:35:640]: Closing MSIHANDLE (394) of type 790531 for 
thread 4940
MSI (s) (0C!4C) [09:18:35:671]: Closing MSIHANDLE (393) of type 790531 for 
thread 4940
MSI (s) (0C!4C) [09:18:35:687]: PROPERTY CHANGE: Adding ConfigureIIsExec 
property. Its value is 
'ConfigureIIs€1€0€0€2€1€0€0€2€1€0€0€2€1€0€0€2€1€0€0€2€1€15€1€DirProperties€1€Access€2€Authorization€2€AnonymousUser_€1€IIsControlledPassword€2€LogVisits€2€Index€2€DefaultDoc€1€AspDetailedError€2€HttpExpires€1€CacheControlMaxAge€2€CacheControlCustom€1€NoCustomError€2€AccessSSLFlags€2€AuthenticationProviders€1€3€IIsWebDirProperties_webclient€513€-2147483648€€0€-2147483648€-2147483648€TextFile1.txt€-2147483648€€-2147483648€€-2147483648€-2147483648€€4€2€1€0€0€2€1€0€0€2€1€12€1€Name€1€Isolation€2€AllowSessions€2€SessionTimeout€2€Buffer€2€ParentPaths€2€DefaultScript€1€ScriptTimeout€2€ServerDebugging€2€ClientDebugging€2€AppPool_€1€Application€1€3€Web
 
Client€2€-2147483648€-2147483648€-2147483648€-2147483648€€-2147483648€-2147483648€-2147483648€€appwebclient€4€2€1€0€0€2€1€18€1€Web€1€Component_€1€Id€1€Description€1€ConnectionTimeout€2€Directory_€1€State€2€Attributes€2€DirProperties_€1€Application_€1€Address€1€IP€1€Port€1€Header€1€Secure€2€Log_€1€ISInstalled€2€ISAction€2€3€DefaultWebSite€€€Default
 We
MSI (s) (0C!4C) [09:18:35:702]: Creating MSIHANDLE (397) of type 790531 for 
thread 4940
MSI (s) (0C!4C) [09:18:35:734]: Closing MSIHANDLE (397) of type 790531 for 
thread 4940
MSI (s) (0C!4C) [09:18:35:749]: Doing action: ConfigureIIsExec
Action start 09:18:35: ConfigureIIsExec.
Action ended 09:18:35: ConfigureIIsExec. Return value 1.
MSI (s) (0C!4C) [09:18:35:812]: PROPERTY CHANGE: Adding WriteMetabaseChanges 
property. Its value is 'ConfigureIIs'.
MSI (s) (0C!4C) [09:18:35:843]: Creating MSIHANDLE (398) of type 790531 for 
thread 4940
MSI (s) (0C!4C) [09:18:35:874]: Closing MSIHANDLE (398) of type 790531 for 
thread 4940
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 [mailto:b...@joyofsetup.com] 
Gesendet: Mittwoch, 28. Januar 2009 19:15
An: General discussion for Windows Installer XML toolset.
Betreff: Re: [WiX-users] SetupBld and IIs Problem

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 enter an alternate path to a folder 
> containing the installation package 'IIsInstallerProblem.msi' in the box 
> below."  If I click the Cancel(!) button the uninstall goes on without any 
> other problems.
>   

Check a verbose log to see what resource MSI is looking for from the 
original database.

-- 
sig://boB
http://joyofsetup.com/



--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] SetupBld and IIs Problem

[Bob Arnson]

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 enter an alternate path to a folder 
> containing the installation package 'IIsInstallerProblem.msi' in the box 
> below."  If I click the Cancel(!) button the uninstall goes on without any 
> other problems.
>   

Check a verbose log to see what resource MSI is looking for from the 
original database.

-- 
sig://boB
http://joyofsetup.com/



--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] SetupBld and IIs Problem

[Uwe Stump]

Hello,

I have created a simple WebSite installation by using WiX. This is my WXS-file.


http://schemas.microsoft.com/wix/2006/wi"; 
xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension";>
   
 

 

 
 

 
 

 

 

   
  

   
   


  
  

  
   

 

 

 

 


 
   


The result of compilation is IIsInstallProblem.msi. Installation and 
uninstallation works fine.

At a next step I added the following lines to my IIsInstallProblem.wixproj:






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 enter an alternate path to a folder 
containing the installation package 'IIsInstallerProblem.msi' in the box 
below."  If I click the Cancel(!) button the uninstall goes on without any 
other problems.

If I uncomment all "iis:..." declarations in my WXS-file (for testing) and wrap 
the MSI-file into an EXE-file everything works fine (only the WebSite is not 
configured naturally). So I think the behavior has something to do with IIS 
extensions or maybe the setup.exe-stub of the WiX-bin-folder?

Can anyone help me to avoid the strange message?

Additional information:
Windows XP SP3
WiX: 3.0.4909.0

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] setupbld scenario

[Alex Ivanoff]

I wonder if setupbld can help us in the following scenario. We have our
own prereq installer that takes care of all application prerequisites
(.NET Framework, C++ runtime, MSXML, etc.). After prereq is done main
application installer executes. We need to be able to pass parameters to
both prereq installer and main app installer. Can I do something like
this with setupbld?

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld, bootstrappers and command line parameters (msicl)

[carlldev]

I've finally had time to look at the code for this and then realised I
couldn't do it because it was written in C (which I don't know). I thought
it was done in C# :(

Oh well, I'll wait for 3.5. Thanks anyway.



Rob Mensching-2 wrote:
> 
> 1.  If you sign the assignment agreement then, yeah, I'd take a change to
> setupbld/setupexe.  Those features are essentially "outside" of WiX v3 so
> we're not being as hardcore about the changes going in, yet.  When you get
> to that stage, please send the patch to wix-devs.
> 
> 2.  My expectation is that WiX v3.5 happens during 2009.  The hope is that
> WiX v3 bugs ramp down hard and so we can spend some focused time on the
> bootstrapper that got cut from WiX v3.0.  Burn (the bootstrapper) was a
> hard cut from WiX v3 but looking at the bug count and stability of the
> core toolset and extensions I think it was worth it.  Currently, the only
> thing in WiX v3.5 is burn development, that's why I hope we can get it to
> RC quality by the end of 2009.  WiX v4 will start sometime 2010 since I
> expect WiX v3.0 to be all done end of 2009.
> 
> An updated 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:39
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] setupbld, bootstrappers and command line
> parameters (msicl)
> 
> 
> Thanks Rob.  I'd be willing to contribute to the project and make the
> change
> if we could include it in v3.0.
> Is that something you might consider? It should only be a small change...
> 
> Out of interest, where does 3.5 fit in the roadmap? I read your post on
> the
> roadmap at
> http://robmensching.com/blog/archive/2008/06/06/Proposed-adjustments-the-WiX-v2-and-WiX-v3-roadmap.aspx
> and there is no clear indication of what 3.5 will contain, nor when it's
> planned for. Or am I missing something?
> 
> 
> Rob Mensching-2 wrote:
>>
>> Yes.  Well, actually, more likely WiX v3.5 with burn will 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-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 before we see a change to this?
>> --
>> View this message in context:
>> http://n2.nabble.com/setupbld%2C-bootstrappers-and-command-line-parameters-%28msicl%29-tp1464124p1581153.html
>> Sent from the wix-users mailing list archive at Nabble.com.
>>
>>
>> -
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the
>> world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>>
>> -
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the
>> world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>>
> 
> --
> View this message in context:
> http://n2.nabble.com/setupbld%2C-bootstrappers-and-command-line-parameters-%28msicl%29-tp1464124p1584601.html
> Sent from the wix-users mailing list archive at Nabble.com.
> 
> 
> -
> This SF.Net email is sponsored by the Mobl

Re: [WiX-users] setupbld, bootstrappers and command line parameters (msicl)

[Rob Mensching]

1.  If you sign the assignment agreement then, yeah, I'd take a change to 
setupbld/setupexe.  Those features are essentially "outside" of WiX v3 so we're 
not being as hardcore about the changes going in, yet.  When you get to that 
stage, please send the patch to wix-devs.

2.  My expectation is that WiX v3.5 happens during 2009.  The hope is that WiX 
v3 bugs ramp down hard and so we can spend some focused time on the 
bootstrapper that got cut from WiX v3.0.  Burn (the bootstrapper) was a hard 
cut from WiX v3 but looking at the bug count and stability of the core toolset 
and extensions I think it was worth it.  Currently, the only thing in WiX v3.5 
is burn development, that's why I hope we can get it to RC quality by the end 
of 2009.  WiX v4 will start sometime 2010 since I expect WiX v3.0 to be all 
done end of 2009.

An updated 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:39
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] setupbld, bootstrappers and command line parameters 
(msicl)


Thanks Rob.  I'd be willing to contribute to the project and make the change
if we could include it in v3.0.
Is that something you might consider? It should only be a small change...

Out of interest, where does 3.5 fit in the roadmap? I read your post on the
roadmap at
http://robmensching.com/blog/archive/2008/06/06/Proposed-adjustments-the-WiX-v2-and-WiX-v3-roadmap.aspx
and there is no clear indication of what 3.5 will contain, nor when it's
planned for. Or am I missing something?


Rob Mensching-2 wrote:
>
> Yes.  Well, actually, more likely WiX v3.5 with burn will 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-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 before we see a change to this?
> --
> View this message in context:
> http://n2.nabble.com/setupbld%2C-bootstrappers-and-command-line-parameters-%28msicl%29-tp1464124p1581153.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>

--
View this message in context: 
http://n2.nabble.com/setupbld%2C-bootstrappers-and-command-line-parameters-%28msicl%29-tp1464124p1584601.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld, bootstrappers and command line parameters (msicl)

[carlldev]

Thanks Rob.  I'd be willing to contribute to the project and make the change
if we could include it in v3.0.
Is that something you might consider? It should only be a small change...

Out of interest, where does 3.5 fit in the roadmap? I read your post on the
roadmap at
http://robmensching.com/blog/archive/2008/06/06/Proposed-adjustments-the-WiX-v2-and-WiX-v3-roadmap.aspx
and there is no clear indication of what 3.5 will contain, nor when it's
planned for. Or am I missing something?


Rob Mensching-2 wrote:
> 
> Yes.  Well, actually, more likely WiX v3.5 with burn will 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-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 before we see a change to this?
> --
> View this message in context:
> http://n2.nabble.com/setupbld%2C-bootstrappers-and-command-line-parameters-%28msicl%29-tp1464124p1581153.html
> Sent from the wix-users mailing list archive at Nabble.com.
> 
> 
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

-- 
View this message in context: 
http://n2.nabble.com/setupbld%2C-bootstrappers-and-command-line-parameters-%28msicl%29-tp1464124p1584601.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld, bootstrappers and command line parameters (msicl)

[Rob Mensching]

Yes.  Well, actually, more likely WiX v3.5 with burn will 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-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 before we see a change to this?
--
View this message in context: 
http://n2.nabble.com/setupbld%2C-bootstrappers-and-command-line-parameters-%28msicl%29-tp1464124p1581153.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld, bootstrappers and command line parameters (msicl)

[carlldev]

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/setupbld%2C-bootstrappers-and-command-line-parameters-%28msicl%29-tp1464124p1581153.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld, bootstrappers and command line parameters (msicl)

[Sébastien Mouren]

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.exe /msicl abc="1 2 3"
>
> and you get a window "Install Error": "The process terminated unexpectedly."
>
> and nothing happens.
>
> Does anyone know how to fix this?
>
> How does one log a bug for WiX. This is quite a serious one as I need the
> bootstrapper to work in production...

I think you could file a bug on SourceForge; here exactly:
http://sourceforge.net/tracker2/?func=browse&group_id=105970&atid=642714

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] setupbld, bootstrappers and command line parameters (msicl)

[carlldev]

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.exe /msicl abc="1 2 3"

and you get a window "Install Error": "The process terminated unexpectedly."

and nothing happens.

Does anyone know how to fix this?

How does one log a bug for WiX. This is quite a serious one as I need the
bootstrapper to work in production...
-- 
View this message in context: 
http://n2.nabble.com/setupbld%2C-bootstrappers-and-command-line-parameters-%28msicl%29-tp1464124p1464124.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] setupbld

[Hotmail]

I cannot get setupbld to work I keep on getting to same error "Failed to
CreateSetup" I followed these instructions :

 

http://blog.torresdal.net/2008/10/06/WiXAndDTFUsingABootstrapperToForceEleva
tedPrivilegesInVista.aspx 

 

any advice?

 

Thanks

 

Jonathan Moore.

 

 

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld/setupexe question

[Tanikella, Rajanikanth (SCR US)]

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, and I simply could not get it
to execute. Eventhough double-clicking the MSP would invoke MSIEXEC
correctly, it did not seem to operate that way when invoked from the
setup.exe.  The same might apply for an MST.
 
The setup.exe writes a pretty handy log file into the extraction folder.
Quite helpful for debugging.
 
Hope it helps.
 
Raj



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Thursday, May 08, 2008 9:47 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] setupbld/setupexe question



I want to embed an msi, transform, and an external cab file into the
setup.exe.  When the setup.exe is run the cab file needs to be extracted
to the same folder as the msi.  Has anyone tried this?  Any hints/tips?

 

  <http://www.clearviewecm.com/> 
The information contained in this email is privileged and confidential 
and is intended solely for the addressee(s). If you are not the intended

recipient, please respond to [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>  then delete 
this email from your system.

 

<>-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] setupbld/setupexe question

[Scott Sam]

I want to embed an msi, transform, and an external cab file into the
setup.exe.  When the setup.exe is run the cab file needs to be extracted
to the same folder as the msi.  Has anyone tried this?  Any hints/tips?

 

   
The information contained in this email is privileged and confidential 
and is intended solely for the addressee(s). If you are not the intended

recipient, please respond to [EMAIL PROTECTED]
  then delete 
this email from your system.

 

<>-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld

[Bob Arnson]

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.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld

[Frédéric Viollet]

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 me to 
>> achieve this?
>
> SetupExe isn't currently configurable for that.
>
Do you know another bootstrapper that would allow me to do this?

Thanks

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld

[Bob Arnson]

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?

SetupExe isn't currently configurable for that.

-- 
sig://boB
http://joyofsetup.com/



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld

[Frédéric Viollet]

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 files for the 
installed components would be upgraded (even if they haven't changed).
  

That's controlled by the settings in REINSTALLMODE.



The REINSTALLMODE options are set by the bootstrapper, aren't they?
I'm using the setupbld bootstrapper with the "mcpsu" options. Does this 
seem correct?


Thanks again.

Fred
  
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?


Thanks again.

Fred

begin:vcard
fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet
n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric
org:Bull, Architect of an Open World (TM);Evidian S.A.
adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France
email;internet:[EMAIL PROTECTED]
title:Software Engineer
tel;work:01 30 80 77 34
url:http://www.evidian.com - http://www.bull.com
version:2.1
end:vcard

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld

[Frédéric Viollet]

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 components would be upgraded (even if they haven't changed).
>
> That's controlled by the settings in REINSTALLMODE.
>
The REINSTALLMODE options are set by the bootstrapper, aren't they?
I'm using the setupbld bootstrapper with the "mcpsu" options. Does this 
seem correct?

Thanks again.

Fred

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld

[Bob Arnson]

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 upgraded (even if they haven't changed).

That's controlled by the settings in REINSTALLMODE.

-- 
sig://boB
http://joyofsetup.com/



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] setupbld

[Frédéric Viollet]

Hi all,

I have a question about the setupbld.exe tool.

I'm using this tool in WixV3 with the mcpsu options and I've noticed 
some strange behaviour.
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 upgraded (even if they haven't changed).
If this is the normal behaviour, is there a way to force all files to be 
upgraded?


By the way, I see that the files have not been updated because the 
timestamps don't change on upgrade... maybe my test is not right.


Thanks for your help.

Fred
begin:vcard
fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet
n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric
org:Bull, Architect of an Open World (TM);Evidian S.A.
adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France
email;internet:[EMAIL PROTECTED]
title:Software Engineer
tel;work:01 30 80 77 34
url:http://www.evidian.com - http://www.bull.com
version:2.1
end:vcard

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] setupbld/setupexe - using both UI and quiet modes

[Bob Arnson]

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/

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] setupbld/setupexe - using both UI and quiet modes

[Hongping Lim]

Hi,

Does the default setup.exe that comes with setupbld.exe support both UI and 
quiet installation (/q) modes in the generated .exe?

For example, currently, to show the UI embedded in the MSIs, I am using the 
following command:
setupbld.exe -mcs MyPackage1.msi -mcs MyPackage2.msi -setup setup.exe -out 
chained.exe

When the user runs "chained.exe", the UI for each MSI is shown as expected. 
However running "chained.exe /q" does not seem to do anything.

If I use just "-mc" when running setupbld, then chained.exe does not show any 
UI, but it shows the progress bar.

Is there a way to get both UI and silent mode installations?

Thanks,
Hongping
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Setupbld produces file but doesn't do anything?

[Bob Arnson]

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 not installed, but if it is already installed, the setup seems to 
just reinstall silently.  Is there something I have to do to get the 
msi change/repair/remove screen using the setup, or is that just not 
supported yet?




If you're using the -ms switch, I'd expect a second setup.exe instance 
to show the maintenance-mode UI in the .msi itself. Setup.exe calls 
MsiInstallProduct which goes through the same path as calling 'msiexec 
/i' (afaik). Do you get different behavior if you drop the other -m 
subswitches?


--
sig://boB
http://joyofsetup.com/

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Setupbld produces file but doesn't do anything?

[Josh Maletz]

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.

 

Leads me to a new question.  The setup works fine if the application is not
installed, but if it is already installed, the setup seems to just reinstall
silently.  Is there something I have to do to get the msi
change/repair/remove screen using the setup, or is that just not supported
yet?

 

Josh

 

  _  

From: Bob Arnson [mailto:[EMAIL PROTECTED] 
Sent: Monday, August 20, 2007 9:13 PM
To: [EMAIL PROTECTED]
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 UI transforms but you aren't supplying any.
That would break it, however. How big is your package? Extracting it might
take a while. I'd suggest starting with ProcMon to see if XsSetup.exe is
doing any i/o.



-- 
sig://boB
http://joyofsetup.com/
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Setupbld produces file but doesn't do anything?

[Bob Arnson]

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 while. I'd suggest starting with ProcMon to see if 
XsSetup.exe is doing any i/o.


--
sig://boB
http://joyofsetup.com/

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Setupbld produces file but doesn't do anything?

[Josh Maletz]

Hi all,

 

I am trying to create a bootstrapper and am having no luck.  I use the
command line utility and it creates the setup file successfully apparently
(at least the file size has greatly increased), but when I run the
XsSetup.exe, it doesn't do anything.

 

I am assuming I am being stupid, but there isn't any documentation and only
4 posts on the mailing list.  I have tried with several different options,
and the file is created but doesn't do anything.  

 

My command line is: 

 

setupbld -out XsSetup.exe -mcst ExtendedServicesSetup.msi -setup setup.exe
-title "Extended Services Setup"

 

Thanks,

 

Josh

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users