[WiX-users] Burn without UI

2012-01-31 Thread Alexander Lamaison
Is it possible to have a bootstrapper made with burn that doesn't show any UI?

All I want my bootstrapper to do is decide what platform it's running
on (x86 or x64), extract the appropriate MSI installer from within
itself and run it.  At the moment, the Burn UI takes over.  Is there a
no-UI option?

Thanks,

Alex

--
Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org)

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Visual C++ 2010 Merge Module

2012-01-31 Thread Joost van Zoest
I've validated my MSM in Orca. At first, I got a lot of ICE33 warnings
because of some COM registration logic. To rule out that this was
causing my problems, I removed this registration logic and validated the
MSM again. Now the validation completes, but ends with:
Execution   ERROR   There is a problem with this Windows Installer
package. A DLL required for this install to complete could not be run.
Contact your support personnel or package vendor.  

I'm using Orca with the darice.cub of WIX 3.6 BETA

Looking further in Orca, I saw 2 tables (ModuleInstallExecuteSequence
and ModuleInstallUISequence) which both contained an action called
AppSearch with a Sequence of 50. I guess the actions of these tables are
moved to the InstallExecuteSequence and InstallUISequence tables when
you embed this merge module into an installer. So could this be the
cause of the warnings I see when I build my installer?

Somewhere in my merge module I perform a registry search to get a
directory from the registry:
Property Id=MYDIRECTORY
  RegistrySearch Id=REG_DirectorySearch Type=raw
Root=HKLM Key=Software\MyApplication Name=InstallDir/
/Property
*MYDIRECTORY is the ID of a Directory element.

When I remove this registry search, the AppSearch actions are also
removed from the 2 tables. And I don't get the warnings anymore when I
build the installer containing this merge module. The original problem,
that a registry key was not written when you run the installer, is also
gone now.

Am I using the RegistrySearch in a correct way? Or is there another way
to fill the Directory element with a value from the registry?



-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Monday, January 30, 2012 1:30 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module

The only reason I asked is because the guid that suffixes the property
names is supposed to be the MSM's Package @Id, and there should be no
reason that your MSM is using another MSMs properties. However, that
appears to be a red herring (the duplicate sequence number warnings
are expected in that scenario). The purpose of the duplicate sequence
warnings is to make you look to ensure that there isn't any sequencing
expectation between the actions being merged. Setting the values of the
system directories doesn't generally have that concern.

The concern I see looking more closely at your build spew is the action
[that] cannot be merged report. Are the names of the actions really
blank
('') or did you remove the action names? If you look at your MSM in Orca
(or other MSI viewer/editor), does it really have entries in the
sequence tables with blank or missing action names? Does your MSM pass
validation by itself?

Blair

-Original Message-
From: Joost van Zoest [mailto:jzo...@siqura.com]
Sent: Monday, January 30, 2012 12:58 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module

If you mean if I've used guids which are also used in the VC MSM, then
no.
I've tested this by generating completely new guids for my merge module,
and still I got the warnings.

Thanks for the idea though, didn't think of this obvious error...

-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Monday, January 30, 2012 9:07 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module

Did you borrow VC's MSM's package guid for your MSM?

This message contains confidential information and is intended only for
the individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system.




--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
This message contains confidential information and is intended only 

Re: [WiX-users] Burn without UI

2012-01-31 Thread jhennessey
Looks like you need to write your own BA: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-bootstrap-a-single-MSI-not-showing-BA-UI-at-all-td6926187.html
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-bootstrap-a-single-MSI-not-showing-BA-UI-at-all-td6926187.html
 

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-without-UI-tp7239834p7239968.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Visual C++ 2010 Merge Module

2012-01-31 Thread Blair

Several action don't seem to be intended to be found in MSMs. Maybe
AppSearch is one of them.

Do you distribute your MSM publically? If not, I've got a couple of ideas.
1) Run a couple of SQL queries against the MSM to remove them from the two
Module*Sequence tables. 2) Change from using MSMs and instead
generate/consume WixLibs instead.

If you do distribute MSMs publically then each idea I have has limitations.

-Original Message-
From: Joost van Zoest [mailto:jzo...@siqura.com] 
Sent: Tuesday, January 31, 2012 6:41 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module

I've validated my MSM in Orca. At first, I got a lot of ICE33 warnings
because of some COM registration logic. To rule out that this was causing my
problems, I removed this registration logic and validated the MSM again. Now
the validation completes, but ends with:
Execution   ERROR   There is a problem with this Windows Installer
package. A DLL required for this install to complete could not be run.
Contact your support personnel or package vendor.  

I'm using Orca with the darice.cub of WIX 3.6 BETA

Looking further in Orca, I saw 2 tables (ModuleInstallExecuteSequence and
ModuleInstallUISequence) which both contained an action called AppSearch
with a Sequence of 50. I guess the actions of these tables are moved to the
InstallExecuteSequence and InstallUISequence tables when you embed this
merge module into an installer. So could this be the cause of the warnings I
see when I build my installer?

Somewhere in my merge module I perform a registry search to get a directory
from the registry:
Property Id=MYDIRECTORY
  RegistrySearch Id=REG_DirectorySearch Type=raw
Root=HKLM Key=Software\MyApplication Name=InstallDir/ /Property
*MYDIRECTORY is the ID of a Directory element.

When I remove this registry search, the AppSearch actions are also removed
from the 2 tables. And I don't get the warnings anymore when I build the
installer containing this merge module. The original problem, that a
registry key was not written when you run the installer, is also gone now.

Am I using the RegistrySearch in a correct way? Or is there another way to
fill the Directory element with a value from the registry?



-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Monday, January 30, 2012 1:30 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module

The only reason I asked is because the guid that suffixes the property names
is supposed to be the MSM's Package @Id, and there should be no reason that
your MSM is using another MSMs properties. However, that appears to be a red
herring (the duplicate sequence number warnings are expected in that
scenario). The purpose of the duplicate sequence warnings is to make you
look to ensure that there isn't any sequencing expectation between the
actions being merged. Setting the values of the system directories doesn't
generally have that concern.

The concern I see looking more closely at your build spew is the action
[that] cannot be merged report. Are the names of the actions really blank
('') or did you remove the action names? If you look at your MSM in Orca (or
other MSI viewer/editor), does it really have entries in the sequence tables
with blank or missing action names? Does your MSM pass validation by itself?

Blair

-Original Message-
From: Joost van Zoest [mailto:jzo...@siqura.com]
Sent: Monday, January 30, 2012 12:58 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module

If you mean if I've used guids which are also used in the VC MSM, then no.
I've tested this by generating completely new guids for my merge module, and
still I got the warnings.

Thanks for the idea though, didn't think of this obvious error...

-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Monday, January 30, 2012 9:07 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module

Did you borrow VC's MSM's package guid for your MSM?

This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and delete
this e-mail from your system.




--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers is
just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro
Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net

Re: [WiX-users] Burn without UI

2012-01-31 Thread Alexander Lamaison
On 31 January 2012 15:07, jhennessey jack.hennes...@hyland.com wrote:
 Looks like you need to write your own BA:
 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-bootstrap-a-single-MSI-not-showing-BA-UI-at-all-td6926187.html

Is this hard to do?  Can it be done in C++ or must I use .net?  Can
you point me to something to get me started (I've searched online and
in the source but can't find anything)?

Thanks,

Alex

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Burn without UI

2012-01-31 Thread Bob Arnson
On 31-Jan-12 09:12, Alexander Lamaison wrote:
 Is it possible to have a bootstrapper made with burn that doesn't show any UI?
The WixStdBA supports the /silent switch for no-UI installations.

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


--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Burn without UI

2012-01-31 Thread jhennessey
You can do it in native or managed code. 

Take a look at the burn solution file in the source (src\burn\burn.sln). You
can see both the wixstdba (native) and WixBA (managed) projects for
examples. I haven't come across any tutorials or anything like that though.

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-without-UI-tp7239834p7240469.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Burn without UI

2012-01-31 Thread Bruce Cran
On 31/01/2012 15:37, Alexander Lamaison wrote:
 Is this hard to do?  Can it be done in C++ or must I use .net?  Can
 you point me to something to get me started (I've searched online and
 in the source but can't find anything)?

Fortunately you can use C++. I certainly don't like the idea of 
requiring customers to install .NET on platforms such as Server 2008 or 
Hyper-V Server just so they can run my installer to install a native 
application :)

-- 
Bruce Cran

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Burn without UI

2012-01-31 Thread Dieter Lunn
Even with a managed bootstrapper you don't need .NET installed
initially if I remember correctly.

Dieter Lunn
http://ubiety.ca



On Tue, Jan 31, 2012 at 1:00 PM, Bruce Cran br...@cran.org.uk wrote:
 On 31/01/2012 15:37, Alexander Lamaison wrote:
 Is this hard to do?  Can it be done in C++ or must I use .net?  Can
 you point me to something to get me started (I've searched online and
 in the source but can't find anything)?

 Fortunately you can use C++. I certainly don't like the idea of
 requiring customers to install .NET on platforms such as Server 2008 or
 Hyper-V Server just so they can run my installer to install a native
 application :)

 --
 Bruce Cran

 --
 Keep Your Developer Skills Current with LearnDevNow!
 The most comprehensive online learning library for Microsoft developers
 is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
 Metro Style Apps, more. Free future releases when you subscribe now!
 http://p.sf.net/sfu/learndevnow-d2d
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Burn without UI

2012-01-31 Thread Bruce Cran
On 31/01/2012 19:14, Dieter Lunn wrote:
 Even with a managed bootstrapper you don't need .NET installed
 initially if I remember correctly.

That's right - Burn will bootstrap .NET first. But I just don't like the 
idea of requiring extra software to be installed just for the installer.

-- 
Bruce Cran

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Burn without UI

2012-01-31 Thread Bruce Cran
On 31/01/2012 20:02, Bruce Cran wrote:
 On 31/01/2012 19:14, Dieter Lunn wrote:
 Even with a managed bootstrapper you don't need .NET installed
 initially if I remember correctly.
 That's right - Burn will bootstrap .NET first. But I just don't like the
 idea of requiring extra software to be installed just for the installer.


Server 2008 Core doesn't even support the .NET Framework at all. From 
http://msdn.microsoft.com/en-us/library/ff770052%28v=winembedded.60%29.aspx 
:

Server Core for Windows Server 2008 does not support any version of the 
.NET Framework.

That page also suggests that trying to install .NET by running the 
redistributable will fail on Server Core installations, and that you 
have to install it as a feature instead.

-- 
Bruce Cran

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Burn - Moving payload to Cache Directory

2012-01-31 Thread Romeo S.
It seems I can't reproduce it anymore.

Thanks

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Moving-payload-to-Cache-Directory-tp7237441p7241383.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Single Add/Remove icon

2012-01-31 Thread Alexander Lamaison
My burn bootstrapper/bundle/thingiemagig is just a wrapper around my
MSI installer; it chooses between an x86 and an x64 version but will
only ever install one.  So I just want one entry for my program in
Add/Remove programs.

I seem to have achieved this by removing the Name attribute from the
Bundle tag but is this the right way?  It seems a bit odd.

Thanks,

Alex

--
Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org)

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Single Add/Remove icon

2012-01-31 Thread Dieter Lunn
Put the following line in your Package:

Property Id=ARPSYSTEMCOMPONENT Value=1 /

It will tell MSI not to include it in Add/Remove Programs.

Dieter Lunn
http://ubiety.ca



On Tue, Jan 31, 2012 at 7:02 PM, Alexander Lamaison sw...@lammy.co.uk wrote:
 My burn bootstrapper/bundle/thingiemagig is just a wrapper around my
 MSI installer; it chooses between an x86 and an x64 version but will
 only ever install one.  So I just want one entry for my program in
 Add/Remove programs.

 I seem to have achieved this by removing the Name attribute from the
 Bundle tag but is this the right way?  It seems a bit odd.

 Thanks,

 Alex

 --
 Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org)

 --
 Keep Your Developer Skills Current with LearnDevNow!
 The most comprehensive online learning library for Microsoft developers
 is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
 Metro Style Apps, more. Free future releases when you subscribe now!
 http://p.sf.net/sfu/learndevnow-d2d
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] msp patch does not update one of files

2012-01-31 Thread Sergey
This behaviour is not stable. When I removed everything and repeated 
test again - file patched. This makes me frightened that on some 
clients' machines patch will work ok, but on some will fail. It is the 
worst variant, when I can not reproduce bug on my PC.

30.01.2012 21:46, Wilson, Phil пишет:
 And in the verbose log, see if there are any SELMGR entries. They indicate 
 that you've broken component rules during a patch by deleting a component. 
 Otherwise look at the log to see what it says about that particular file and 
 why it didn't replace it.

 Phil W

 -Original Message-
 From: Fyodor Koryazhkin [mailto:fyodor...@gmail.com]
 Sent: Sunday, January 29, 2012 12:11 AM
 To: wix-users@lists.sourceforge.net
 Subject: [WiX-users] msp patch does not update one of files

 Hi,
 To find out why file is not being updated you can do the following:
 1. Examine log file.
 2. Apply patch to the target image at design time:
 a. Open target image in ORCA
 b. Open Transforms -  View Patch
 c. All changed tables, rows and columns will be marked in green rectangle
 d. Check version, sequence and language for suspicious file.

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users