from:"Tobias S"

ICE validation needs an interactive account or Admin privileges to be
happy. See e.g.
http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/11/14/wix-projects-vs-tfs-2010-team-build.aspx
or http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg34102.html

2011/2/18 Peter Solomon pe...@nextsteps.co.za:
I solved this by adding the continuous integration service account
into the 'Domain Admin' group.

Kind regards

---
Peter Solomon

On Fri, Feb 18, 2011 at 10:57 AM, Peter Solomon pe...@nextsteps.co.za wrote:
Hi There,

I'm wondering if someone else has also experienced the same problem
when using Cruise Control to build there project - see error below

Everything build fine in VS 2008.

I've got Wix 3.5.2519.0 installed on Windows Server 2008 R2.

Would someone be able to point me in the correct direction?

light.exe (0,0):

errorLGHT0217: Error executing ICE action 'ICE01'.
The most common
cause of this kind of ICE failure is an incorrectly registered
scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for
details and how to solve this problem. The following string format was
not expected by the external UI message logger: The Windows Installer
Service could not be accessed. This can occur if the Windows Installer
is not correctly installed. Contact your support personnel for
assistance..
light.exe (0,0):

errorLGHT0217: Error executing ICE action 'ICE02'.
The most common
cause of this kind of ICE failure is an incorrectly registered
scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for
details and how to solve this problem. The following string format was
not expected by the external UI message logger: The Windows Installer
Service could not be accessed. This can occur if the Windows Installer
is not correctly installed. Contact your support personnel for
assistance..
light.exe (0,0):

errorLGHT0217: Error executing ICE action 'ICE03'.
The most common
cause of this kind of ICE failure is an incorrectly registered
scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for
details and how to solve this problem. The following string format was
not expected by the external UI message logger: The Windows Installer
Service could not be accessed. This can occur if the Windows Installer
is not correctly installed. Contact your support personnel for
assistance..
light.exe (0,0):

errorLGHT0217: Error executing ICE action 'ICE04'.
The most common
cause of this kind of ICE failure is an incorrectly registered
scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for
details and how to solve this problem. The following string format was
not expected by the external UI message logger: The Windows Installer
Service could not be accessed. This can occur if the Windows Installer
is not correctly installed. Contact your support personnel for
assistance..
light.exe (0,0):

errorLGHT0217: Error executing ICE action 'ICE05'.
The most common
cause of this kind of ICE failure is an incorrectly registered
scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for
details and how to solve this problem. The following string format was
not expected by the external UI message logger: The Windows Installer
Service could not be accessed. This can occur if the Windows Installer
is not correctly installed. Contact your support personnel for
assistance..
light.exe (0,0):

errorLGHT0217: Error executing ICE action 'ICE06'.
The most common
cause of this kind of ICE failure is an incorrectly registered
scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for
details and how to solve this problem. The following string format was
not expected by the external UI message logger: The Windows Installer
Service could not be accessed. This can occur if the Windows Installer
is not correctly installed. Contact your support personnel for
assistance..
light.exe (0,0):

errorLGHT0217: Error executing ICE action 'ICE07'.
The most common
cause of this kind of ICE failure is an incorrectly registered
scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for
details and how to solve this problem. The following string format was
not expected by the external UI message logger: The Windows Installer
Service could not be accessed. This can occur if the Windows Installer
is not correctly installed. Contact your support personnel for
assistance..
light.exe (0,0):

errorLGHT0216: An unexpected Win32 exception with
error code 0x643
occurred: Action - 'ICE08' Fatal error during installation

---
Peter Solomon

Re: [WiX-users] 2 Queries for WIX Evaluation

1. You need Burn (Beta state in Wix 3.6), DotNetInstaller, MSI Factory
Bootstrapper Generator or VS2008 (2010) bootstrapper for WiX

2. Possible in WiX by modifying integrated dialogs (comp.
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm ),
also with help of SharpDevelop in a version 3.2.1 or 4.0.1.7090 and
higher (available here http://build.sharpdevelop.net/buildartefacts/)
possible

3. Not possible in MSI itself. So custom bootstrapper to fulfill that
requirement needed. Burn e.g. will offer functionality for that in WiX
3.6 (not sure about the proxy configuration, I'd assume it will take
Internet Explorere settings), VS Bootstrapper has afaik such
functionality at least when not considering needs for a proxy


Regards
Tobias




2011/2/18 Ritz ritz.1...@gmail.com:
 Dear Team



 I am evaluating WiX, NSIS  Inno Setup, VS2008 Setup for my deployment
 scenario.



 I have the following scenario for deployment -

 1.       Bootstrapper for Pre-Requisites
 Available in VS 2008

 2.       Custom UI for Customer Data
 Available in VS 2008(Restricted UI Set)

 3.       Online File Downloading
 Not Available in VS2008



 My Query is about point 2's ease  3's support majorly.

 Does WiX support Online File Downloading during installation. Are there any
 plugins available for that ?

 If yes, does it have Proxy Support ?



 Thanks

 Ritz

 --
 The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
 Pinpoint memory and threading errors before they happen.
 Find and fix more than 250 security defects in the development cycle.
 Locate bottlenecks in serial and parallel code that limit performance.
 http://p.sf.net/sfu/intel-dev2devfeb
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Dynamically set WixVariable WixUILicenseRtf

You have to overwrite the default WiX dialog e.g. in WixUI_InstallDir
with a modified LicenseAgreementDlg.wxs:

1.) get the WiX Source code


2.) from there add copies from
src\ext\UIExtension\wixlib\WixUI_InstallDir.wxs +
LicenseAgreementDlg.wxs to your solution renamed as
MyLicenseAgreementDlg.wxs + MyWixUI_InstallDir.wxs


3.) MyLicenseAgreementDlg.wxs
change lines
Dialog Id=LicenseAgreementDlg Width=370 Height=270
Title=!(loc.LicenseAgreementDlg_Title)
--
Dialog Id=MyLicenseAgreementDlg Width=370 Height=270
Title=!(loc.LicenseAgreementDlg_Title)



Control Id=LicenseText Type=ScrollableText X=20 Y=60
Width=330 Height=140 Sunken=yes TabSkip=no
   Text SourceFile=!(wix.WixUILicenseRtf=$(var.licenseRtf)) /
/Control

--

Control Id=LicenseText Type=ScrollableText X=20 Y=60
Width=330 Height=140 Sunken=yes TabSkip=no
   Text SourceFile=!(loc.LicenseRtf) /
/Control


4.) WixUI_InstallDir.wxs
change line
 UI Id=WixUI_InstallDir
--
 UI Id=MyWixUI_InstallDir

Replace all four occurences of LicenseAgreementDlg with MyLicenseAgreementDlg


5.) Change in the main wxs the reference to the modified MyWixUI_InstallDir
UIRef Id=WixUI_InstallDir/
--
UIRef Id=MyWixUI_InstallDir/


6.) Add for every language a localization file with at least the
following content:
?xml version=1.0 encoding=utf-8?
WixLocalization Culture=en-US
xmlns=http://schemas.microsoft.com/wix/2006/localization;
  String Id=Language1033/String
  String Id=LicenseRtfLanguages\EnglishLicenseAgreement.rtf/String
/WixLocalization


Here LicenseRtf is the location of the localized License Agreement


Regards
Tobias


2011/2/18 Michael Tissington michael_tissing...@ciqual.com:
 How can I dynamically set the value of WixUILicenseRtf?

 I have tried WixVariable Id=WixUILicenseRtf Value=[PROPERTY_NAME]/

 What I'm trying to do is for each localization to use a different license.rtf.


 --
 The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
 Pinpoint memory and threading errors before they happen.
 Find and fix more than 250 security defects in the development cycle.
 Locate bottlenecks in serial and parallel code that limit performance.
 http://p.sf.net/sfu/intel-dev2devfeb
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Dynamically set WixVariable WixUILicenseRtf

Ok, knew there exists an english speaking tutorial:
http://weblogs.sqlteam.com/mladenp/archive/2010/04/15/WiX-3-Tutorial-Custom-EULA-License-and-MSI-localization.aspx

2011/2/18 Tobias S tobias.s1...@gmail.com:
 You have to overwrite the default WiX dialog e.g. in WixUI_InstallDir
 with a modified LicenseAgreementDlg.wxs:

 1.) get the WiX Source code


 2.) from there add copies from
 src\ext\UIExtension\wixlib\WixUI_InstallDir.wxs +
 LicenseAgreementDlg.wxs to your solution renamed as
 MyLicenseAgreementDlg.wxs + MyWixUI_InstallDir.wxs


 3.) MyLicenseAgreementDlg.wxs
 change lines
 Dialog Id=LicenseAgreementDlg Width=370 Height=270
 Title=!(loc.LicenseAgreementDlg_Title)
 --
 Dialog Id=MyLicenseAgreementDlg Width=370 Height=270
 Title=!(loc.LicenseAgreementDlg_Title)



 Control Id=LicenseText Type=ScrollableText X=20 Y=60
 Width=330 Height=140 Sunken=yes TabSkip=no
   Text SourceFile=!(wix.WixUILicenseRtf=$(var.licenseRtf)) /
 /Control

 --

 Control Id=LicenseText Type=ScrollableText X=20 Y=60
 Width=330 Height=140 Sunken=yes TabSkip=no
   Text SourceFile=!(loc.LicenseRtf) /
 /Control


 4.) WixUI_InstallDir.wxs
 change line
  UI Id=WixUI_InstallDir
 --
  UI Id=MyWixUI_InstallDir

 Replace all four occurences of LicenseAgreementDlg with MyLicenseAgreementDlg


 5.) Change in the main wxs the reference to the modified MyWixUI_InstallDir
 UIRef Id=WixUI_InstallDir/
 --
 UIRef Id=MyWixUI_InstallDir/


 6.) Add for every language a localization file with at least the
 following content:
 ?xml version=1.0 encoding=utf-8?
 WixLocalization Culture=en-US
 xmlns=http://schemas.microsoft.com/wix/2006/localization;
  String Id=Language1033/String
  String Id=LicenseRtfLanguages\EnglishLicenseAgreement.rtf/String
 /WixLocalization


 Here LicenseRtf is the location of the localized License Agreement


 Regards
 Tobias


 2011/2/18 Michael Tissington michael_tissing...@ciqual.com:
 How can I dynamically set the value of WixUILicenseRtf?

 I have tried WixVariable Id=WixUILicenseRtf Value=[PROPERTY_NAME]/

 What I'm trying to do is for each localization to use a different 
 license.rtf.


 --
 The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
 Pinpoint memory and threading errors before they happen.
 Find and fix more than 250 security defects in the development cycle.
 Locate bottlenecks in serial and parallel code that limit performance.
 http://p.sf.net/sfu/intel-dev2devfeb
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users



--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] heat: the ID of a directory with numeric name

2011-02-21 Thread Tobias S

You can use the -t:xsl (transform harvested output with XSL file)
parameter to use a XSL-transform. A sample XSLT can be found here:
http://www.wixwiki.com/index.php?title=Heat or search this mailing
list e.g. at http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/
for some samples. Additionally XMLspy has a good debugger to track the
modifications an XSLT is doing on a XML file.

Regards
Tobias

2011/2/21  samuel.feren...@barclayscapital.com:
 Hi,

 I guess this question is for me rather than for Palbinder.

 I am running heat 3.0.5419.0. And I do use -suid (on purpose).

 Anyway, this is not critical, I was just wondering if there was a good 
 explanation for the ID change from Directory1234 to _1234, but I can live 
 with it.

 Thanks a lot,
 Sam

 ---
 Date: Thu, 17 Feb 2011 08:59:39 -0800
 From: Brian Rogers rogers.br...@gmail.com
 Subject: Re: [WiX-users] heat: the ID of a directory with numeric name
 To: General discussion for Windows Installer XML toolset.
        wix-users@lists.sourceforge.net
 Message-ID:
        AANLkTinsPkGfV=P=j6x+m2-zg0olr7_nxhugukqq8...@mail.gmail.com
 Content-Type: text/plain; charset=ISO-8859-1

 Hey Palbinder,

 Which version of heat.exe are you using? As long as you aren't using -suid
 you should be ok.

 Thanks,

 Brian Rogers
 Intelligence removes complexity. - Me
 http://blogs.msdn.com/icumove


 On Thu, Feb 17, 2011 at 2:10 AM, samuel.feren...@barclayscapital.comwrote:

 Hi Palbinder, (group),

 thanks for your response.

 As per the link you said, an ID of 1234 is *not* acceptable (every
 identifier must begin with either a letter or an underscore), which is why
 I think heat does some magic to avoid that ID for a directory called 1234.

 It seems that in one case heat generates the ID Directory1234 and in
 another _1234, and I'm wondering if this is something that one can control
 in heat (or if, perhaps, this is due to different versions of heat...)

 Thanks,
 Sam

 -Original Message-
 From: Pally Sandher [mailto:pally.sand...@iesve.com]
 Sent: 11 February 2011 17:32
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] heat: the ID of a directory with numeric name

 Directory ID's can be anything you like as long as they're valid
 identifiers (see http://msdn.microsoft.com/en-gb/library/aa369212.aspx)
 since they go directly into the Directory table. They don't need to
 reflect the actual name of the directory.

 Just rename it after harvesting.

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

 http://www.iesve.com
 **Design, Simulate + Innovate with the Virtual Environment**
 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: samuel.feren...@barclayscapital.com
 [mailto:samuel.feren...@barclayscapital.com]
 Sent: 11 February 2011 14:05
 To: wix-users@lists.sourceforge.net
 Subject: [WiX-users] heat: the ID of a directory with numeric name

 Hi,

 I am harvesting (heat dir) a directory structure like this:

 foo
 + bar
   + 1234
      + a.a
      + b.b

 The output is as follows:

        DirectoryRef Id=TARGETDIR
            Directory Id=foo Name=foo
                Directory Id=bar Name=bar
                    Directory Id=_1234 Name=1234

 I am wondering about the Id _1234. I suppose the Id cannot be purely
 numeric, so the underscore is prepended.

 However, I'm trying to mimic another MSI package, and that one has the
 Id of Directory1234:

        DirectoryRef Id=TARGETDIR
            Directory Id=foo Name=foo
                Directory Id=bar Name=bar
                    Directory Id=Directory1234 Name=1234

 How can that be achieved?

 Thanks,
 Sam
 ___

 This e-mail may contain information that is confidential, privileged or 
 otherwise protected from disclosure. If you are not an intended recipient of 
 this e-mail, do not duplicate or redistribute it by any means. Please delete 
 it and any attachments and notify the sender that you have received it in 
 error. Unless specifically indicated, this e-mail is not an offer to buy or 
 sell or a solicitation to buy or sell any securities, investment products or 
 other financial product or service, an official confirmation of any 
 transaction, or an official statement of Barclays. Any views or opinions 
 presented are solely those of the author and do not necessarily represent 
 those of Barclays. This e-mail is subject to terms available at the following 
 link: www.barcap.com/emaildisclaimer. By messaging with Barclays you consent 
 to the foregoing.  Barclays Capital is the investment banking division of 
 Barclays Bank PLC, a company registered in England (number 1026167) with its 
 registered office at 1 Churchill Place, London, E14 5HP.  This email may 
 relate to or be sent from other

Re: [WiX-users] Setup can't install drivers via DIFXApp.

2011-02-24 Thread Tobias S

Hi,

Think there is no way to directly do that as the Difxapp has, as you
stated already, no element for that.

I'd check the issue what is going wrong with the device driver instead
of Resume on error. Do you have e.g. the correct files integrated in
the Installation ? Once I had such an issue where I had the wrong
directory structure in the installation which was different from the
in the inf file defined one.

Regards
Tobias


2011/2/24 Sergey Yukhno sergey.yuk...@visutechsystem.by:
 Hi,

 Setup can't install driver via DIFXApp and installation process stopped
 with error.
 How to just show error message and continue. Difxapp element doesn't
 have necessary option.

 Sergey Yukhno.

 --
 Free Software Download: Index, Search  Analyze Logs and other IT data in
 Real-Time with Splunk. Collect, index and harness all the fast moving IT data
 generated by your applications, servers and devices whether physical, virtual
 or in the cloud. Deliver compliance at lower cost and gain new business
 insights. http://p.sf.net/sfu/splunk-dev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Free Software Download: Index, Search  Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Running a third party installer

2011-02-25 Thread Tobias S

Without deeper knowign the issue: Are you trying to run an MSI from
another one ? If yes: Not recommended! The only workaround is to abuse
the InstallUI sequence for such an approach. This fails e.g. if user
runs installer without UI! A short fragment to illustrate such an
approach:

CustomAction Id=Install_MSI Impersonate=yes Execute=immediate
Directory=WindowsFolder ExeCommand=msiexec.exe /i
quot;c:\MyMSIpackage.msiquot; /qb Return=ignore /
InstallUISequence
Custom Action=Install_MSI After=ProgressDlgNot 
Installed/Custom
/InstallUISequence

But to emphasis it again. Not recommended by MSDN but to be honest I
do a similat approach as well e.g. for deploying the VCRedists.


Regards
Tobias



2011/2/25 Samudra Vishvajith vishv...@gmail.com:
 Hi,

 In our WIX installer,
 a third party installer (postgresql server installer) is run as a custom
 action

 the third party installer starts and the following error message pops up.

 Another program is being installed. Please wait until that installation is
 complete, and then try installing this software again

 Any idea why this happens?

 --
 Vishva
 --
 Free Software Download: Index, Search  Analyze Logs and other IT data in
 Real-Time with Splunk. Collect, index and harness all the fast moving IT data
 generated by your applications, servers and devices whether physical, virtual
 or in the cloud. Deliver compliance at lower cost and gain new business
 insights. http://p.sf.net/sfu/splunk-dev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Free Software Download: Index, Search  Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Running a third party installer

2011-02-25 Thread Tobias S

Just as additional information if you want to run several MSIs: For
sure a bootstrapper or chainer application to do so would be the
recommended solution.
Tobias


2011/2/25 Tobias S tobias.s1...@gmail.com:
 Without deeper knowign the issue: Are you trying to run an MSI from
 another one ? If yes: Not recommended! The only workaround is to abuse
 the InstallUI sequence for such an approach. This fails e.g. if user
 runs installer without UI! A short fragment to illustrate such an
 approach:

 CustomAction Id=Install_MSI Impersonate=yes Execute=immediate
 Directory=WindowsFolder ExeCommand=msiexec.exe /i
 quot;c:\MyMSIpackage.msiquot; /qb Return=ignore /
        InstallUISequence
                Custom Action=Install_MSI After=ProgressDlgNot 
 Installed/Custom
        /InstallUISequence

 But to emphasis it again. Not recommended by MSDN but to be honest I
 do a similat approach as well e.g. for deploying the VCRedists.


 Regards
 Tobias



 2011/2/25 Samudra Vishvajith vishv...@gmail.com:
 Hi,

 In our WIX installer,
 a third party installer (postgresql server installer) is run as a custom
 action

 the third party installer starts and the following error message pops up.

 Another program is being installed. Please wait until that installation is
 complete, and then try installing this software again

 Any idea why this happens?

 --
 Vishva
 --
 Free Software Download: Index, Search  Analyze Logs and other IT data in
 Real-Time with Splunk. Collect, index and harness all the fast moving IT data
 generated by your applications, servers and devices whether physical, virtual
 or in the cloud. Deliver compliance at lower cost and gain new business
 insights. http://p.sf.net/sfu/splunk-dev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users



--
Free Software Download: Index, Search  Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Installation path of Adobe/Return a value from aCustomAction

2011-03-05 Thread Tobias S

Not sure whether you mean the Acrobat Reader or another Acrobat
product. If it's the reader did you think of finding the default
application for pdf files ? This can be archived with a CA by
traversing the reg keys


string defaultApplication =
(string)Registry.GetValue(@HKEY_CLASSES_ROOT\.PDF, , );
string regValue = HKEY_CLASSES_ROOT\\ +
defaultApplication + \\shell\\open\\command;
defaultApplication = (string)Registry.GetValue(@regValue, , );


Afterwards check if default app exists and cut filename from full path
+ filename. In my understanding this should work as long as the PDF
reader is registered correctly on the system, nevertheless if it's a
Acrobat, FoxIt or some other one. For Foxit I know that it writes keys
not during install but after first starting of the application.



2011/3/4 David Watson dwat...@sdl.com:
 I don't think the version key that you are using is very reliable, I don't
 have it on my machine but I do have the InstallPath.

 Msdn states that the reglocator key column is of the type regPath which is
 formatted so properties should be usable, but I don't think you can guarantee
 the search order to allow you to use one registry searches results from
 another. Also the wix docs say RegistrySearch@Key is a string so it may not
 be formatted from wix.

 You could of course try a FileSearch based on the ProgramFiles folder.

 The other way of doing it is to have several registry searches for each
 acrobat version that you support (I recall us doing something like this a
 while ago to search for Word).

 Oh and another thing to note is that you are reading type raw which will add
 a # to the beginning of some data types found so if the version is an actual
 number that would be wrong.

 Also your second search's type should be directory.

 You can set a property inside your custom action and a property can be used
 as a directory ID.



 -Original Message-
 From: bradley.jo...@thomsonreuters.com
 [mailto:bradley.jo...@thomsonreuters.com]
 Sent: 04 March 2011 15:52
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] Installation path of Adobe/Return a value from
 aCustomAction

 I'm able to copy a file using the custom action, letting the Custom
 Action (in this case an .exe) handle the entire process.

 I'm still wondering if there's a way to use the Property Id's and
 Registry Search to handle this.

 What is the best practice for determining an installation path that
 could be different based on what is installed on the users machine?  In
 this case a version of Adobe.

 Thanks for any suggestions.

 Brad

 -Original Message-
 From: Jones, Bradley (TA WSS)
 Sent: Wednesday, March 02, 2011 4:59 PM
 To: WiX-users@lists.sourceforge.net
 Subject: [WiX-users] Installation path of Adobe/Return a value from a
 CustomAction

 I'm looking for the best way to find a version of Adobe that's installed
 on a user's machine.  This will determine the installation path of some
 files to deploy.



 I've tried the following:



    Property Id=ACROBAT_VERSION

      RegistrySearch

        Id=Acrobat_Version

        Root=HKLM

        Key=SOFTWARE\Classes\AcroExch.Document\AcrobatVersion

        Type=raw/

    /Property



    Property Id=ACROBATPATH

      RegistrySearch

        Id=AcrobatPath

        Root=HKLM

        Key=HKEY_CURRENT_USER\Software\Adobe\Adobe
 Acrobat\VERSION\InstallPath

        Type=raw/

    /Property



 The issue I have here is depending on what version the user has
 installed, VERSION changes.



 Is there a way to pass a Property Id to part of the key, for example:

 HKEY_CURRENT_USER\Software\Adobe\Adobe
 Acrobat\[ACROBAT_VERSION]\InstallPath



 The above does not work, but was wondering if there's a way to
 accomplish this?



 I also thought of going the route of a custom action, I've written an
 exe that returns the path to Adobe.

 I've written an .exe and called from a custom action:  If there's a way,
 what is the syntax to return a value from a custom action?



 Can a Custom action return a value that I can pass to a Directory or use
 as a DirectoryRef?



    DirectoryRef Id=PROPERTYRETURNEDFROMCUSTOMACTION

        Component Id=FindAdobeLocation.exe Guid=GUID HERE

          File Id=FindAdobeLocation.exe Source=SourceLocation
 KeyPath=yes Checksum=yes /

        /Component

      /DirectoryRef







 Thanks for any suggestions.



 Brad

 
 --
 Free Software Download: Index, Search  Analyze Logs and other IT data
 in
 Real-Time with Splunk. Collect, index and harness all the fast moving IT
 data
 generated by your applications, servers and devices whether physical,
 virtual
 or in the cloud. Deliver compliance at lower cost and gain new business
 insights. http://p.sf.net/sfu/splunk-dev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net

Re: [WiX-users] How to read binary file content using c#custom action???

2011-03-05 Thread Tobias S

Alternatively you can use the BinaryWrite CA from
http://msiext.codeplex.com/ to extract binaries from a binary stream

http://code.dblock.org/Source/msiext/1.2/Docs/_msi_binary_8h.html#ae1b642e8fa3ad62c069a7a76eb90f688
should be the direct link to the CA documentation.

DTF should have some functionality to process  binary streams. As I
assume you are german speaking did you consider Andreas Kerl Inside
Windows Installer 4.5 chapter 4 Deployment Tools Foundation or his
code samples available at http://www.microsoft-press.de/ . They are a
good intorduction when starting coding in DTF. But I'm not sure
whether he discusses binary streams.

Alternatively check out WiX sources and their good code samples esp.
src\DTF\Samples\ManagedCASampleCAs.cs below
session.Log(Testing record stream extraction...);


Regards
Tobias



2011/3/4 Dan Vasilov d...@rms.ro:
        You may want to take a look at
 http://blogs.msdn.com/b/icumove/archive/2009/06/23/custom-action-using-wix-r
 eading-from-the-binary-table.aspx.
        Also http://www.installsite.org/pages/en/msi/ca.htm lists an example
  Streaming a File From the Binary Table.

        'if the size of the file allows' = if you only have to read a 6KB
 file and you are sure this size will not greatly increase in the future,
 then you can safely use File.ReadAllBytes, knowing your code does not risk
 allocating a large byte array. Otherwise, you have to plan the file reading
 strategy (like creating a buffer and iteratively reading in this buffer
 until you have processed all data from the file).




 -Original Message-
 From: Simon Chromow [mailto:simon.chro...@bewotec.de]
 Sent: Friday, March 04, 2011 3:35 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] How to read binary file content using c#custom
 action???

 What I don't understand, is how to get the file from the binary table.
 Could you give me an example?
 What means 'if the size of the file allows' ?
 Is there a maximum file size for this?

 Windows Explorer says the file has 6KB.

 -Ursprüngliche Nachricht-
 Von: Dan Vasilov [mailto:d...@rms.ro]
 Gesendet: Freitag, 4. März 2011 13:29
 An: 'General discussion for Windows Installer XML toolset.'
 Betreff: Re: [WiX-users] How to read binary file content using c#custom
 action???

        In .NET you will use a BinaryReader or File.ReadAllBytes, if the
 size of the file allows. Does this answer your question?

 Dan


 -Original Message-
 From: Simon Chromow [mailto:simon.chro...@bewotec.de]
 Sent: Friday, March 04, 2011 1:05 PM
 To: wix-users@lists.sourceforge.net
 Subject: [WiX-users] How to read binary file content using c# custom
 action???

 Hi wix-users,

 Does anybody know,

 how to read content from a specific binary file using a c# custom-action?



 Thanks for your efforts

 Simon

 
 --
 What You Don't Know About Data Connectivity CAN Hurt You This paper provides
 an overview of data connectivity, details its effect on application quality,
 and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


 
 --
 What You Don't Know About Data Connectivity CAN Hurt You This paper provides
 an overview of data connectivity, details its effect on application quality,
 and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

 
 --
 What You Don't Know About Data Connectivity CAN Hurt You
 This paper provides an overview of data connectivity, details
 its effect on application quality, and explores various alternative
 solutions. http://p.sf.net/sfu/progress-d2d
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


 --
 What You Don't Know About Data Connectivity CAN Hurt You
 This paper provides an overview of data connectivity, details
 its effect on application quality, and explores various alternative
 solutions. http://p.sf.net/sfu/progress-d2d
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application

Re: [WiX-users] Using a file from media in a custom action.

2011-03-08 Thread Tobias S

Some construct referencing the corresponding File ID (Here quick 
dirty for a MSI DLL) ?
 CustomAction Id=NewCustomAction1 FileKey=twain_32.dll DllEntry=test /


2011/3/8 Mark Tempel mark.tem...@shavlik.com:
 I'm trying to avoid including the file in the binary table because it is an
 extra 900K added to a 6.5Meg installer.

 It is a dll that I need to unpack and explicitly load from a custom action.
  The action will be run before files are copied to the install directory
 (where this dll will have to live for the product).

 I was hoping someone here know how to get this file out of the cab and into
 a temp directory from a custom action.

 Thanks for the suggestion though.

 --mark

 Mark Tempel
 Sr Software Engineer
 Shavlik Technologies LLC.

 On Mon, Mar 7, 2011 at 3:58 PM, Wilson, Phil phil.wil...@invensys.comwrote:

 There is a type of custom action (resolves to type 18 and variations) that
 specifically means run this exe being installed with the product as a custom
 action. As long as you want to run it after the files are installed that's
 fine, but I suspect you wouldn't be asking if that was the situation.

 It's ok to put it in the Binary table if you need it before that, as long
 as it has no dependency issues and isn't enormously bloated. Why is
 including it twice a bad thing?

 Phil Wilson


 -Original Message-
 From: Mark Tempel [mailto:mark.tem...@shavlik.com]
 Sent: Monday, March 07, 2011 11:23 AM
 To: wix-users@lists.sourceforge.net
 Subject: [WiX-users] Using a file from media in a custom action.

 Hello,

 I am in a situation where I need to use a file in a custom action that I am
 also laying down as part of the file set stored in the cab build into my
 MSI.

 Is there a way to get that file out of the cab from a custom action?  I
 know
 I can include the file in the binaries table, but that would mean I'm
 including it in my installer twice.  I'd like to avoid that.

 Thanks,

 Mark Tempel
 Sr. Software Engineer
 Shavlik Technologies LLC.

 --
 What You Don't Know About Data Connectivity CAN Hurt You
 This paper provides an overview of data connectivity, details
 its effect on application quality, and explores various alternative
 solutions. http://p.sf.net/sfu/progress-d2d
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


 *** Confidentiality Notice: This e-mail, including any associated or
 attached files, is intended solely for the individual or entity to which it
 is addressed. This e-mail is confidential and may well also be legally
 privileged. If you have received it in error, you are on notice of its
 status. Please notify the sender immediately by reply e-mail and then delete
 this message from your system. Please do not copy it or use it for any
 purposes, or disclose its contents to any other person. This email comes
 from a division of the Invensys Group, owned by Invensys plc, which is a
 company registered in England and Wales with its registered office at 3rd
 Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For
 a list of European legal entities within the Invensys Group, please go to
 http://www.invensys.com/legal/default.asp?top_nav_id=77nav_id=80prev_id=77
 .

 You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
 recept...@invensys.com. This e-mail and any attachments thereto may be
 subject to the terms of any agreements between Invensys (and/or its
 subsidiaries and affiliates) and the recipient (and/or its subsidiaries and
 affiliates).




 --
 What You Don't Know About Data Connectivity CAN Hurt You
 This paper provides an overview of data connectivity, details
 its effect on application quality, and explores various alternative
 solutions. http://p.sf.net/sfu/progress-d2d
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

 --
 What You Don't Know About Data Connectivity CAN Hurt You
 This paper provides an overview of data connectivity, details
 its effect on application quality, and explores various alternative
 solutions. http://p.sf.net/sfu/progress-d2d
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
___

Re: [WiX-users] I want the next button to be disabled if Entire feature will be unavailable is selected in a feature tree.

2011-03-08 Thread Tobias S

Afaik not possible the way you are planing it. Just did a test with
modifying the NEXT button on a CustomizeDlg with following code:
Control Id=Next Type=PushButton X=236 Y=243 Width=56
Height=17 Default=yes Text=!(loc.WixUINext)
Subscribe Event=SelectionNoItems Attribute=Enabled /
  Condition Action=enable![CDATA[(Feature1 
2)]]/Condition
  Condition Action=disable![CDATA[(Feature1 
3)]]/Condition
/Control

Right now it refreshes the button state when disabling the feature
click back and click next again. But this is not the desired behavior.
Reading the post here
See also http://forum.installsite.net/index.php?showtopic=2337

indicates that there seems no exacct solution to the problem. Add a
condition to the next button showing an error in case nothing was
selected and proceeding in case something was selected.

Regards
Tobias


2011/3/7 santhosh yalamuri santhu_...@yahoo.co.in:
 Hi,
     I have a simple installer which has only one feature,I want the next 
 button to be disabled if Entire feature will be unavailable is selected in 
 a feature tree.
 Thanks

 --
 What You Don't Know About Data Connectivity CAN Hurt You
 This paper provides an overview of data connectivity, details
 its effect on application quality, and explores various alternative
 solutions. http://p.sf.net/sfu/progress-d2d
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] how to include Component Win64 in heat.exe result.

2011-03-08 Thread Tobias S

Think there is no direct flag. Use a xslt to transform the generated
file instead. In http://www.wixwiki.com/index.php?title=Heat there
exists a sample how to do so.

Best regards
Tobias



2011/3/8 Thai-Hoa Nguyen taiwa...@hotmail.com:

 When running heat.exe, what flag do I use to turn on the Component Win64 
 attribute?  Thank you.
 --
 What You Don't Know About Data Connectivity CAN Hurt You
 This paper provides an overview of data connectivity, details
 its effect on application quality, and explores various alternative
 solutions. http://p.sf.net/sfu/progress-d2d
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Multilanguage install

2011-03-12 Thread Tobias S

Hi, Just did a build with the same things in our build environment.
The two MSIs differ only in (except language string)  Product Language
Property (1033 and 1040). The transform then is created with Torch.exe
-t Language en-US\SetupProject.msi it-IT\SetupProject.msi -out
en-US\it-IT.mst. Did you use the -t Language parameter here ?

 I then created a transform between my 1033 and 1040 and embedded it into the
 1033 with a name of 1040
 I then set the Languages in the Summary Info to '1033,1040'

Never did it the way as described in
http://www.installsite.org/pages/en/msi/articles/embeddedlang/index.htm
. But at first glance the way you tried it seems similar to the
described way.

What happens if you build the italian and english package and
afterwards create the transform as described above and apply it to the
english package in the form
msiexec /i SetupProject.msi TRANSFORMS=it-IT.mst
?



2011/3/11 Michael Tissington michael_tissing...@ciqual.com:
 Hi I'm having problems with creating an msi that works for different locals.
 Below is an extract from the log file

 I have created an msi for each language, changing the Language in the
 Product element to 1033 and 1040

 I can run both the 1033 and 1040 msi on the machine and they display the
 correct language

 I then created a transform between my 1033 and 1040 and embedded it into the
 1033 with a name of 1040
 I then set the Languages in the Summary Info to '1033,1040'

 I change my regional settings and  then try to run the resulting msi and it
 fails.

 Any ideas what I've missed please?


 -
 MSI (c) (F4:94) [15:30:26:256]: APPCOMPAT: looking for appcompat database
 entry with ProductCode '{15FA6484-DB24-460C-97D5-89CA132144D7}'.
 MSI (c) (F4:94) [15:30:26:256]: APPCOMPAT: no matching ProductCode found in
 database.
 MSI (c) (F4:94) [15:30:26:271]: MSCOREE not loaded loading copy from
 system32
 MSI (c) (F4:94) [15:30:26:271]: Machine policy value 'TransformsSecure' is 0
 MSI (c) (F4:94) [15:30:26:271]: User policy value 'TransformsAtSource' is 0
 MSI (c) (F4:94) [15:30:26:271]: Machine policy value 'DisablePatch' is 0
 MSI (c) (F4:94) [15:30:26:271]: Machine policy value 'AllowLockdownPatch' is
 0
 MSI (c) (F4:94) [15:30:26:271]: Machine policy value 'DisableLUAPatching' is
 0
 MSI (c) (F4:94) [15:30:26:271]: Machine policy value
 'DisableFlyWeightPatching' is 0
 MSI (c) (F4:94) [15:30:26:271]: Looking for storage transform: 1040
 MSI (c) (F4:94) [15:30:26:271]: Validating transform '1040' with validation
 bits 0x1
 MSI (c) (F4:94) [15:30:26:271]: Note: 1: 2745 2: 1040 3:
 C:\DOCUME~1\ADMINI~1\IMPOST~1\Temp\d6082c.msi 4: 1033 5: 1040
 MSI (c) (F4:94) [15:30:26:271]: 1: 2745 2: 1040 3:
 C:\DOCUME~1\ADMINI~1\IMPOST~1\Temp\d6082c.msi 4: 1033 5: 1040
 MSI (c) (F4:94) [15:30:26:271]: Note: 1: 2729
 DEBUG: Error 2745:  Transform 1040 invalid for package
 C:\DOCUME~1\ADMINI~1\IMPOST~1\Temp\d6082c.msi. Expected language 1033, found
 language 1040.
 1: 2745 2: 1040 3: C:\DOCUME~1\ADMINI~1\IMPOST~1\Temp\d6082c.msi 4: 1033 5:
 1040
 Errore nell'applicazione dei trasformatori. Verificare che i percorsi dei
 trasformatori specificati siano validi.
 1040
 MSI (c) (F4:94) [15:30:26:271]: Note: 1: 1708
 MSI (c) (F4:94) [15:30:26:271]: Note: 1: 2729
 MSI (c) (F4:94) [15:30:26:271]: Note: 1: 2729
 MSI (c) (F4:94) [15:30:26:271]: Product: Session Insight -- Installation
 failed.


 --
 Colocation vs. Managed Hosting
 A question and answer guide to determining the best fit
 for your organization - today and in the future.
 http://p.sf.net/sfu/internap-sfd2d
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Multifeature filetype association

2011-03-15 Thread Tobias S

Maybe some words to good sources. Unfortunately for the english
speaking community they are all written in German. Andreas Kerl wrote
several good books about Windows Installer. See
http://www.installsite.biz/de/buecher.htm (German!) for an overview.
There also the english speaking books for Windows Installer are
mentioned.

For Inside Windows Installer 4.5 he discusses in one chapter WiX and
in another DTF. Additionally he wrote several articles for the German
DotNetPro. But as already mentioned they are only available in German.


2011/3/15 Pally Sandher pally.sand...@iesve.com:
 Here is the best place for WiX help. The actual WiX dev's such as Rob M,
 Bob A et al reply on a regular basis if other learned members haven't
 responded to a query. We also have people like Phil Wilson whom I
 believe (although he's never confirmed) wrote The definitive guide to
 Windows Installer which is a pretty damn good book in my opinion.

 In your Feature B component which registers the filetype(s) you can
 simply use [#executable] for the TargetProperty field which will expand
 to the full path of your executable when installed. That is assuming
 what you're referring to as features A, B  C are Features in the
 Windows Installer sense all within the same MSI Package (the
 stackoverflow thread refers to plug-in installers).

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

 http://www.iesve.com
 **Design, Simulate + Innovate with the Virtual Environment**
 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: The Eligible Bachelors [mailto:theeligiblebachel...@yahoo.com]
 Sent: 14 March 2011 20:10
 To: wix-users@lists.sourceforge.net
 Subject: [WiX-users] Multifeature filetype association

 First of all what is the best resource for getting help with advanced
 WiX topics? A book or mailing list will do. I have been mostly using
 stackoverflow.

 And now for my question. I have an installer with features A, B
 (optional) and C (optional).

 Feature A is an executable and B and C are DLLs that add support to the
 executable for additional filetypes.

 If I install B, I would like to associate the appropriate filetype to
 the exec installed in A.

 Right now I am working off the solution here:
 http://stackoverflow.com/questions/4787085/wix-plugin-installer-needs-to
 -reference-primary-installation

 But there are several complications. When you search through a component
 for a file, does it indicate if it is installed? And if it does, does it
 have to be installed in a previous run of the installer?

 Or should I have it search the filesystem to see if the exec is
 installed. And then does order of installation matter?




 
 --
 Colocation vs. Managed Hosting
 A question and answer guide to determining the best fit for your
 organization - today and in the future.
 http://p.sf.net/sfu/internap-sfd2d
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users



 --
 Colocation vs. Managed Hosting
 A question and answer guide to determining the best fit
 for your organization - today and in the future.
 http://p.sf.net/sfu/internap-sfd2d
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Is it Possible: Dialog Box Text Edit Control with Wrapped Text?

Hi,

Assume this is a limitation of textbox element in Windows Installer
(comp. e.g.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/multiline-edit-control-type-td4176815.html
).

The only point to ensure a better usability here from my point of view
would be to make the edit wider
Control Id=DatabaseConnectionParamsInput Type=Edit X=9 Y=82
Width=351 Height=15 Property=DBCONNECTION_STRING TabSkip=no
Multiline=yes

Text{32767}sadfsaddfsdfasfsadfsfs asdf asdf
asd fasd f
sdf sdf sadf sda fas fsd fsd fg sadfasdf sadfsd/Text

/Control

or make the whole Windows Installer dialog containing this input form
wider. Additionally you could e.g. create a C# DTF Custom Action to
retrieve such a property in a wider dialog.

Regards
Tobias

2011/3/15 Robert Buck buck.rober...@gmail.com:
Hello,

I'd like to have a text control in a installer dialog that allows
input of a database connection string. The database connection string
can be rather long, so rather than have its text flow off into the
nether world, I'd like to make the text box taller and have the text
automatically wrap so the entire string is visible WITHOUT having to
scroll horizontally (which is a big usability issue for me).

Control Id=DatabaseConnectionParamsInput Type=Edit
X=150 Y=85 Width=180 Height=75 Property=DBCONNECTION_STRING
TabSkip=no Multiline=yes
Text{32767}sadfsaddfsdfasfsadfsfs asdf asdf asd fasd f sdf
sdf sadf sda fas fsd fsd fg sadfasdf sadfsd/Text
/Control

Problem is, no matter what I seem to try the text keeps flowing
horizonally off the box rather than wrapping.

Is there a way to make a text entry box that wraps as a single line of text?

Thanks in advance,

Bob

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Multilanguage install

Hi Francesco,

Here some information to your questions

RTL (Right to left language support in WiX) which you need for arabic
(and hebrew)
WiX by default: Uses default left to right for these languages.
Otherwise you must redesign all dialogs to the new layout which is not
done by default. Assume this needs some effort to do so and do a good
layout for these dialogs. Here it depends on how important these
lanugages appear (in fact it is only arabic and hebrew for the WiX
languages). In tramontana some effort for a custom script was done to
do so. See http://www.tramontana.co.hu/wix/loc/index.php in section
(tfeL ot thgiR).

For the localization approach described on InstallSite. First of all I
don't prefer it as there is e.g. no ability for a Select Language
dialog. Also I want to emphasis that this is an undocumented feature!
I got a short test working as described on InstallSite
(http://www.installsite.org/pages/en/msi/articles/embeddedlang/index.htm)
:

For 1. and 2.) I created a MSI (Setup.msi) and a german MST (de-DE.mst).

For 3.) I embedded the Transform with
wisubstg.vbs Setup.msi de-DE.mst 1031

For 4.) This was a bit tricky. First I tried
cscript WiLangId.vbs Setup.msi Package 1033,1031. Then I got an error
Error applying transforms. Verify that the specified transform paths
are valid. So I did the settings using Orca (View - Summary
Information... - there changed Laanguages to 1033,1031 and saved the
package afterwards)

This should work. If you don't get it working what then happens when
only applying the transform ?
( msiexec /i setup.msi TRANSFORMS=de-DE.mst )

Regards
Tobias

2011/3/17 Francisco Gabriel Malbrán fgmalb...@gmail.com:
Hello Wix users. This is my first time around. I've been playing for a while
now and after lots
of do not write to the list stupid questions before you think they are not
stupid anymore I think
I really need your help.
All related to localization of course. I separate the original question in
two:

A) How can I make the multilanguague work?? (I'm trying hard, I swear)

Can you please explain in more detail how did you manage to make this work?

I am using WiX 3.5 in Windows 7 and I just can't find a way to make my msi
file autodetect
the language of the OS. It always starts in the default language, english.

I've tried a lot of things, for example:
- http://www.codeproject.com/KB/install/WixWindowsInstallerDemo3.aspx
-
http://www.geektieguy.com/2010/03/13/create-a-multi-lingual-multi-language-msi-using-wix-and-custom-build-scripts/
- things explained in this book:
http://my.safaribooksonline.com/book/-/9781849513722/localizing-your-installer/ch12lvl1sec06(of
course, the complete version)
- my own mixed versions of all I read in different places.
- more

Michael, can you explain what you say at the end, about changing the
SummaryInfo properties?
did you simply use the script as referenced in
http://www.installsite.org/pages/en/msi/articles/embeddedlang/index.htm?

I used the Windows 7 SDK script

cscript.exe utils\WiLangId.vbs installer.msi Package 1033,1034

then open the .msi with Orca and search for 1034. I get nothing. (Not to say
that obviusly, the
installer still launches in english in my spanish OS.

B) Does WiX offer some way of Mirroring the user interface? For example,
suppose I want my
installer to be localized to arabic or some language that is read from right
to left. How can I make
the interface inverted so text are correctly aligned and images are shown in
a mirrored fashion?
(or for example, other images are shown instead of the traditionals).

If you help me with this I will be the happiest guy ever. I'm telling you,
this is driving me crazy!

Thanks in advance.

From: Michael Tissington michael_tissington@ci... - 2011-03-14 14:18

Thanks - I was using a script to create the transform but when I use torch
it works great :)

-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: 12 March 2011 13:07
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Multilanguage install

Hi, Just did a build with the same things in our build environment.
The two MSIs differ only in (except language string) Product Language
Property (1033 and 1040). The transform then is created with Torch.exe -t
Language en-US\SetupProject.msi it-IT\SetupProject.msi -out
en-US\it-IT.mst. Did you use the -t Language parameter here ?

I then created a transform between my 1033 and 1040 and embedded it
into the
1033 with a name of 1040
I then set the Languages in the Summary Info to '1033,1040'

Never did it the way as described
inhttp://www.installsite.org/pages/en/msi/articles/embeddedlang/index.htm
. But at first glance the way you tried it seems similar to the described
way.

What happens if you build the italian and english package and afterwards
create the transform as described above and apply it to the english package
in the form msiexec /i

Re: [WiX-users] Multilanguage install

For the storing in the MSI package:

When diffing it with InstED (unfortuanelty IS2010 and MSIDiff seem not
being able to show it) you can see a substorage element (_Storages)
where the german transform is stored in.

Regards
Tobias

2011/3/17 Tobias S tobias.s1...@gmail.com:
Hi Francesco,

Here some information to your questions

For 1. and 2.) I created a MSI (Setup.msi) and a german MST (de-DE.mst).

For 3.) I embedded the Transform with
wisubstg.vbs Setup.msi de-DE.mst 1031

This should work. If you don't get it working what then happens when
only applying the transform ?
( msiexec /i setup.msi TRANSFORMS=de-DE.mst )

Regards
Tobias

A) How can I make the multilanguague work?? (I'm trying hard, I swear)

Can you please explain in more detail how did you manage to make this work?

I am using WiX 3.5 in Windows 7 and I just can't find a way to make my msi
file autodetect
the language of the OS. It always starts in the default language, english.

I used the Windows 7 SDK script

cscript.exe utils\WiLangId.vbs installer.msi Package 1033,1034

then open the .msi with Orca and search for 1034. I get nothing. (Not to say
that obviusly, the
installer still launches in english in my spanish OS.

If you help me with this I will be the happiest guy ever. I'm telling you,
this is driving me crazy!

Thanks in advance.

From: Michael Tissington michael_tissington@ci... - 2011-03-14 14:18

Thanks - I was using a script to create the transform but when I use torch
it works great :)

-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: 12 March 2011 13:07
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Multilanguage install

I then created a transform between my 1033 and 1040 and embedded it
into the
1033 with a name of 1040
I then set the Languages in the Summary Info to '1033,1040'

Never did it the way as described
inhttp

Re: [WiX-users] Multilanguage install

Francisco,

When you get it working with the transform msiexec /i installer.msi
TRANSFORMS=:1034. (I'm wondering about the :1034 - should be e.g.
1034.mst???) this means it is working with your produced spanish
transform applied to the english one. So when going back to
InstallSite your problems can result in problems in step 3. or 4. .

In general and why I don't like this approach very much: you must rely
on the way here this undocumented feature retrieves the current OS
language. If something goes wrong here it is difficult to track down
the real issue. So did you try the package on several spanish systems
?

Btw: Spanish if I remember right this is the OS where the LCID is 1034
and additionally other LCIDs exist. Maybe that causes problems in
detecting a spanish OS with these embedded transforms. Read
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/LCIDs-of-the-supported-languages-of-WixUIExtension-tp5910168p5910168.html
So maybe use some other language first to track down the problem and
set the OS language as described in InstallSite.

I'd recommend you to use e.g. German and 1031 for your testing. Please
do exactly following:
1. Build the MSI + transform
2. test it with msiexec /i setup.msi TRANSFORMS=1031.mst

If working
3. embed the transform with
wisubstg.vbs Setup.msi 1031.mst 1031

4. ORCA: View - Summary Information... - there change Languages to
1033,1031 (without quotes and without empty spaces between the
numbers) and save the
package afterwards)

Change the computer language of the system to German (Gerrmany) as
described on InstallSite. If still not working: Interesting is the
output of step 3. Please post it here. Be aware that you work exactly
on the generated packages and no dirty ones where possibly something
went wrong...

Regarding Arabic: Think of only localize text and not RTL the UIs.
One of our arabic speaking guys told me that these people are used of
not well RTL modified UIs. If you still want to do so: Get an
installShield demo (they offer well RTL layout, think only the graphic
on the start dlg and finish dialog is turned) and modify the WiX
dialogs in WiX sources folder src\ext\UIExtension\wixlib (approx 25 -
30 dialogs and User Interface sequences). Think it should be
possible here as well to embed a transform for the modifications even
here this transform then contains a completely modified UI. But as
never done also expect some issues when transforming with a torch
generated transform for arabic (not sure whether -t Language is
enough).

As already stated think of using a bootstrapper for the language
transform application (e.g. dotnetinstaller) instead of the embedded
approach.

regards
Tobias

2011/3/17 Francisco Gabriel Malbrán fgmalb...@gmail.com:
Thanks Michael. I've tried your solution as well but still no results.

Can any body please attach an empty/demo version of your multilanguage msi
to test it out in my computer? This way I would be able to detect if the
problem is in the procedure or in the environment.

Thanks in advance

Francisco

2011/3/17 Michael Tissington michael_tissing...@ciqual.com

out
$(ProjectDir)$(OutDir)1040.mst

--
Francisco Gabriel Malbrán
Licenciado en Ciencias de la Computación
Online CV: www.linkedin.com/in/franciscomalbran
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Multilanguage install

@Chris: Am I understanding you right ? You want to apply a transform
for the base language, e.g. english MSI + english MST + spanish MST
? For InstallShield as they build by default a transform for the
default language ? If yes did you check with a man in the middle
tool (custom msiexec.exe in directory of setup.exe which shows its
calling command line) what the installshield setup.exe calls in case
of the default Language ? (esp. if they already apply a transform or
not ?) Not sure right now whether this works or not but I can check if
Andreas Kerl wrote something in his book about this and the abilities
of torch here.

As a sample if you want e.g. 8 transforms you only need 2 MSIs in
different languages and then can create an XML diff and modify this
for the other 6 languages and from these generate the transforms
again. This might reduce build time as not building the MSIs just for
transform generation is needed.

2011/3/17 Tobias S tobias.s1...@gmail.com:
Francisco,

I'd recommend you to use e.g. German and 1031 for your testing. Please
do exactly following:
1. Build the MSI + transform
2. test it with msiexec /i setup.msi TRANSFORMS=1031.mst

If working
3. embed the transform with
wisubstg.vbs Setup.msi 1031.mst 1031

4. ORCA: View - Summary Information... - there change Languages to
1033,1031 (without quotes and without empty spaces between the
numbers) and save the
package afterwards)

As already stated think of using a bootstrapper for the language
transform application (e.g. dotnetinstaller) instead of the embedded
approach.

regards
Tobias

2011/3/17 Francisco Gabriel Malbrán fgmalb...@gmail.com:
Thanks Michael. I've tried your solution as well but still no results.

Can any body please attach an empty/demo version of your multilanguage msi
to test it out in my computer? This way I would be able to detect if the
problem is in the procedure or in the environment.

Thanks in advance

Francisco

2011/3/17 Michael Tissington michael_tissing...@ciqual.com

out
$(ProjectDir)$(OutDir)1040.mst

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d

Re: [WiX-users] Multilanguage install

Target Name=AfterBuild
Torch
Condition=%(CultureGroup.Identity) != '$(DefaultLanguage)'
ToolPath=$(WixToolPath)
BaselineFile=$(TargetDir)$(DefaultLanguage)\$(TargetFileName)
UpdateFile=$(TargetDir)%(CultureGroup.OutputFolder)$(TargetFileName)

OutputFile=$(TargetDir)$(DefaultLanguage)\%(CultureGroup.Identity)$(TransformExt)
AdditionalOptions=-t Language /
/Target

for the WiX Proj ? This generates transforms in the DefaultLanguage
output folder.

2011/3/17 Christopher Painter chr...@deploymentengineering.com:
Oh I already know how it works and can get it to work. :-) I was just
wondering if there was a better way to generate the transforms then post build
events that call torch. Votive has some nice msbuild support for
encapsulating

the underlying calls to the wix tools I just wish it has a little checkbox
next

to cultures to build ( generate language transforms ).

BTW, you don't need a man in the middle to sniff out the command line, you
can use wmic ( windows management instrumentation console ) to do that.

---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me

- Original Message
From: Tobias S tobias.s1...@gmail.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Thu, March 17, 2011 4:52:53 PM
Subject: Re: [WiX-users] Multilanguage install

2011/3/17 Tobias S tobias.s1...@gmail.com:
Francisco,

Btw: Spanish if I remember right this is the OS where the LCID is 1034
and additionally other LCIDs exist. Maybe that causes problems in
detecting a spanish OS with these embedded transforms. Read
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/LCIDs-of-the-supported-languages-of-WixUIExtension-tp5910168p5910168.html
l
So maybe use some other language first to track down the problem and
set the OS language as described in InstallSite.

I'd recommend you to use e.g. German and 1031 for your testing. Please
do exactly following:
1. Build the MSI + transform
2. test it with msiexec /i setup.msi TRANSFORMS=1031.mst

If working
3. embed the transform with
wisubstg.vbs Setup.msi 1031.mst 1031

4. ORCA: View - Summary Information... - there change Languages to
1033,1031 (without quotes and without empty spaces between the
numbers) and save the
package afterwards)

Re: [WiX-users] Multilanguage install

You must add a torch task to the AfterBuild target in the wixproj file.

Following a description assuming you are using VS2010 English, your
solution is called MySetupProject and you want to create for an
english MSI the needed MSTs:
Solution Explorer - Choose the Setup Project - Right click - Unload
Project - Right click - Edit MySetupProject.wixproj

Uncomment
Target Name=AfterBuild
/Target

and modify it to e.g.

  Target Name=AfterBuild
Torch
Condition=%(CultureGroup.Identity) != 'en-US'
ToolPath=$(WixToolPath)
BaselineFile=$(TargetDir)en-US\$(TargetFileName)
UpdateFile=$(TargetDir)%(CultureGroup.OutputFolder)$(TargetFileName)
OutputFile=$(TargetDir)en-US\%(CultureGroup.Identity).mst
AdditionalOptions=-t Language /
  /Target


Reload project and build ...

This undocumented torch task is used here to build the transform(s)
(no matter how much Cultures you have set) except for the base
language en-US.


@Chris: For your wish Checkbox: Commenting and uncommenting is
necessary here. Thanks for your hint regarding WMIC. Use now the
functionality of ProcessExplorer to show the passed MSI parameters :-)



2011/3/18 Michael Tissington michael_tissing...@ciqual.com:
 This looks great - where do I put this?

 -Original Message-
 From: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: 18 March 2011 09:07
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Multilanguage install

  Target Name=AfterBuild
    Torch
      Condition=%(CultureGroup.Identity) != '$(DefaultLanguage)'
      ToolPath=$(WixToolPath)
      BaselineFile=$(TargetDir)$(DefaultLanguage)\$(TargetFileName)
      UpdateFile=$(TargetDir)%(CultureGroup.OutputFolder)$(TargetFileName)

 OutputFile=$(TargetDir)$(DefaultLanguage)\%(CultureGroup.Identity)$(Transfo
 rmExt)
      AdditionalOptions=-t Language /
  /Target

 for the WiX Proj ? This generates transforms in the DefaultLanguage
 output folder.



 2011/3/17 Christopher Painter chr...@deploymentengineering.com:
 Oh I already know how it works and can get it to work. :-)   I was
 just wondering if there was a better way to generate the transforms
 then post build events that call torch.   Votive has some nice msbuild
 support for encapsulating

 the underlying calls to the wix tools  I just wish it has a little
 checkbox next

 to cultures to build ( generate language transforms ).

 BTW, you don't need a man in the middle to sniff out the command
 line,  you can use wmic ( windows management instrumentation console )
 to do that.


 ---
 Christopher Painter, Author of Deployment Engineering Blog Have a hot
 tip, know a secret or read a really good thread that deserves
 attention? E-Mail Me



 - Original Message 
 From: Tobias S tobias.s1...@gmail.com
 To: General discussion for Windows Installer XML toolset.
 wix-users@lists.sourceforge.net
 Sent: Thu, March 17, 2011 4:52:53 PM
 Subject: Re: [WiX-users] Multilanguage install

 @Chris: Am I understanding you right ? You want to apply a transform
 for the base language, e.g. english MSI + english MST + spanish MST
 ? For InstallShield as they build by default a transform for the
 default language ? If yes did you check with a man in the middle
 tool (custom msiexec.exe in directory of setup.exe which shows its
 calling command line) what the installshield setup.exe calls in case
 of the default Language ? (esp. if they already apply a transform or
 not ?) Not sure right now whether this works or not but I can check if
 Andreas Kerl wrote something in his book about this and the abilities
 of torch here.

 As a sample if you want e.g. 8 transforms you only need 2 MSIs in
 different languages and then can create an XML diff and modify this
 for the other 6 languages and from these generate the transforms
 again. This might reduce build time as not building the MSIs just for
 transform generation is needed.



 2011/3/17 Tobias S tobias.s1...@gmail.com:
 Francisco,

 When you get it working with the transform msiexec /i installer.msi
 TRANSFORMS=:1034. (I'm wondering about the :1034 - should be e.g.
 1034.mst???) this means it is working with your produced spanish
 transform applied to the english one. So when going back to
 InstallSite your problems can result in problems in step 3. or 4. .

 In general and why I don't like this approach very much: you must
 rely on the way here this undocumented feature retrieves the current
 OS language. If something goes wrong here it is difficult to track
 down the real issue. So did you try the package on several spanish
 systems ?

 Btw: Spanish if I remember right this is the OS where the LCID is
1034  and additionally other LCIDs exist. Maybe that causes problems
in  detecting a spanish OS with these embedded transforms. Read
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/LCIDs-of
-the-supported-languages-of-WixUIExtension-tp5910168p5910168.html
l
 So maybe use some other

Re: [WiX-users] Multilanguage install

you must build all languages of the MSI pacakge from one project.
Think there is no additional modification necessary as the AfterBuild
target starts when there already exist the different MSIs (e.g.
en-US\MySetupProject.msi, de-DE\MySetupProject.msi and
ja-JP\MySetupProject.msi).

BTW: be sure not using a autogenerated ProductCode (*) to not
transform this by the transforms as well!



2011/3/18 Michael Tissington michael_tissing...@ciqual.com:
 Thanks for the detailed info ..

 I'm trying to implement this. This seems to require that the en-US is built
 first.
 How do I make this happen?

 -Original Message-
 From: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: 18 March 2011 10:08
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Multilanguage install

 You must add a torch task to the AfterBuild target in the wixproj file.

 Following a description assuming you are using VS2010 English, your solution
 is called MySetupProject and you want to create for an english MSI the
 needed MSTs:
 Solution Explorer - Choose the Setup Project - Right click - Unload
 Project - Right click - Edit MySetupProject.wixproj

 Uncomment
        Target Name=AfterBuild
        /Target

 and modify it to e.g.

  Target Name=AfterBuild
    Torch
        Condition=%(CultureGroup.Identity) != 'en-US'
        ToolPath=$(WixToolPath)
        BaselineFile=$(TargetDir)en-US\$(TargetFileName)

 UpdateFile=$(TargetDir)%(CultureGroup.OutputFolder)$(TargetFileName)
        OutputFile=$(TargetDir)en-US\%(CultureGroup.Identity).mst
        AdditionalOptions=-t Language /
  /Target


 Reload project and build ...

 This undocumented torch task is used here to build the transform(s) (no
 matter how much Cultures you have set) except for the base
 language en-US.


 @Chris: For your wish Checkbox: Commenting and uncommenting is necessary
 here. Thanks for your hint regarding WMIC. Use now the functionality of
 ProcessExplorer to show the passed MSI parameters :-)



 2011/3/18 Michael Tissington michael_tissing...@ciqual.com:
 This looks great - where do I put this?

 -Original Message-
 From: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: 18 March 2011 09:07
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Multilanguage install

  Target Name=AfterBuild
    Torch
      Condition=%(CultureGroup.Identity) != '$(DefaultLanguage)'
      ToolPath=$(WixToolPath)
      BaselineFile=$(TargetDir)$(DefaultLanguage)\$(TargetFileName)

  UpdateFile=$(TargetDir)%(CultureGroup.OutputFolder)$(TargetFileName)

 OutputFile=$(TargetDir)$(DefaultLanguage)\%(CultureGroup.Identity)$(T
 ransfo
 rmExt)
      AdditionalOptions=-t Language /
  /Target

 for the WiX Proj ? This generates transforms in the DefaultLanguage
 output folder.



 2011/3/17 Christopher Painter chr...@deploymentengineering.com:
 Oh I already know how it works and can get it to work. :-)   I was
 just wondering if there was a better way to generate the transforms
 then post build events that call torch.   Votive has some nice
 msbuild support for encapsulating

 the underlying calls to the wix tools  I just wish it has a little
 checkbox next

 to cultures to build ( generate language transforms ).

 BTW, you don't need a man in the middle to sniff out the command
 line,  you can use wmic ( windows management instrumentation console
 )
 to do that.


 ---
 Christopher Painter, Author of Deployment Engineering Blog Have a hot
 tip, know a secret or read a really good thread that deserves
 attention? E-Mail Me



 - Original Message 
 From: Tobias S tobias.s1...@gmail.com
 To: General discussion for Windows Installer XML toolset.
 wix-users@lists.sourceforge.net
 Sent: Thu, March 17, 2011 4:52:53 PM
 Subject: Re: [WiX-users] Multilanguage install

 @Chris: Am I understanding you right ? You want to apply a transform
 for the base language, e.g. english MSI + english MST + spanish MST
 ? For InstallShield as they build by default a transform for the
 default language ? If yes did you check with a man in the middle
 tool (custom msiexec.exe in directory of setup.exe which shows its
 calling command line) what the installshield setup.exe calls in case
 of the default Language ? (esp. if they already apply a transform or
 not ?) Not sure right now whether this works or not but I can check
 if Andreas Kerl wrote something in his book about this and the
 abilities of torch here.

 As a sample if you want e.g. 8 transforms you only need 2 MSIs in
 different languages and then can create an XML diff and modify this
 for the other 6 languages and from these generate the transforms
 again. This might reduce build time as not building the MSIs just for
 transform generation is needed.



 2011/3/17 Tobias S tobias.s1...@gmail.com:
 Francisco,

 When you get it working with the transform msiexec /i installer.msi
 TRANSFORMS=:1034. (I'm wondering about the :1034 - should be e.g.
 1034.mst???) this means

Re: [WiX-users] Multilanguage install

Nope don't think so as WiSubStg.vbs + WiLangId.vbs are part of the
Windows SDK and WiX will use Burn for Multilanguage Bootstrapper
installers. And as the Transform Embedding is undocumented I don't
assume WiX will write wrappers for such a purpose.


To do so you must e.g. write an own C# task fulfilling the actions
from these 2 VBscripts. Think this should be possible using DTF. It's
adding the transform(s) to a binary stream and modify the Summary
Information stream...



2011/3/18 Michael Tissington michael_tissing...@ciqual.com:
 Thanks got it :)

 Are there any additional hidden gems (undocumented tasks)to do the
 additional two task to embed the mst files into a single msi?
 Currently I'm using WiSubStg.vbs and WiLangID.vbs

 -Original Message-
 From: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: 18 March 2011 10:32
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Multilanguage install

 you must build all languages of the MSI pacakge from one project.
 Think there is no additional modification necessary as the AfterBuild target
 starts when there already exist the different MSIs (e.g.
 en-US\MySetupProject.msi, de-DE\MySetupProject.msi and
 ja-JP\MySetupProject.msi).

 BTW: be sure not using a autogenerated ProductCode (*) to not transform
 this by the transforms as well!



 2011/3/18 Michael Tissington michael_tissing...@ciqual.com:
 Thanks for the detailed info ..

 I'm trying to implement this. This seems to require that the en-US is
 built first.
 How do I make this happen?

 -Original Message-
 From: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: 18 March 2011 10:08
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Multilanguage install

 You must add a torch task to the AfterBuild target in the wixproj file.

 Following a description assuming you are using VS2010 English, your
 solution is called MySetupProject and you want to create for an
 english MSI the needed MSTs:
 Solution Explorer - Choose the Setup Project - Right click - Unload
 Project - Right click - Edit MySetupProject.wixproj

 Uncomment
        Target Name=AfterBuild
        /Target

 and modify it to e.g.

  Target Name=AfterBuild
    Torch
        Condition=%(CultureGroup.Identity) != 'en-US'
        ToolPath=$(WixToolPath)
        BaselineFile=$(TargetDir)en-US\$(TargetFileName)

 UpdateFile=$(TargetDir)%(CultureGroup.OutputFolder)$(TargetFileName)
        OutputFile=$(TargetDir)en-US\%(CultureGroup.Identity).mst
        AdditionalOptions=-t Language /
  /Target


 Reload project and build ...

 This undocumented torch task is used here to build the transform(s)
 (no matter how much Cultures you have set) except for the base
 language en-US.


 @Chris: For your wish Checkbox: Commenting and uncommenting is
 necessary here. Thanks for your hint regarding WMIC. Use now the
 functionality of ProcessExplorer to show the passed MSI parameters :-)



 2011/3/18 Michael Tissington michael_tissing...@ciqual.com:
 This looks great - where do I put this?

 -Original Message-
 From: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: 18 March 2011 09:07
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Multilanguage install

  Target Name=AfterBuild
    Torch
      Condition=%(CultureGroup.Identity) != '$(DefaultLanguage)'
      ToolPath=$(WixToolPath)
      BaselineFile=$(TargetDir)$(DefaultLanguage)\$(TargetFileName)

  UpdateFile=$(TargetDir)%(CultureGroup.OutputFolder)$(TargetFileName)

 OutputFile=$(TargetDir)$(DefaultLanguage)\%(CultureGroup.Identity)$(
 T
 ransfo
 rmExt)
      AdditionalOptions=-t Language /
  /Target

 for the WiX Proj ? This generates transforms in the DefaultLanguage
 output folder.



 2011/3/17 Christopher Painter chr...@deploymentengineering.com:
 Oh I already know how it works and can get it to work. :-)   I was
 just wondering if there was a better way to generate the transforms
 then post build events that call torch.   Votive has some nice
 msbuild support for encapsulating

 the underlying calls to the wix tools  I just wish it has a little
 checkbox next

 to cultures to build ( generate language transforms ).

 BTW, you don't need a man in the middle to sniff out the command
 line,  you can use wmic ( windows management instrumentation console
 )
 to do that.


 ---
 Christopher Painter, Author of Deployment Engineering Blog Have a
 hot tip, know a secret or read a really good thread that deserves
 attention? E-Mail Me



 - Original Message 
 From: Tobias S tobias.s1...@gmail.com
 To: General discussion for Windows Installer XML toolset.
 wix-users@lists.sourceforge.net
 Sent: Thu, March 17, 2011 4:52:53 PM
 Subject: Re: [WiX-users] Multilanguage install

 @Chris: Am I understanding you right ? You want to apply a transform
 for the base language, e.g. english MSI + english MST + spanish
 MST ? For InstallShield as they build by default a transform

Re: [WiX-users] Multilanguage install

They are used by the underlying WiX MSBUild target which is
responsible for building the solution in MSBuild. IIRC it is
C:\Program Files (x86)\MSBuild\Microsoft\WiX\v3.x\wix200x.targets for
NET35 and wix2010.targets for .NET 40.


2011/3/18 Michael Tissington michael_tissing...@ciqual.com:
 Too bad ...

 What are the properties for CultureGroup ?
 Where does this come from?

 Thanks.

 -Original Message-
 From: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: 18 March 2011 11:49
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Multilanguage install

 Nope don't think so as WiSubStg.vbs + WiLangId.vbs are part of the Windows
 SDK and WiX will use Burn for Multilanguage Bootstrapper installers. And as
 the Transform Embedding is undocumented I don't assume WiX will write
 wrappers for such a purpose.


 To do so you must e.g. write an own C# task fulfilling the actions from
 these 2 VBscripts. Think this should be possible using DTF. It's adding the
 transform(s) to a binary stream and modify the Summary Information stream...



 2011/3/18 Michael Tissington michael_tissing...@ciqual.com:
 Thanks got it :)

 Are there any additional hidden gems (undocumented tasks)to do the
 additional two task to embed the mst files into a single msi?
 Currently I'm using WiSubStg.vbs and WiLangID.vbs

 -Original Message-
 From: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: 18 March 2011 10:32
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Multilanguage install

 you must build all languages of the MSI pacakge from one project.
 Think there is no additional modification necessary as the AfterBuild
 target starts when there already exist the different MSIs (e.g.
 en-US\MySetupProject.msi, de-DE\MySetupProject.msi and
 ja-JP\MySetupProject.msi).

 BTW: be sure not using a autogenerated ProductCode (*) to not
 transform this by the transforms as well!



 2011/3/18 Michael Tissington michael_tissing...@ciqual.com:
 Thanks for the detailed info ..

 I'm trying to implement this. This seems to require that the en-US is
 built first.
 How do I make this happen?

 -Original Message-
 From: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: 18 March 2011 10:08
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Multilanguage install

 You must add a torch task to the AfterBuild target in the wixproj file.

 Following a description assuming you are using VS2010 English, your
 solution is called MySetupProject and you want to create for an
 english MSI the needed MSTs:
 Solution Explorer - Choose the Setup Project - Right click -
 Unload Project - Right click - Edit MySetupProject.wixproj

 Uncomment
        Target Name=AfterBuild
        /Target

 and modify it to e.g.

  Target Name=AfterBuild
    Torch
        Condition=%(CultureGroup.Identity) != 'en-US'
        ToolPath=$(WixToolPath)
        BaselineFile=$(TargetDir)en-US\$(TargetFileName)

 UpdateFile=$(TargetDir)%(CultureGroup.OutputFolder)$(TargetFileName)
        OutputFile=$(TargetDir)en-US\%(CultureGroup.Identity).mst
        AdditionalOptions=-t Language /
  /Target


 Reload project and build ...

 This undocumented torch task is used here to build the transform(s)
 (no matter how much Cultures you have set) except for the base
 language en-US.


 @Chris: For your wish Checkbox: Commenting and uncommenting is
 necessary here. Thanks for your hint regarding WMIC. Use now the
 functionality of ProcessExplorer to show the passed MSI parameters
 :-)



 2011/3/18 Michael Tissington michael_tissing...@ciqual.com:
 This looks great - where do I put this?

 -Original Message-
 From: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: 18 March 2011 09:07
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Multilanguage install

  Target Name=AfterBuild
    Torch
      Condition=%(CultureGroup.Identity) != '$(DefaultLanguage)'
      ToolPath=$(WixToolPath)
      BaselineFile=$(TargetDir)$(DefaultLanguage)\$(TargetFileName)

  UpdateFile=$(TargetDir)%(CultureGroup.OutputFolder)$(TargetFileName)

 OutputFile=$(TargetDir)$(DefaultLanguage)\%(CultureGroup.Identity)$
 (
 T
 ransfo
 rmExt)
      AdditionalOptions=-t Language /
  /Target

 for the WiX Proj ? This generates transforms in the DefaultLanguage
 output folder.



 2011/3/17 Christopher Painter chr...@deploymentengineering.com:
 Oh I already know how it works and can get it to work. :-)   I was
 just wondering if there was a better way to generate the transforms
 then post build events that call torch.   Votive has some nice
 msbuild support for encapsulating

 the underlying calls to the wix tools  I just wish it has a little
 checkbox next

 to cultures to build ( generate language transforms ).

 BTW, you don't need a man in the middle to sniff out the command
 line,  you can use wmic ( windows management instrumentation
 console
 )
 to do

Re: [WiX-users] Multilanguage install

To be honest I'd like this approach more as well (InstallShield e.g.
does it and so would better fit into the Christopher Painter approach
to incorporate IS bootstrapper + WiX MSI packages). But for now I
didn't find a solution except renaming all the transforms.

Figuring out how to handle the CultureGroup cost me some time and, as
I'm not soo deep in MSBuild targets, figuring out how to get the LCIDs
(even if it's possible ?) would cost me additional time which is
surely better invested in just renaming the files which is a 5 minute
job :-)



2011/3/18 Michael Tissington michael_tissing...@ciqual.com:
 Instead of using CultureGroup.Identity is there a way to use the Product
 Language (for example 1033) ?

 I'd like torch to create a file name Language.mst

 Thanks.

 -Original Message-
 From: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: 18 March 2011 12:18
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Multilanguage install

 They are used by the underlying WiX MSBUild target which is responsible for
 building the solution in MSBuild. IIRC it is C:\Program Files
 (x86)\MSBuild\Microsoft\WiX\v3.x\wix200x.targets for
 NET35 and wix2010.targets for .NET 40.


 2011/3/18 Michael Tissington michael_tissing...@ciqual.com:
 Too bad ...

 What are the properties for CultureGroup ?
 Where does this come from?

 Thanks.

 -Original Message-
 From: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: 18 March 2011 11:49
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Multilanguage install

 Nope don't think so as WiSubStg.vbs + WiLangId.vbs are part of the
 Windows SDK and WiX will use Burn for Multilanguage Bootstrapper
 installers. And as the Transform Embedding is undocumented I don't
 assume WiX will write wrappers for such a purpose.


 To do so you must e.g. write an own C# task fulfilling the actions
 from these 2 VBscripts. Think this should be possible using DTF. It's
 adding the
 transform(s) to a binary stream and modify the Summary Information
 stream...



 2011/3/18 Michael Tissington michael_tissing...@ciqual.com:
 Thanks got it :)

 Are there any additional hidden gems (undocumented tasks)to do the
 additional two task to embed the mst files into a single msi?
 Currently I'm using WiSubStg.vbs and WiLangID.vbs

 -Original Message-
 From: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: 18 March 2011 10:32
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Multilanguage install

 you must build all languages of the MSI pacakge from one project.
 Think there is no additional modification necessary as the AfterBuild
 target starts when there already exist the different MSIs (e.g.
 en-US\MySetupProject.msi, de-DE\MySetupProject.msi and
 ja-JP\MySetupProject.msi).

 BTW: be sure not using a autogenerated ProductCode (*) to not
 transform this by the transforms as well!



 2011/3/18 Michael Tissington michael_tissing...@ciqual.com:
 Thanks for the detailed info ..

 I'm trying to implement this. This seems to require that the en-US
 is built first.
 How do I make this happen?

 -Original Message-
 From: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: 18 March 2011 10:08
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Multilanguage install

 You must add a torch task to the AfterBuild target in the wixproj file.

 Following a description assuming you are using VS2010 English, your
 solution is called MySetupProject and you want to create for an
 english MSI the needed MSTs:
 Solution Explorer - Choose the Setup Project - Right click -
 Unload Project - Right click - Edit MySetupProject.wixproj

 Uncomment
        Target Name=AfterBuild
        /Target

 and modify it to e.g.

  Target Name=AfterBuild
    Torch
        Condition=%(CultureGroup.Identity) != 'en-US'
        ToolPath=$(WixToolPath)
        BaselineFile=$(TargetDir)en-US\$(TargetFileName)

 UpdateFile=$(TargetDir)%(CultureGroup.OutputFolder)$(TargetFileName)
        OutputFile=$(TargetDir)en-US\%(CultureGroup.Identity).mst
        AdditionalOptions=-t Language /
  /Target


 Reload project and build ...

 This undocumented torch task is used here to build the
 transform(s) (no matter how much Cultures you have set) except for the
 base
 language en-US.


 @Chris: For your wish Checkbox: Commenting and uncommenting is
 necessary here. Thanks for your hint regarding WMIC. Use now the
 functionality of ProcessExplorer to show the passed MSI parameters
 :-)



 2011/3/18 Michael Tissington michael_tissing...@ciqual.com:
 This looks great - where do I put this?

 -Original Message-
 From: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: 18 March 2011 09:07
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Multilanguage install

  Target Name=AfterBuild
    Torch
      Condition=%(CultureGroup.Identity) != '$(DefaultLanguage

Re: [WiX-users] Multilanguage install

2011-03-21 Thread Tobias S

@Chris
InstallShield bootstrapper needs 2 MSTs as it even transforms the
default lanugage (no idea why - transform is not empty, it applies
additional property InstallShieldTempProp=0 ). Assume here the only
way is to build with WiX the MSIs containing a dummy property (e.g.
WiXProperty = 0). Afterwards create a copy of the base language MSI,
remove from the copy the property again and create with torch the
transforms between the different languages (with dummy property) and
the modified base package without dummy property.

Having now the transforms for all languages should fit for
InstallShield bootstrapper. BTW: Should also work for IS2010 and
previous when there is no need for embedding the WiX files in a
Setup.exe.

Regards
Tobias

2011/3/17 Christopher Painter chr...@deploymentengineering.com:
I created an installer using Votive and told it to build English and Spanish
cultures. I ended up with two MSIs. Is there a way to tell it to build 1 MSI
and 2 MSTs? I was able to run Torch from the command line to get there but I
was wondering if there was an easier way.

If you happeen to own InstallShield you can create a fake Basic MSI with a
multilingual story and then drop your WiX MSI on top of your IS MSI and get
the
best of both worlds. If you are distributing a compressed setup.exe you can
still do this if you have IS 2011 Premiere. The trick is to use the
precompression build event to do the swap out.

---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me

- Original Message
From: Tobias S tobias.s1...@gmail.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Thu, March 17, 2011 4:30:32 AM
Subject: Re: [WiX-users] Multilanguage install

Hi Francesco,

Here some information to your questions

For 1. and 2.) I created a MSI (Setup.msi) and a german MST (de-DE.mst).

For 3.) I embedded the Transform with
wisubstg.vbs Setup.msi de-DE.mst 1031

This should work. If you don't get it working what then happens when
only applying the transform ?
( msiexec /i setup.msi TRANSFORMS=de-DE.mst )

Regards
Tobias

A) How can I make the multilanguague work?? (I'm trying hard, I swear)

Can you please explain in more detail how did you manage to make this work?

I am using WiX 3.5 in Windows 7 and I just can't find a way to make my msi
file autodetect
the language of the OS. It always starts in the default language, english.

I've tried a lot of things, for example:
- http://www.codeproject.com/KB/install/WixWindowsInstallerDemo3.aspx
-
http://www.geektieguy.com/2010/03/13/create-a-multi-lingual-multi-language-msi-using-wix-and-custom-build-scripts/
/
- things explained in this book:
http://my.safaribooksonline.com/book/-/9781849513722/localizing-your-installer/ch12lvl1sec06(of
f
course, the complete version)
- my own mixed versions of all I read in different places.
- more

I used the Windows 7 SDK script

cscript.exe utils\WiLangId.vbs installer.msi Package 1033,1034

Re: [WiX-users] EN-IN language ID in WiX

2011-03-24 Thread Tobias S

Hi,

Assume this won't work as the LCID and locale en-IN doesn't exist in
WiX. Try hi-IN and 0x0439 Hindi (India) instead. An overview of the
LCIDs and WiX Culture names you can see in my post
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/LCIDs-of-the-supported-languages-of-WixUIExtension-td5910168.html#a5913708
.

BTW: Where do you use the hex representation of the LCID ? Normally
for localization only the decimal representation of the LCID + WiX
culture name is needed.

For a sample wxl file check out e.g. http://wix.mindcapers.com/wiki/Localization

Regards
Tobias

2011/3/24 Grzegorz Borczuch t-gr...@microsoft.com:
Hallo everyone,

Recently, I was trying to find some information about how does WiX handle the
issue with the new LCIDs introduced in Windows Vista. I mean for example
en-IN locale with LCID as 0x4009.

I tried to build the MSI tables from WiX that contained India files. In that
case the light.exe throws a validation error ICE03 which means I am using
incorrect language id. Is this a matter of something in my .wxs file or
.wixproj or I should change the WiX version? I am using the 3.5.1916.0
version.

When I was searching the internet about that problem I could not find many
similar questions that could mean it is something rare. Is there anybody that
could confirm that this is a known issue?

Thanks in advance,
Grzegorz Borczuch
--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] EN-IN language ID in WiX

2011-03-24 Thread Tobias S

Regarding the localization of hi-in. This localization contains the
english strings which is confirmed to be a bug (comp.
http://sourceforge.net/tracker/index.php?func=detailaid=3163411group_id=105970atid=642714)
Think an older (or also newer) version of the WiX toolset has a
correct version of the translation for hi-In. (Didn't re-check it)

As this language is from minor importance I didn't follow the issue...

2011/3/24 Tobias S tobias.s1...@gmail.com:
Hi,

BTW: Where do you use the hex representation of the LCID ? Normally
for localization only the decimal representation of the LCID + WiX
culture name is needed.

For a sample wxl file check out e.g.
http://wix.mindcapers.com/wiki/Localization

Regards
Tobias

2011/3/24 Grzegorz Borczuch t-gr...@microsoft.com:
Hallo everyone,

Recently, I was trying to find some information about how does WiX handle
the issue with the new LCIDs introduced in Windows Vista. I mean for example
en-IN locale with LCID as 0x4009.

When I was searching the internet about that problem I could not find many
similar questions that could mean it is something rare. Is there anybody
that could confirm that this is a known issue?

Re: [WiX-users] DifxApp - Cannot create a stable subkey under a volatile parent key

2011-03-24 Thread Tobias S

Hi Rob,

Just some thoughts to it (even I never had the issue). Maybe they help:
On http://errordecoder.com/system-error-codes/3/code-1021.html I found
some points which could be from interest:
* Device Driver Conflicts
* Hardware Malfunction

Is it only one system where it occurs ? Hardware issues only with one
hardware device or with several ones?

Stupid but happened once to me: An internal NW Interface had some not
correct inserted memory which caused driver installation to fail in
not reproducible manner. As I didn't check I spent some days on that
issue...

Regards
Tobias



2011/3/24 Rob Hamflett r...@snsys.com:
 I'm seeing an occasional issue using DifxApp, which a log reports as:

 DIFXAPP: INFO:   ENTER UpdateDriverForPlugAndPlayDevices...
 DIFXAPP: ERROR:  RETURN UpdateDriverForPlugAndPlayDevices. (Error code 0x3FD: 
 Cannot create a stable
 subkey under a volatile parent key.)
 DIFXAPP: ERROR:  Installation failed. (Error code 0x3FD: Cannot create a 
 stable subkey under a
 volatile parent key.)
 DIFXAPP: ERROR:  PnP Install failed. (Error code 0x3FD: Cannot create a 
 stable subkey under a
 volatile parent key.)

 Running the installer again seems to be fine, so it's not a permanent 
 problem.  Has anyone seen this
 before?  The solutions I found online say to delete the registry key in 
 question, which I don't
 really think is safe in this situation.

 Thanks,
 Rob


 --
 Enable your software for Intel(R) Active Management Technology to meet the
 growing manageability and security demands of your customers. Businesses
 are taking advantage of Intel(R) vPro (TM) technology - will your software
 be a part of the solution? Download the Intel(R) Manageability Checker
 today! http://p.sf.net/sfu/intel-dev2devmar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] bootstrapper for non-Microsoft installer - warning item not located

2011-03-26 Thread Tobias S

Hi,

At first glance for me the two files product and pacack.xml seem to
have the wrong content.

As you describe your requirements have a look at SQL Server Compact
Edition Prerequisite as it has a similar structure and the intention
to install MSI packages.

Pleaase therefore diff the whole folder (esp. the content of
product.xml and package.xml)
C:\Program Files (x86)\Microsoft
SDKs\Windows\v7.0A\Bootstrapper\Packages\YourPackage
against
C:\Program Files (x86)\Microsoft
SDKs\Windows\v7.0A\Bootstrapper\Packages\SQL Server Compact Edition


Regards,
Tobias

2011/3/25 Paul Brook brook.p...@gmail.com:
 Hi all,

 I am attempting to build a bootstrapper for my wix installer in order
 install another program our customer wants deployed along with ours. I've
 been given the .msi file.

 Here's the error / warning I'm getting:
 warning MSB3155: Item 'Network.Configurator' could not be located in
 'C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\'.

 Also - when I run the setup.exe that is created along with my main .msi file
 it doesn't run the SetupNetConfig.msi file.

 Any help would be appreciated

 Paul

 What I have done so far is this.

 1. created a folder called NetworkConfigurator for the installer in:

 C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\

 2. copied the .msi file into the new folder
 3. created the product.xml in the new folder: Here it is.

 ?xml version=1.0 encoding=utf-8 ?
 Product
   xmlns=http://schemas.microsoft.com/developer/2004/01/bootstrapper;
   ProductCode=Network.Configurator

   !-- Defines list of files to be copied on build --
   PackageFiles CopyAllPackageFiles=true
      PackageFile Name=SetupNetConfig.msi/
   /PackageFiles

   RelatedProducts
      DependsOnProduct Code=Microsoft.Windows.Installer.3.1 /
   /RelatedProducts

   ExitCodes
      ExitCode Value=0 Result=Success/
      ExitCode Value=1641 Result=SuccessReboot/
      ExitCode Value=3010 Result=SuccessReboot/
      DefaultExitCode Result=Fail String=GeneralFailure/
   /ExitCodes

 /Product


 4. created the EN folder
 5. created the package.xml file in the EN folder

 ?xml version=1.0 encoding=utf-8 ?
 Package
   xmlns=http://schemas.microsoft.com/developer/2004/01/bootstrapper;
   Name=DisplayName
   Culture=Culture

   Strings
      String Name=DisplayNameNetwork.Configurator/String
      String Name=Cultureen/String
      String Name=NotAnAdminYou must be an administrator to install this
 package./String
      String Name=GeneralFailureA general error has occurred while
 installing this package./String
   /Strings
 /Package

 6. Added the following to the wixproj file

  ItemGroup
    BootstrapperFile Include=Network.Configurator
      ProductNameNetwork.Configurator/ProductName
    /BootstrapperFile
    BootstrapperFile Include=Microsoft.Windows.Installer.3.1
      ProductNameWindows Installer 3.1/ProductName
    /BootstrapperFile
  /ItemGroup
  Target Name=AfterBuild Outputs=$(Outdir)\Setup.exe
    GenerateBootstrapper ApplicationFile=$(TargetFileName)
 ApplicationName=Network Configurator
 BootstrapperItems=@(BootstrapperFile) ComponentsLocation=Relative
 CopyComponents=True OutputPath=$(OutputPath) Path=C:\Program Files
 (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\ /
  /Target
 --
 Enable your software for Intel(R) Active Management Technology to meet the
 growing manageability and security demands of your customers. Businesses
 are taking advantage of Intel(R) vPro (TM) technology - will your software
 be a part of the solution? Download the Intel(R) Manageability Checker
 today! http://p.sf.net/sfu/intel-dev2devmar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] EN-IN language ID in WiX

2011-03-26 Thread Tobias S

For Product/@Language decimal LCID representation is needed and here
16393 (en-IN) is not allowed. As I understand WiX uses the parent
language for special Locales like e.g. German(German) for
German(Austria) and German(Switzerland) to serve german speaking
installations or en-US for the different english locales in the world.

So the list of LCIDs is also working for WiX installers without UI
when you plan to not use WiXUIExtension. For the exact supported LCIDs
I assume all in the list mentioned ones are supported and working
correctly.

Regarding your question about specialized langages like e.g. en-SG I
see no need for that. IMHO no vendor in installation tools has such
localizations and if you consider e.g. WiX localisation zh-tw and
zw-hk you see minor differences only (even I don't understand these
languages). Here the company I'm working for distinguishes between
Chinese Simplified and Chinese Traditional (and here no additional
difference between zh-hk and zh-tw) and afaik nobody ever complained
about that.

2011/3/25 Grzegorz Borczuch t-gr...@microsoft.com:
Hi everybody,

Thanks Tobias for his answers.

@Tobias: I not sure if it makes any difference, but I intend to use LCID
without using WixUIExtension. Is your list of supported languages is also
valid when one doesn't use the translated UI?

Another question is to the whole community. Does anybody know if there are
plans for enabling en-IN and other en-XX (en-MY, en-SG) languages in future
versions of WiX?

Best regards,
Grzegorz Borczuch

2011/3/24 Tobias S tobias.s1...@gmail.com:
Regarding the localization of hi-in. This localization contains the english
strings which is confirmed to be a bug (comp.
http://sourceforge.net/tracker/index.php?func=detailaid=3163411group_id=105970atid=642714)
Think an older (or also newer) version of the WiX toolset has a correct
version of the translation for hi-In. (Didn't re-check it)

As this language is from minor importance I didn't follow the issue...

2011/3/24 Tobias S tobias.s1...@gmail.com:
Hi,

Assume this won't work as the LCID and locale en-IN doesn't exist in
WiX. Try hi-IN and 0x0439 ?Hindi (India) ?instead. An overview of the
LCIDs and WiX Culture names you can see in my post
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/LCIDs-of
-the-supported-languages-of-WixUIExtension-td5910168.html#a5913708
.

BTW: Where ?do you use the hex representation of the LCID ? Normally
for localization only the decimal representation of the LCID + WiX
culture name is needed.

For a sample wxl file check out e.g.
http://wix.mindcapers.com/wiki/Localization

Regards
Tobias

2011/3/24 Grzegorz Borczuch t-gr...@microsoft.com:
Hallo everyone,

Recently, I was trying to find some information about how does WiX handle
the issue with the new LCIDs introduced in Windows Vista. I mean for
example en-IN locale with LCID as 0x4009.

I tried to build the MSI tables from WiX that contained India files. In
that case the light.exe throws a validation error ICE03 which means I am
using incorrect language id. Is this a matter of something in my .wxs file
or .wixproj or I should change the WiX version? I am using the ?3.5.1916.0
version.

When I was searching the internet about that problem I could not find many
similar questions that could mean it is something rare. Is there anybody
that could confirm that this is a known issue?

Thanks in advance,
Grzegorz Borczuch
-
- Enable your software for Intel(R) Active Management
Technology to meet the growing manageability and security demands of
your customers. Businesses are taking advantage of Intel(R) vPro (TM)
technology - will your software be a part of the solution? Download
the Intel(R) Manageability Checker today!
http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WiX v3.5 and DTF using .NET 4

2011-03-26 Thread Tobias S

I read about that, as stated by Neil,
useLegacyV2RuntimeActivationPolicy must be set to true to prevent
issues 
(http://siderite.blogspot.com/2010/07/msi-custom-action-error-2896-on-windows.html).

But if I want the code not to run on FW 2.0 is it possible to not
allow the Runtime by commenting the supportedRuntime version 2.0 in
the .config: ?

 ?xml version=1.0?
 configuration
   startup useLegacyV2RuntimeActivationPolicy=true
 supportedRuntime version=v4.0 /
!-- supportedRuntime version=v2.0.50727/ --
   /startup
 /configuration

In this case I assume to be sure that the 4.0 code runs on 4.0 without
issues and on 2.0 not. Even normally this should work I'd like to
suppress the residual risk.


Regards,
Tobias



2011/3/26 Neil Sleightholm n...@x2systems.com:
 I am targeting .Net 4 with DTF and have not seen an issue. IIRC
 correctly you do need to make an alteration to the .config file as
 follows:
  ?xml version=1.0?
  configuration
    startup useLegacyV2RuntimeActivationPolicy=true
      supportedRuntime version=v4.0 /
      supportedRuntime version=v2.0.50727/
    /startup
  /configuration

 Neil

 -Original Message-
 From: Paden, Patrick [mailto:patrick.pa...@wolterskluwer.com]
 Sent: 25 March 2011 22:58
 To: General discussion for Windows Installer XML toolset.
 Subject: [WiX-users] WiX v3.5 and DTF using .NET 4

 I know it is supposed to work (saw the fixed bugs on it) but I needed a
 sanity check just to confirm with someone else that using WiX v3.5 and
 DTF with targeted .NET framework of 4.0, that it works for them and I
 must be doing something wrong =]

 
 --
 Enable your software for Intel(R) Active Management Technology to meet
 the growing manageability and security demands of your customers.
 Businesses are taking advantage of Intel(R) vPro (TM) technology - will
 your software be a part of the solution? Download the Intel(R)
 Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

 --
 Enable your software for Intel(R) Active Management Technology to meet the
 growing manageability and security demands of your customers. Businesses
 are taking advantage of Intel(R) vPro (TM) technology - will your software
 be a part of the solution? Download the Intel(R) Manageability Checker
 today! http://p.sf.net/sfu/intel-dev2devmar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] bootstrapper for non-Microsoft installer - warning item not located

2011-03-29 Thread Tobias S

Try BootstrapperItems=@(BootstrapperFile) instead of
BootstrapperItems=$(BootstrapperFile) in project file:
GenerateBootstrapper ApplicationFile=$(TargetFileName)
ApplicationName=Network Configurator
BootstrapperItems=@(BootstrapperFile) ComponentsLocation=Relative
CopyComponents=True OutputPath=$(OutputPath) Path=C:\Program
Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\ /

Additionally an additional folder is created and the prerequisite is
not included into the setup.exe


Regards
Tobias



2011/3/28 Paul Brook brook.p...@gmail.com:
 Thanks for the reply.

 I have tried to implement the bootstrapper based on your suggestion and I am
 not getting any more errors. However  the setup.exe is not getting bigger so
 I know the .msi file didn't make it into the setup.exe. I also ran the
 setup.exe and the bootstrapper didn't run.

 I can definitely see how the SQL project is a good model for installing an
 MSI so probably I've got an error in the package or product files. Please
 take a look - and thanks for your help.

 Here's my new package and product xml files. I did move the
 SetupNetConfig.msi file into the EN sub folder. I've include the new
 elements in the project file at the bottom of the email.

 Package.xml:

 ?xml version=1.0 encoding=utf-8 ?
 Package
   xmlns=http://schemas.microsoft.com/developer/2004/01/bootstrapper;
   Name=DisplayName
   Culture=Culture

  InstallChecks
    FileCheck Property=CONFIG
      SpecialFolder=ProgramFilesFolder
      FileName=NetConfig.exe SearchPath=.\ERF\VSU Network Configurator\
      SearchDepth=1/
  /InstallChecks

  PackageFiles CopyAllPackageFiles=false
    PackageFile Name=SetupNetConfig.msi /
  /PackageFiles

  Commands Reboot=Defer
    Command PackageFile =SetupNetConfig.msi Arguments=
      InstallConditions
        BypassIf Property=CONFIG Compare=ValueGreaterThanOrEqualTo
 Value=1.0.0.0/
      /InstallConditions
      ExitCodes
        ExitCode Value=0 Result=Success /
        ExitCode Value=1641 Result=SuccessReboot /
        ExitCode Value=3010 Result=SuccessReboot /
        ExitCode Value=4123 Result=SuccessReboot /
        DefaultExitCode Result=Fail String=Anunexpected
 FormatMessageFromSystem=true /
      /ExitCodes
    /Command

  /Commands
  Strings
    String Name=DisplayNameNetwork.Configurator/String
    String Name=CultureEN/String
    String Name=AnunexpectedAn unexpected exit code was returned from
 the installer. The installation failed./String
    String Name=GeneralFailureA general error has occurred while
 installing this package./String
  /Strings
 /Package

 Product.xml:

 ?xml version=1.0 encoding=utf-8 ?
 Product
   xmlns=http://schemas.microsoft.com/developer/2004/01/bootstrapper;
   ProductCode=Network.Configurator
 /Product


 New lines in project file:

 ItemGroup
    BootstrapperFile Include=Network.Configurator
      ProductNameNetwork.Configurator/ProductName
    /BootstrapperFile
  /ItemGroup
  Target Name=AfterBuild Outputs=$(Outdir)\Setup.exe
    GenerateBootstrapper ApplicationFile=$(TargetFileName)
 ApplicationName=Network Configurator
 BootstrapperItems=$(BootstrapperFile) ComponentsLocation=Relative
 CopyComponents=True OutputPath=$(OutputPath) Path=C:\Program Files
 (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\ /
  /Target


 On Sat, Mar 26, 2011 at 8:16 AM, Tobias S tobias.s1...@gmail.com wrote:

 Hi,

 At first glance for me the two files product and pacack.xml seem to
 have the wrong content.

 As you describe your requirements have a look at SQL Server Compact
 Edition Prerequisite as it has a similar structure and the intention
 to install MSI packages.

 Pleaase therefore diff the whole folder (esp. the content of
 product.xml and package.xml)
 C:\Program Files (x86)\Microsoft
 SDKs\Windows\v7.0A\Bootstrapper\Packages\YourPackage
 against
 C:\Program Files (x86)\Microsoft
 SDKs\Windows\v7.0A\Bootstrapper\Packages\SQL Server Compact Edition


 Regards,
 Tobias

 2011/3/25 Paul Brook brook.p...@gmail.com:
  Hi all,
 
  I am attempting to build a bootstrapper for my wix installer in order
  install another program our customer wants deployed along with ours. I've
  been given the .msi file.
 
  Here's the error / warning I'm getting:
  warning MSB3155: Item 'Network.Configurator' could not be located in
  'C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\'.
 
  Also - when I run the setup.exe that is created along with my main .msi
 file
  it doesn't run the SetupNetConfig.msi file.
 
  Any help would be appreciated
 
  Paul
 
  What I have done so far is this.
 
  1. created a folder called NetworkConfigurator for the installer in:
 
  C:\Program Files (x86)\Microsoft
 SDKs\Windows\v7.0A\Bootstrapper\Packages\
 
  2. copied the .msi file into the new folder
  3. created the product.xml in the new folder: Here it is.
 
  ?xml version=1.0 encoding=utf-8 ?
  Product
    xmlns=http://schemas.microsoft.com/developer/2004/01/bootstrapper;
    ProductCode=Network.Configurator
 
    !-- Defines

Re: [WiX-users] bootstrapper for non-Microsoft installer - warning item not located

2011-03-30 Thread Tobias S

No sorry. I meant the prerequisite is started by clicking on
setup.exe. Then a dialog appears if the launch condition for the
prerequisite is not satisfied and the user can confirm to install it.
As I remember the bootstrapper aborts if the user cancels the
prerequisite installation. So he is obliged to confirm in order to
install the application.

At first I thought you mean the prerequisite is directly embedded into
the setup.exe what the MS Bootstrapper cannot do.


2011/3/30 Paul Brook brook.p...@gmail.com:
 Ok that worked. I now am getting the new folder and the prerequisite .msi
 file.

 Based on my test and your comment the prereq will Not run via clicking on
 the setup.exe so the user will be required to make that choice themselves.
 Correct?



 On Tue, Mar 29, 2011 at 2:32 PM, Tobias S tobias.s1...@gmail.com wrote:

 Try BootstrapperItems=@(BootstrapperFile) instead of
 BootstrapperItems=$(BootstrapperFile) in project file:
 GenerateBootstrapper ApplicationFile=$(TargetFileName)
 ApplicationName=Network Configurator
 BootstrapperItems=@(BootstrapperFile) ComponentsLocation=Relative
 CopyComponents=True OutputPath=$(OutputPath) Path=C:\Program
 Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\ /

 Additionally an additional folder is created and the prerequisite is
 not included into the setup.exe


 Regards
 Tobias



 2011/3/28 Paul Brook brook.p...@gmail.com:
  Thanks for the reply.
 
  I have tried to implement the bootstrapper based on your suggestion and I
 am
  not getting any more errors. However  the setup.exe is not getting bigger
 so
  I know the .msi file didn't make it into the setup.exe. I also ran the
  setup.exe and the bootstrapper didn't run.
 
  I can definitely see how the SQL project is a good model for installing
 an
  MSI so probably I've got an error in the package or product files. Please
  take a look - and thanks for your help.
 
  Here's my new package and product xml files. I did move the
  SetupNetConfig.msi file into the EN sub folder. I've include the new
  elements in the project file at the bottom of the email.
 
  Package.xml:
 
  ?xml version=1.0 encoding=utf-8 ?
  Package
    xmlns=http://schemas.microsoft.com/developer/2004/01/bootstrapper;
    Name=DisplayName
    Culture=Culture
 
   InstallChecks
     FileCheck Property=CONFIG
       SpecialFolder=ProgramFilesFolder
       FileName=NetConfig.exe SearchPath=.\ERF\VSU Network
 Configurator\
       SearchDepth=1/
   /InstallChecks
 
   PackageFiles CopyAllPackageFiles=false
     PackageFile Name=SetupNetConfig.msi /
   /PackageFiles
 
   Commands Reboot=Defer
     Command PackageFile =SetupNetConfig.msi Arguments=
       InstallConditions
         BypassIf Property=CONFIG Compare=ValueGreaterThanOrEqualTo
  Value=1.0.0.0/
       /InstallConditions
       ExitCodes
         ExitCode Value=0 Result=Success /
         ExitCode Value=1641 Result=SuccessReboot /
         ExitCode Value=3010 Result=SuccessReboot /
         ExitCode Value=4123 Result=SuccessReboot /
         DefaultExitCode Result=Fail String=Anunexpected
  FormatMessageFromSystem=true /
       /ExitCodes
     /Command
 
   /Commands
   Strings
     String Name=DisplayNameNetwork.Configurator/String
     String Name=CultureEN/String
     String Name=AnunexpectedAn unexpected exit code was returned from
  the installer. The installation failed./String
     String Name=GeneralFailureA general error has occurred while
  installing this package./String
   /Strings
  /Package
 
  Product.xml:
 
  ?xml version=1.0 encoding=utf-8 ?
  Product
    xmlns=http://schemas.microsoft.com/developer/2004/01/bootstrapper;
    ProductCode=Network.Configurator
  /Product
 
 
  New lines in project file:
 
  ItemGroup
     BootstrapperFile Include=Network.Configurator
       ProductNameNetwork.Configurator/ProductName
     /BootstrapperFile
   /ItemGroup
   Target Name=AfterBuild Outputs=$(Outdir)\Setup.exe
     GenerateBootstrapper ApplicationFile=$(TargetFileName)
  ApplicationName=Network Configurator
  BootstrapperItems=$(BootstrapperFile) ComponentsLocation=Relative
  CopyComponents=True OutputPath=$(OutputPath) Path=C:\Program Files
  (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\ /
   /Target
 
 
  On Sat, Mar 26, 2011 at 8:16 AM, Tobias S tobias.s1...@gmail.com
 wrote:
 
  Hi,
 
  At first glance for me the two files product and pacack.xml seem to
  have the wrong content.
 
  As you describe your requirements have a look at SQL Server Compact
  Edition Prerequisite as it has a similar structure and the intention
  to install MSI packages.
 
  Pleaase therefore diff the whole folder (esp. the content of
  product.xml and package.xml)
  C:\Program Files (x86)\Microsoft
  SDKs\Windows\v7.0A\Bootstrapper\Packages\YourPackage
  against
  C:\Program Files (x86)\Microsoft
  SDKs\Windows\v7.0A\Bootstrapper\Packages\SQL Server Compact Edition
 
 
  Regards,
  Tobias
 
  2011/3/25 Paul Brook brook.p...@gmail.com:
   Hi all,
  
   I am attempting to build

Re: [WiX-users] FormatSize attribute of text control

2011-03-31 Thread Tobias S

You could use a custom action to generate such a string out of the
property PrimaryVolumeSpaceRequired.


2011/3/31 Pally Sandher pally.sand...@iesve.com:
 MSDN appears to say you can't. See
 http://msdn.microsoft.com/en-gb/library/aa368608.aspx

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

 http://www.iesve.com
 **Design, Simulate + Innovate with the Virtual Environment**
 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: Sergey [mailto:sh0...@gmail.com]
 Sent: 31 March 2011 07:35
 To: General discussion for Windows Installer XML toolset.
 Subject: [WiX-users] FormatSize attribute of text control

 Hi,

 I added this element to my CustomizeDlg:
 Control Id=PrimaryVolumeSpaceRequiredText Type=Text X=220 Y=58
 Width=128 Height=20 Text=PrimaryVolumeSpaceRequired]
 FormatSize=yes /

 FormatSize works - i have a text in form 7533MB.

 But i need to have thousand separator in this number: 7,533MB. Is it
 possible?

 --
 Thank you!

 
 --
 Create and publish websites with WebMatrix Use the most popular FREE web
 apps or write code yourself; WebMatrix provides all the features you
 need to develop and publish your website.
 http://p.sf.net/sfu/ms-webmatrix-sf
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users



 --
 Create and publish websites with WebMatrix
 Use the most popular FREE web apps or write code yourself;
 WebMatrix provides all the features you need to develop and
 publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] DTF Transaction problem with x64 msi

2011-04-01 Thread Tobias S

The point here is that you are using a multi package transaction. So
the whole Install Execute transaction can run either as x86
transaction or x64 transaction if there are only x64 pacakges in
the transaction but not as combined one where x64 packages are treated
as they should (e.g. targeting  'C:\Program Files\' folder). Windows
Installer now seems to make the x64 packages compatible to x86
packages with the described result.

Read this issues a short time ago, think it was also in this mailing
list but don't find the link anymore.

In general I think as workaround you could separate the logic and use
a second transaction just for installing the x64 packages in your
bootstrapper.

Regards,
Tobias


2011/4/1 Douglas Mendizabal doug...@asna.com:
 I'm using an external UI to chain several msi files together.  I have an 
 ExternalUIHandler that is part of a WPF MVVM wizard application.  Most of the 
 msi files are 32bit (Intel platform) but one of them is a 64 bit (x64 
 platform, let's call it my-x64.msi) that contains both 32-bit and 64-bit 
 components.  The wizard app checks the operating system bitness and then 
 makes a list of the msi files that will be installed, so that the x64 msi is 
 only installed when running on a 64-bit OS.

 When I run the my-x64.msi by itself, the 64-bit components are correctly 
 installed into C:\Program Files\...  and the 32-bit components are installed 
 into C:\Program Files (x86)\...  However, when my-x64.msi is installed by the 
 External UI, the Windows Installer service treats it like a 32-bit MSI and 
 WIN64DUALFOLDERS hoses all components using ProgramFiles64Folder, so I end up 
 with all components in the C:\Program Files (x86)\... folder.

 From the MSI log when using the External UI:

 MSI (s) (9C:00) [16:00:24:038]: WIN64DUALFOLDERS: 'C:\Program Files (x86)\' 
 will substitute 17 characters in 'C:\Program Files\' folder path. (mask 
 argument = 0, the folder pair's iSwapAttrib member = 0).

 In the External UI, I'm using

 var installTransaction = new Transaction(myInstallTransaction, 
 TransactionAttributes.None);

 to start a muti-package transaction.  After that I'm using

                Installer.InstallProcut(pathToMsiString, propertiesString);

 for every MSI file, followed by

                installTransaction.Rollback();

 if any InstallProduct() call fails or is cancelled, or

                installTransaction.Commit();

 if they are all successful.  Am I missing something else here?  Or have I 
 stumbled upon a bug in DTF?

 Thanks,
 Douglas M.

 --
 Create and publish websites with WebMatrix
 Use the most popular FREE web apps or write code yourself;
 WebMatrix provides all the features you need to develop and
 publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Dialog to select a file type.

2011-04-03 Thread Tobias S

No unfortunately WiX ( and the underlying Windows Installer) doesn't
support that scenario to select a file. Only Folder is possible.This
requirement can be solved e.g. by a custom action in c# (+DTF) showing
such a dialog.

Or check the CA File Browse Dialog on
http://www.installsite.org/pages/en/msi/ca.htm.

Googling for wix dialog select file gives you additional discussions
about that topic and possible solutions.



2011/4/2 Uma Harano uhar...@esri.com:
 Hi,
 Is there a way to create a Browse dialog in the msi that will allow me to 
 pick a file? For instance, if I want a browse dialog to pick an existing 
 *.txt files only.
 Also, I need to create a Browse Dialog to save a file to path.
 I am reading that the Browse Dialog only allows you to select a path, but not 
 a file in the path,
 Thanks!
 Uma-
 --
 Create and publish websites with WebMatrix
 Use the most popular FREE web apps or write code yourself;
 WebMatrix provides all the features you need to develop and
 publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to implement tab control in a Dialog

2011-04-06 Thread Tobias S

Hmm... MSI still is not able to do so.

The ThmUtil is something completely new in WiX 3.6. I assume it is
used for modelling the Burn Bootstrapper UI (Schema for describing
Theme files processsed by thmutil is written in the help). But as it
is very new few information about it and how to use it is available
;-)

2011/4/6 Shal Philipp luc2...@inbox.ru:
Up the theme! )

here:
http://wix.sourceforge.net/releases/3.6.1230.0/history.txt

I have found this string:
MiCarls: Add ListView Tab control support to ThmUtil

does it mean that WIX will be able to support implementing tabs into install
UI? or maybe support already in 3.6.1230.0 version? (nothing in help file of
3.6.1230.0 version was found)

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-implement-tab-control-in-a-Dialog-tp3291570p6245419.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] [Wix-users] msi and combo box

2011-04-06 Thread Tobias S

So if I understand your requirements correctly you want to have a
combobox just for selecting a language for the license agreement?

That should be possible by adding a combobox e.g. on the first
installation scren and afterwards set a property for the selected
language and use this value for the language of the license agreement.
But to be honest from my point of view I'd recommend to localize the
complete UI and then the license agreement as well. E.g. all the
strings are already included in WiX and you only have to localize
additional ones.

Then build the lanugage transforms and create a bootstrapper to to
select the language. Alternatively you can use the approach to embed
transforms as it is descibed e.g. here:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multilanguage-install-td6161866.html

Regards
Tobias

2011/4/6 Thomazeau Michel neomichou...@gmail.com:
Hi Guys,

I have not found any infomation about using combo box ( the widget where you
can choose one item in a list ) with WIX.

My problem is about dynamic license text localization.

I have seen many post about creating multiple msi, one for each languages. I
have try this, in fact it work fine, all the ui that are produced are well
localized but this solution does not correspond to my needs, because it
induce to have one msi for every language (and I want to adress the msi to
16 different languages ...).

Another problem is that I don't care about the UI button or text
localization, the only thing I want to be translated is the license text
that appears in the second or third page of the installer.

And the easiest way to do that, from user point of view, is to have a
combobox where he can choose his language and that change the license text
field below.

Is there any way to do that with WIX?

Tanks a lot,

M.
--
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] [Wix-users] msi and combo box

2011-04-07 Thread Tobias S

HI,

Think this is a bit more tricky:

Control Id=LicenseText Type=ScrollableText X=20 Y=60
Width=330 Height=140 Sunken=yes TabSkip=no
Text SourceFile=!(wix.WixUILicenseRtf=$(var.licenseRtf)) /
/Control

adds the source file for the ScrollableText during binding of the
installation. Actually here you would need 3 different rtf files and
so you have to work around to populate the ScrollableText control.

At first glance it seems that you need some additional code to do so
(comp. http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg06828.html
)


Regards,
Tobias

2011/4/7 Thomazeau Michel neomichou...@gmail.com:
 Hi,

 I see your point Tobias, thanks for your quick answer. If the solution with
 the combo box doen't work/doesn't fit my expectation, I will go for the
 transform.


 I have a question about the combo box.


 I have set the combobox with its property and it seems to works fine
  Control Type=ComboBox Property=LANGUAGELIST Id=languageCombo
 Width=84 Height=16 X=30 Y=244 ComboList=yes RightToLeft=yes/
 ComboBox Property=LANGUAGELIST
            ListItem Text=English Value=1033 / !--or ListItem
 Text=English Value=English /--
            ListItem Text=Spanish Value=3082 /
            ListItem Text=Japanese Value=1041 /
          /ComboBox
 Property Id=LANGUAGELIST1033/Property !-- default value--


 but I don't see how to use this property to change the value of my
 ScrollableText dynamically.

  Control Id=AgreementText Type=ScrollableText X=20 Y=60 Width=330
 Height=140 Sunken=yes TabSkip=no
  Text SourceFile=EULA_English.rtf /
  /Control


 Just putting the properties in the field (Text
 SourceFile=EULA_[LANGUAGELIST].rtf/) doen't compile and it is normal.

 Do I need to go for a wix project variable? or a condition?


 Can someone help me to do that?


 Thanks


 Michel.
 --
 Xperia(TM) PLAY
 It's a major breakthrough. An authentic gaming
 smartphone on the nation's most reliable network.
 And it wants your games.
 http://p.sf.net/sfu/verizon-sfdev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WiX v3.5: Culture zh-HK ICE03 errors

2011-04-07 Thread Tobias S

Use zh-TW instead. Zh-HK is a known issue that localization is incorrerct:
http://sourceforge.net/tracker/?func=detailaid=3162829group_id=105970atid=642714
http://sourceforge.net/tracker/?func=detailaid=3163411group_id=105970atid=642714

zh-HK and zh-TW differ in few strings and my company uses zh-TW for
chinese traditional instead of the Hongkong one.

Regards,
Tobias



2011/4/7 Francisco Gabriel Malbrán fgmalb...@gmail.com:
 Whenever building my project in zh-HK culture I get the following errors
 (vs2008 sp3):

 Error 1 ICE03: Invalid template string; Table: Error, Column: Message,
 Key(s): 1306
 C:\delivery\Dev\wix35_public\src\ext\UIExtension\wixlib\ErrorProgressText.wxs
 120 1 IFRInstaller
 Error 2 ICE03: Invalid template string; Table: Error, Column: Message,
 Key(s): 1307
 C:\delivery\Dev\wix35_public\src\ext\UIExtension\wixlib\ErrorProgressText.wxs
 121 1 IFRInstaller
 Error 3 ICE03: Invalid template string; Table: Error, Column: Message,
 Key(s): 1312
 C:\delivery\Dev\wix35_public\src\ext\UIExtension\wixlib\ErrorProgressText.wxs
 126 1 IFRInstaller
 Error 4 ICE03: Invalid template string; Table: Error, Column: Message,
 Key(s): 1605
 C:\delivery\Dev\wix35_public\src\ext\UIExtension\wixlib\ErrorProgressText.wxs
 169 1 IFRInstaller
 Error 5 ICE03: Invalid template string; Table: Error, Column: Message,
 Key(s): 1609
 C:\delivery\Dev\wix35_public\src\ext\UIExtension\wixlib\ErrorProgressText.wxs
 173 1 IFRInstaller
 Error 6 ICE03: Invalid template string; Table: Error, Column: Message,
 Key(s): 1702
 C:\delivery\Dev\wix35_public\src\ext\UIExtension\wixlib\ErrorProgressText.wxs
 175 1 IFRInstaller
 Error 7 ICE03: Invalid template string; Table: Error, Column: Message,
 Key(s): 1703
 C:\delivery\Dev\wix35_public\src\ext\UIExtension\wixlib\ErrorProgressText.wxs
 176 1 IFRInstaller
 Error 8 ICE03: Invalid template string; Table: Error, Column: Message,
 Key(s): 1711
 C:\delivery\Dev\wix35_public\src\ext\UIExtension\wixlib\ErrorProgressText.wxs
 184 1 IFRInstaller
 Error 9 ICE03: Invalid template string; Table: Error, Column: Message,
 Key(s): 1803
 C:\delivery\Dev\wix35_public\src\ext\UIExtension\wixlib\ErrorProgressText.wxs
 208 1 IFRInstaller
 Error 10 ICE03: Invalid template string; Table: Error, Column: Message,
 Key(s): 1804
 C:\delivery\Dev\wix35_public\src\ext\UIExtension\wixlib\ErrorProgressText.wxs
 209 1 IFRInstaller

 This only happens for this culture and not for zh-TW for example.

 After some research I found this:
 http://blogs.msdn.com/b/heaths/archive/2009/02/13/why-does-ice03-state-my-localized-template-string-is-invalid.aspx

 saying that I would have to escape '[' characters in certain parts of the
 translation.

 Does this mean that the WixUI_zh-HK.wxl file from WiX source is incorrect
 and I would need to change it? or is there any way to workaround this?

 *funny thing: the zh-HK installer gets created anyway, yet it stops the
 build process for other cultures.

 Thanks
 --
 Xperia(TM) PLAY
 It's a major breakthrough. An authentic gaming
 smartphone on the nation's most reliable network.
 And it wants your games.
 http://p.sf.net/sfu/verizon-sfdev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Wix installers and Continuous Integration

2011-04-12 Thread Tobias S

Hm interesting point. The term CD I hear for the first time. When I
understand it correctly this means to deploy to the customers as
frequent as possible.

Back to CI: Imho here the whole company (team) testing strategy should
be taken into account. One aspect of CI are short builds and some unit
tests to give fast feedback after check in.

But CI also means e.g. nightly builds where definitely Installation
should be considered. Here also some testing might be possible like
pushing the installation on virtual machines and run UI tests based on
the complete system. Also possible mixed strategies where e.g. every
10th check in scedules a complete build with test runs of the
installed applications on VMs.

Additionally WiX offers a great way to involve developers into
installation development. So they are able to maintain the
installation (or at least do common tasks) which helps for agile
development as they gain better understanding of installers. based on
this understanding it is easier to keep the installations up to
date...

Back to Windows Installer packages. Installation also should act like
in real world. For servicing installations I consider major upgrades
as best strategy with fewest possible erors. If that can be archived
with few effort in your CI I'd recommend that with major upgrade of
all previous installers.

Regards
Tobias



2011/4/12 Christopher Painter chr...@deploymentengineering.com:
 I think I've seen some suggest that CI shouldn't include deployment as 
 there's also another term out there called Continous Deployment... different 
 book :-)

 Some in the CI camp say the CI build must be really fast and light weight.  
 Unit tests only, nothing to do with integration/deployment and it should be 
 done in less then 10 minutes, the faster the better.

 I'd say that whatever we call this thing,  when it comes to doing CI/CD for 
 your installers,  whatever servicing strategy you plan on doing in production 
 you should do in dev/test to get max test coverage of your deployment 
 solution.   Prototype it out and see if the performance is acceptable or if 
 you have pain that's not tolerable.

 ---
 Christopher Painter, Author of Deployment Engineering Blog
 Have a hot tip, know a secret or read a really good thread that deserves 
 attention? E-Mail Me

 From: Nick Porter porter.nicho...@gmail.com
 To: wix-users@lists.sourceforge.net
 Sent: Tuesday, April 12, 2011 8:23 AM
 Subject: Re: [WiX-users] Wix installers and Continuous Integration

 I have developed Wix installers in the past using the minor upgrade
 route but have recently changed to major upgrades to allow for easy
 double click upgrades. A couple reasons we wanted to do this was:

   1) Preserve existing configuration files
   2) Preserve login and recovery options for our Windows Services

 My question is for those that have moved to Continuous Integration.
 With that model in place is it best to do a complete uninstall then
 install as if it's a fresh without preserving any configuration
 settings or can the upgrade model work along side the Continuous
 Integration model? If using an upgrade model is still a good idea then
 is a Major Upgrade preferred to the Minor Upgrade? As of this time we
 are planning on using Go for our CI tool. Thanks for your help!

 --
 Forrester Wave Report - Recovery time is now measured in hours and minutes
 not days. Key insights are discussed in the 2010 Forrester Wave Report as
 part of an in-depth evaluation of disaster recovery service providers.
 Forrester found the best-in-class provider in terms of services and vision.
 Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 --
 Forrester Wave Report - Recovery time is now measured in hours and minutes
 not days. Key insights are discussed in the 2010 Forrester Wave Report as
 part of an in-depth evaluation of disaster recovery service providers.
 Forrester found the best-in-class provider in terms of services and vision.
 Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
WiX-users

Re: [WiX-users] CopyFile with pattern doesn't copy files - it looks like it doesn't do anything at all!

2011-04-13 Thread Tobias S

Check out src\Setup\Msi\Lux.wxs or src\Setup\Msi\VStudio.wxs from wix
sources for a working sample:
Component Id=VSSchema2005
Guid=7150C0A6-5626-48B6-AA4C-671754E22706 KeyPath=yes Win64=no
Directory=TARGETDIR
   CopyFile Id=CopyWixSchema2005
DestinationProperty=VS2005_SCHEMAS_DIR FileId=wix.xsd /
   ...
/Component

At first glance Component/@Directory is sourcedir and
Component/CopyFile/@DestinationProperty destinationdir...


2011/4/13 Amber Scouras amber.scou...@thetradedesk.com:
 I'm using WiX 3.5 (an RC from late in 2010).

 My core problem is that I have an installer that needs to deploy the same 
 files to multiple Components.  In this thread on StackOverflow 
 (http://stackoverflow.com/questions/4941602/features-installed-to-different-locations-but-referencing-the-same-components),
  Rob Mensching states:

A Component can only be installed once via an MSI. Each Component can only be 
installed to a single Directory. To have the contents of a Component 
installed to two different locations, you either have to create another 
Component with the same content or try to use the CopyFile element to 
duplicate the content.

 The files are referenced in the .wxs via a .wxi include, which means their Id 
 properties are static.  I tried various methods of namespacing these Ids at 
 include time, but that didn't work for various reasons (I can go into these 
 if necessary, but would prefer not to for brevity).  So, for now, I've 
 eliminated the possibility of duplicating the File elements per Component.  
 That leaves me with just the CopyFile option.

 I created a new Component for the shared files that installs to its own 
 directory and I added a single CopyFile element (using a pattern of * in 
 the SourceName attribute) to each of the existing Components that should copy 
 the files.  The new Component installs correctly but, unfortunately, the 
 CopyFile elements seem to do nothing.  The files just don't copy.  In trying 
 to debug the issue, I installed with msiexec from the command line with full 
 logging (/lvx*) and could find no trace of relevant file copy logging.  
 Without any indication of what I'm doing wrong, I can't debug the problem and 
 I'm hoping somebody on this list can help me.  Here are the approaches I've 
 tried so far (none have worked):

 First Approach
 Use CopyFile's SourceDirectory and DestinationDirectory attributes with a 
 SourceName pattern.  Note that I've also tried with a pattern of *.*, a 
 pattern of .*, pattern of *.dll, and without a pattern (specifying a 
 single specific file to be copied), which also did not work.

      Directory Id =ROOT_INSTALL_DIR
        Directory Id =SERVICES_DIR Name =Services
          Directory Id=SHARED_BINARIES_DIR Name=Binaries
            Component Id=SharedBinaries 
 Guid=49779A88-652A-11E0-AE98-1EF2DFD72085
              ?include $(var.BUILD_DIR)\Shared.wxi ?
            /Component
          /Directory
          Directory Id =SERVICE_ONE_DIR Name=ServiceOne
            Component Id=ServiceOneComponent 
 Guid=C743A1E6-7E71-4196-979F-F3218421BCCE
              CopyFile Id=ServiceOneSharedBinaries 
 SourceDirectory=SHARED_BINARIES_DIR SourceName=* 
 DestinationDirectory=SERVICE_ONE_DIR/
            /Component
          /Directory
          !-- More services with similar CopyFile elements --
        /Directory
      /Directory

     Feature Id=SharedBinariesFeature Level=1
        ComponentRef Id=SharedBinaries /
      /Feature
      Feature Id=ServiceOneFeature Level=1
        ComponentRef Id=ServiceOneComponent/
      /Feature

 Second Approach
 Use SourceProperty and DestinationProperty attributes instead of the 
 *Directory attributes.

      Directory Id =ROOT_INSTALL_DIR
        Directory Id =SERVICES_DIR Name =Services
          Directory Id=SHARED_BINARIES_DIR Name=Binaries
            Component Id=SharedBinaries 
 Guid=49779A88-652A-11E0-AE98-1EF2DFD72085
              ?include $(var.BUILD_DIR)\Shared.wxi ?
            /Component
          /Directory
          Directory Id =SERVICE_ONE_DIR Name=ServiceOne
            Component Id=ServiceOneComponent 
 Guid=C743A1E6-7E71-4196-979F-F3218421BCCE
              CopyFile Id=ServiceOneSharedBinaries 
 SourceProperty=SHARED_BINARIES_DIR SourceName=* 
 DestinationProperty=SERVICE_ONE_DIR/
            /Component
          /Directory
          !-- More services with similar CopyFile elements --
        /Directory
      /Directory

     Feature Id=SharedBinariesFeature Level=1
        ComponentRef Id=SharedBinaries /
      /Feature
      Feature Id=ServiceOneFeature Level=1
        ComponentRef Id=ServiceOneComponent/
      /Feature

 Third Approach
 Explicitly create new properties with CustomActions and use those properties 
 in SourceProperty and DestinationProperty - this seemed silly and redundant, 
 but it appears that it worked in this thread 
 (http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CopyFile-doesn-t-work-td2592289.html).
   From the install log, I can tell

Re: [WiX-users] old unanswered question regarding to Dialog Close button

2011-04-27 Thread Tobias S

afaik not possible except for modal dialogs. Assume here Tramontana
shows such one.

By default this is not a possible requirement for Windows Installer.

Regards,
Tobias


2011/4/27 william lee wele...@gmail.com:
 Hi,
 I searched a lot online, but did not hit a result.
 The question is how the installer make the decision to enable or disable the
 dialog X(close) button on top right corner.
 There is no dialog attribute to control it, but sometimes it just disabled,
 for example:
 http://www.tramontana.co.hu/wix/lesson8.php#8.1
 The first sample dialog just have X button disabled.

 I have a requirement that want to disable this X button on the finish
 install dialog, no idea how to do it.
 Any one know some internal undocumented information? :)

 thanks,
 William L.
 --
 WhatsUp Gold - Download Free Network Management Software
 The most intuitive, comprehensive, and cost-effective network
 management toolset available today.  Delivers lowest initial
 acquisition cost and overall TCO of any competing solution.
 http://p.sf.net/sfu/whatsupgold-sd
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] old unanswered question regarding to Dialog Close button

2011-04-27 Thread Tobias S

hmmm ... just, by accident figured out something interesting. The [X]
seems to correspond with the [Cancel] Button. So when removing the
Cancel button the Dialog Close / [X] gets disabled. Unfortunately
this seems not be working for the ExitDialog.


2011/4/27 Tobias S tobias.s1...@gmail.com:
 afaik not possible except for modal dialogs. Assume here Tramontana
 shows such one.

 By default this is not a possible requirement for Windows Installer.

 Regards,
 Tobias


 2011/4/27 william lee wele...@gmail.com:
 Hi,
 I searched a lot online, but did not hit a result.
 The question is how the installer make the decision to enable or disable the
 dialog X(close) button on top right corner.
 There is no dialog attribute to control it, but sometimes it just disabled,
 for example:
 http://www.tramontana.co.hu/wix/lesson8.php#8.1
 The first sample dialog just have X button disabled.

 I have a requirement that want to disable this X button on the finish
 install dialog, no idea how to do it.
 Any one know some internal undocumented information? :)

 thanks,
 William L.
 --
 WhatsUp Gold - Download Free Network Management Software
 The most intuitive, comprehensive, and cost-effective network
 management toolset available today.  Delivers lowest initial
 acquisition cost and overall TCO of any competing solution.
 http://p.sf.net/sfu/whatsupgold-sd
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users



--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] old unanswered question regarding to Dialog Close button

Did a short test where [X] was enabled when disabling the Cancel
button. So seems to be disabled only when removing [Cancel] and not on
the ExitDialog...

2011/4/27 Blair os...@live.com:
 I'm curious: what happens if you include but disable the cancel button?

 -Original Message-
 From: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: Wednesday, April 27, 2011 5:13 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] old unanswered question regarding to Dialog Close
 button

 hmmm ... just, by accident figured out something interesting. The [X]
 seems to correspond with the [Cancel] Button. So when removing the
 Cancel button the Dialog Close / [X] gets disabled. Unfortunately
 this seems not be working for the ExitDialog.


 2011/4/27 Tobias S tobias.s1...@gmail.com:
 afaik not possible except for modal dialogs. Assume here Tramontana
 shows such one.

 By default this is not a possible requirement for Windows Installer.

 Regards,
 Tobias


 2011/4/27 william lee wele...@gmail.com:
 Hi,
 I searched a lot online, but did not hit a result.
 The question is how the installer make the decision to enable or disable
 the
 dialog X(close) button on top right corner.
 There is no dialog attribute to control it, but sometimes it just
 disabled,
 for example:
 http://www.tramontana.co.hu/wix/lesson8.php#8.1
 The first sample dialog just have X button disabled.

 I have a requirement that want to disable this X button on the finish
 install dialog, no idea how to do it.
 Any one know some internal undocumented information? :)

 thanks,
 William L.

 
 --
 WhatsUp Gold - Download Free Network Management Software
 The most intuitive, comprehensive, and cost-effective network
 management toolset available today.  Delivers lowest initial
 acquisition cost and overall TCO of any competing solution.
 http://p.sf.net/sfu/whatsupgold-sd
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users



 
 --
 WhatsUp Gold - Download Free Network Management Software
 The most intuitive, comprehensive, and cost-effective network
 management toolset available today.  Delivers lowest initial
 acquisition cost and overall TCO of any competing solution.
 http://p.sf.net/sfu/whatsupgold-sd
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


 --
 WhatsUp Gold - Download Free Network Management Software
 The most intuitive, comprehensive, and cost-effective network
 management toolset available today.  Delivers lowest initial
 acquisition cost and overall TCO of any competing solution.
 http://p.sf.net/sfu/whatsupgold-sd
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] VC++ reditributable questions

Maybe you should consider to use the VCRedist installer instead of the
merge module.

Actually that's not the recommended way as you e.g. have to run an
installer in InstallUI sequence but it works (saw it also e.g. in
OpenOffice installer). The recommended way for installing the VCRedist
installer would be using it in a bootstrapper app.

If you want to go the unofficial way with InstallUI maybe following
snippets help and can be modified easily for other VCRedist.exes:

2008 SP1 x86 vcredist_x86.exe:
  !-- Microsoft Visual C++ 2008 SP1 x86 Redistributable (9.0.30729)  --
  Property Id=VC2008SP1REDIST_X86 Secure=yes
RegistrySearch Id=VC2008SP1REDIST_X86Value Root=HKLM
Key=SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{9A25302D-30C0-39D9-BD6F-21E6EC160475}
Name=Publisher Type=raw Win64=no /
  /Property
  CustomAction Id=Install_2008SP1VCredist.x86 Impersonate=yes
Return=check Execute=immediate BinaryKey=vc2008SP1Redist_x86.exe
ExeCommand=/qb/
  Binary Id=vc2008SP1Redist_x86.exe
SourceFile=$(sys.SOURCEFILEDIR)\vcredist_x86.exe/
  InstallUISequence
Custom Action=Install_2008SP1VCredist.x86
After=ProgressDlgNot Installed And Not VC2008SP1REDIST_X86/Custom
  /InstallUISequence

or for 2010 SP1 x86 vcredist_x86.exe as it cannot be installed anymore
side by side as 2005 and 2008 VCRedists:
  !-- Microsoft Visual C++ 2010 Redistributable (10.0.40219)  --
  !-- FindRelatedProducts is used to detect if a VCREdist 2010 x86
with the given version is already installed --
  Upgrade Id='{1F4F1D2A-D9DA-32CF-9909-48485DA06DD5}'
UpgradeVersion
 OnlyDetect='yes'
 Property='VC2010SP1REDIST_X86'
 Minimum='10.0.40219'
 IncludeMinimum='yes'/
  /Upgrade
  CustomAction Id=Install_2010SP1VCredist.x86 Impersonate=yes
Return=check Execute=immediate BinaryKey=vc2010SP1Redist_x86.exe
ExeCommand=/passive /norestart/
  Binary Id=vc2010SP1Redist_x86.exe
SourceFile=$(sys.SOURCEFILEDIR)\vcredist_x86.exe/
  InstallUISequence
Custom Action=Install_2010SP1VCredist.x86
After=ProgressDlgNot Installed And Not VC2010SP1REDIST_X86/Custom
  /InstallUISequence



2011/4/27 Wilson, Phil phil.wil...@invensys.com:
 A merge module is merged into your MSI and becomes part of it, so you'll 
 never find any evidence of VC runtime in Add/Remove Programs. If the VC++ 
 files are already installed then yours won't be, perhaps subject to file 
 version replacement rules, but if it's in the WinSxS folder you may see 
 multiple version of the VC++ files.

 I'm not sure that there are any registry entries for the VC files. You could 
 install with a verbose log and see what happens to the VC++ files, and look 
 in Windows\WinSxS for new files. And is that feature really being installed?  
 I also don't think the files will actually go into TARGETDIR from meerge 
 modules, just in case you were looking there.

 Phil Wilson

 -Original Message-
 From: Francisco Gabriel Malbrán [mailto:fgmalb...@gmail.com]
 Sent: Wednesday, April 27, 2011 10:48 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: [WiX-users] VC++ reditributable questions

 Hello.

 First: the context: WiX v3.5, Windows 7 Enterprise

 I'm intending to install the VC++ 9.0 redistributable from it's msm as
 described in WiX's official documentation page [0]
 Yet, even when my msi size augments in the same size as the msm and I can
 see with Orca entrances related to the msm, I think it does not get
 installed.

 What I've done in my code is:
 !-- VC++ redistributable dependence --
 DirectoryRef Id=TARGETDIR
      Merge Id=VCRedist
 SourceFile=$(var.DependencesDir)Microsoft_VC90_CRT_x86.msm DiskId=1
 Language=0/
 /DirectoryRef

 Feature Id=VCRedist Title=Visual C++ 9.0 Runtime AllowAdvertise=no
 Display=hidden Level=1
        MergeRef Id=VCRedist/
 /Feature

 The code compiles and throws some warnings as expected and detailed in the
 documentation. It does however, throw some other errors[1] but I've searched
 the web and found that these are also expected from using mergemod.dll[2]

 Whenever installing, however, I can't find any evidence that the VC++
 redistributable package has been installed. I don't find it in Add/Remove
 programs. I don't find registry keys associated with it. Etc.
 1. Is this the correct way to check?
 2. What can I do if in fact, the package is not being installed? (I need
 some hint on where to look now)

 Thanks in advance.

 [0]
 http://wix.sourceforge.net/manual-wix3/install_vcredist.htm

 [1]
 light.exe(0,0): warning LGHT1076: ICE82: This action
 SystemFolder.21022.08.Microsoft_VC90_CRT_x86.RTM.0138F525_6C8A_333F_A105_14AE030B9A54
 has duplicate sequence number 2 in the table InstallUISequence
 1light.exe(0,0): warning LGHT1076: ICE82: This action
 SystemFolder.21022.08.Microsoft_VC90_CRT_x86.RTM.0138F525_6C8A_333F_A105_14AE030B9A54
 has duplicate sequence number 2 in the table AdminUISequence
 1light.exe(0,0): warning LGHT1076: ICE82: This action

Re: [WiX-users] VC++ redistributable questions

Hi,

Yes I know the issues mentioned in MSDN about concurrent installers.
But for the VCRedist.exe there were no issues at our customers site
related to this implementation. For OpenOffice I mentioned it as it
was the first package where I saw other engineers doing the same
approach. I didn't want to state that this is the fact for concurrent
installations to be safe.

IMHO this approach is worth mentioning it in case of the VCRedist:
- VCRedist.exe is an installer which never caused any trouble itself
- No need doing bootstrapping for VCRedist.exe
- With this implementation the VCRedist installer runs at a point
where the user can run the installation unattended (for bootstrapper
normally waiting until completion necessary - not considering Burn
here as it is in beta)
- Most installs run in UI mode, otherwise also for InstallExecute a
condition could be integrated. Same scenario must be considered when
designing an installer with a bootstrapper

Cons:
- Elevation necessary to get only one UAC prompt

If there exists a good bootstrapper for implementing it in a chaining
way I think to re-implement it that way.

Regards
Tobias


PS: I know this approach is somehow quick-and-dirty and not MSDN
compliant ... but it does a good job ...



2011/4/28 Pally Sandher pally.sand...@iesve.com:
 Yeah if OpenOffice use concurrent installations it must be totally 
 safe http://msdn.microsoft.com/en-us/library/aa368010.aspx

 Stick with using the merge modules and/or a bootstrapper for the vcredist. If 
 you don't need to bootstrap any other pre-reqs the merge modules are the 
 easiest way to go.

 Here's how you test whether the merge modules install properly - 
 http://www.joyofsetup.com/2007/09/24/test-your-setups-virtually/
 Get yourself a Virtual Machine of any operating system your software 
 supports. Don't install anything on it other than Windows Updates. Install 
 your app using the MSI with the merge modules. If it runs, they installed 
 properly. If you're really worried about the magic voodoo which is making 
 your application run, go look in the WinSXS directories  see if the runtimes 
 have been installed. The VC++ 8.0 merge modules put some registry values 
 under SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Installations so 
 open your MSI in InstEd!/Orca, check the registry table  look for entries 
 with components which don't match any you've authored to see if the v9.0 ones 
 do too.

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

 http://www.iesve.com
 **Design, Simulate + Innovate with the Virtual Environment**
 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: Tobias S [mailto:tobias.s1...@gmail.com]
 Sent: 28 April 2011 08:47
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] VC++ reditributable questions

 Maybe you should consider to use the VCRedist installer instead of the
 merge module.

 Actually that's not the recommended way as you e.g. have to run an
 installer in InstallUI sequence but it works (saw it also e.g. in
 OpenOffice installer). The recommended way for installing the VCRedist
 installer would be using it in a bootstrapper app.

 If you want to go the unofficial way with InstallUI maybe following
 snippets help and can be modified easily for other VCRedist.exes:

 2008 SP1 x86 vcredist_x86.exe:
  !-- Microsoft Visual C++ 2008 SP1 x86 Redistributable (9.0.30729)  --
  Property Id=VC2008SP1REDIST_X86 Secure=yes
    RegistrySearch Id=VC2008SP1REDIST_X86Value Root=HKLM
 Key=SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{9A25302D-30C0-39D9-BD6F-21E6EC160475}
 Name=Publisher Type=raw Win64=no /
  /Property
  CustomAction Id=Install_2008SP1VCredist.x86 Impersonate=yes
 Return=check Execute=immediate BinaryKey=vc2008SP1Redist_x86.exe
 ExeCommand=/qb/
  Binary Id=vc2008SP1Redist_x86.exe
 SourceFile=$(sys.SOURCEFILEDIR)\vcredist_x86.exe/
  InstallUISequence
    Custom Action=Install_2008SP1VCredist.x86
 After=ProgressDlgNot Installed And Not VC2008SP1REDIST_X86/Custom
  /InstallUISequence

 or for 2010 SP1 x86 vcredist_x86.exe as it cannot be installed anymore
 side by side as 2005 and 2008 VCRedists:
  !-- Microsoft Visual C++ 2010 Redistributable (10.0.40219)  --
  !-- FindRelatedProducts is used to detect if a VCREdist 2010 x86
 with the given version is already installed --
  Upgrade Id='{1F4F1D2A-D9DA-32CF-9909-48485DA06DD5}'
    UpgradeVersion
         OnlyDetect='yes'
         Property='VC2010SP1REDIST_X86'
         Minimum='10.0.40219'
         IncludeMinimum='yes'/
  /Upgrade
  CustomAction Id=Install_2010SP1VCredist.x86 Impersonate=yes
 Return=check Execute=immediate BinaryKey=vc2010SP1Redist_x86.exe
 ExeCommand=/passive /norestart/
  Binary Id=vc2010SP1Redist_x86.exe
 SourceFile=$(sys.SOURCEFILEDIR

Re: [WiX-users] VC++ redistributable questions

Thanks for your feedback.

I used the InstallUI sequence to install the VCRedist.exe and did
nothing in InstallExecute sequence. So actually my implementation can
lead to an installed product without installed VCRedist when user runs
in /qn.

When writing

 - Most installs run in UI mode, otherwise also for InstallExecute a
 condition could be integrated. Same scenario must be considered when
 designing an installer with a bootstrapper


I thought of

CustomAction Id='NoVCRedist' Error=No VCRedist ... detected /
InstallExecuteSequence
  Custom Action='NoVCRedist' After='LaunchConditions'Not Installed
And Not VC2010REDIST_X86/Custom
/InstallExecuteSequence

I didn't think of installing another MSI in InstallExecute sequence.
Sorry for the misunderstanding.

Right now I also mentioned that properties are not re-evaluated when
FindRelatedProducts is called in InstallUISequence and
InstallExecuteSequence. So a set property CA must be implemented...



2011/4/28 Bob Arnson b...@joyofsetup.com:
 On 28-Apr-11 09:52, Tobias S wrote:
 - With this implementation the VCRedist installer runs at a point
 where the user can run the installation unattended (for bootstrapper
 normally waiting until completion necessary - not considering Burn
 here as it is in beta)
 - Most installs run in UI mode, otherwise also for InstallExecute a
 condition could be integrated. Same scenario must be considered when
 designing an installer with a bootstrapper

 Neither of these is the case: Unattended installs skip the UI sequence
 so anything done only in the UI sequence is also skipped. And you cannot
 run another installer from the execute sequence; that requires a chainer.

 PS: I know this approach is somehow quick-and-dirty and not MSDN
 compliant ... but it does a good job ...

 There's nothing wrong with quick, but dirty and unsupported are bad news.

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


 --
 WhatsUp Gold - Download Free Network Management Software
 The most intuitive, comprehensive, and cost-effective network
 management toolset available today.  Delivers lowest initial
 acquisition cost and overall TCO of any competing solution.
 http://p.sf.net/sfu/whatsupgold-sd
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] VC++ redistributable questions

Assumption based on personal experience as we ran at least the last 4
years the VCRedist during InstallUI. We nerver got customer issues
regarding a missing VC runtime. This would be expected when they run
unattended as there is (was) no abort criteria during InstallExecute
when no VCRedist installed.


2011/4/28 Jeremy Farrell jfarr...@pillardata.com:
 From: Tobias S [mailto:tobias.s1...@gmail.com]

 ...

 - Most installs run in UI mode

 Interesting, where did you get that information from? What's the ratio 
 between UI-mode runs and silent, and how accurate is the estimate believed to 
 be?
 --
 WhatsUp Gold - Download Free Network Management Software
 The most intuitive, comprehensive, and cost-effective network
 management toolset available today.  Delivers lowest initial
 acquisition cost and overall TCO of any competing solution.
 http://p.sf.net/sfu/whatsupgold-sd
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] VC++ redistributable questions

=Install_2010VCredist.x86Not Installed And Not
VC2010REDIST_X86/Custom
  /InstallUISequence

  !-- Throw an error in InstallExecute when no VCRedist is detected
by FindRelatedProducts --
  CustomAction Id='Install_2010VCredist.x86_Error' Error=Microsoft
Visual C++ 2010 x86 Redistributable (RTM - 10.0.30319) or higher not
installed /
  InstallExecuteSequence
Custom Action='Install_2010VCredist.x86_Error'
After='LaunchConditions'Not Installed And Not
VC2010REDIST_X86/Custom
  /InstallExecuteSequence
/Include

- End: VC2010Redist_x86.wxi -

2011/4/28 Tobias S tobias.s1...@gmail.com:
 Assumption based on personal experience as we ran at least the last 4
 years the VCRedist during InstallUI. We nerver got customer issues
 regarding a missing VC runtime. This would be expected when they run
 unattended as there is (was) no abort criteria during InstallExecute
 when no VCRedist installed.


 2011/4/28 Jeremy Farrell jfarr...@pillardata.com:
 From: Tobias S [mailto:tobias.s1...@gmail.com]

 ...

 - Most installs run in UI mode

 Interesting, where did you get that information from? What's the ratio 
 between UI-mode runs and silent, and how accurate is the estimate believed 
 to be?
 --
 WhatsUp Gold - Download Free Network Management Software
 The most intuitive, comprehensive, and cost-effective network
 management toolset available today.  Delivers lowest initial
 acquisition cost and overall TCO of any competing solution.
 http://p.sf.net/sfu/whatsupgold-sd
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users



--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] VC++ reditributable questions

Hi Phil,

there was a ongoing discussion about the topic and think somebody used
another subject and therefore googlemail started a new thread. There
is some additional information.

Regarding the VCredist I think that could be an alternative option to
the merge modules as stated in
http://msdn.microsoft.com/en-us/library/ms235316.aspx . The ongoing
discussion in the Follow-Up thread includes some statements about both
ways (Merge modules and VCRedist.exe). Uninstall: When installing the
VCredist I don't care about uninstall and leave it installed like I
think all vendors do. Think there exists also a comment in appwiz.cpl
in one of the columns not to uninstall it. It just stays permanent as
these installers have no shared counter concept.

Same do other vendors like e.g. Microsoft (Visual Studio as example)
do it with parts of their applications as uninstall might become too
complex...

Regards,
Tobias

2011/4/29 Francisco Gabriel Malbrán fgmalb...@gmail.com:
Thanks Phil Tobias.
I've followed Phil advice and checked out the WinSxS folder. There the
installer modified as recommended in the WiX 3.5 documentation does create
files that seem related to VC++ redistributable.
I actually took an empty VM without the redistributable and installed the
app. The code that depended con the redistributable seemed to run well.

Tobias, Why you say I need to consider using the .exe installer? So that it
would do a clean install of the redistributable? Also I believe there
could be some trouble handling uninstall since it would be hard to determine
whether the redistributable should be uninstalled too (and in that case, we
would need to make some magic to uninstall it right?)

Thanks both for your time and advice.

Francisco

2011/4/28 Tobias S tobias.s1...@gmail.com

Maybe you should consider to use the VCRedist installer instead of the
merge module.

Actually that's not the recommended way as you e.g. have to run an
installer in InstallUI sequence but it works (saw it also e.g. in
OpenOffice installer). The recommended way for installing the VCRedist
installer would be using it in a bootstrapper app.

If you want to go the unofficial way with InstallUI maybe following
snippets help and can be modified easily for other VCRedist.exes:

2008 SP1 x86 vcredist_x86.exe:
!-- Microsoft Visual C++ 2008 SP1 x86 Redistributable (9.0.30729) --
Property Id=VC2008SP1REDIST_X86 Secure=yes
RegistrySearch Id=VC2008SP1REDIST_X86Value Root=HKLM

Key=SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{9A25302D-30C0-39D9-BD6F-21E6EC160475}
Name=Publisher Type=raw Win64=no /
/Property
CustomAction Id=Install_2008SP1VCredist.x86 Impersonate=yes
Return=check Execute=immediate BinaryKey=vc2008SP1Redist_x86.exe
ExeCommand=/qb/
Binary Id=vc2008SP1Redist_x86.exe
SourceFile=$(sys.SOURCEFILEDIR)\vcredist_x86.exe/
InstallUISequence
Custom Action=Install_2008SP1VCredist.x86
After=ProgressDlgNot Installed And Not VC2008SP1REDIST_X86/Custom
/InstallUISequence

or for 2010 SP1 x86 vcredist_x86.exe as it cannot be installed anymore
side by side as 2005 and 2008 VCRedists:
!-- Microsoft Visual C++ 2010 Redistributable (10.0.40219) --
!-- FindRelatedProducts is used to detect if a VCREdist 2010 x86
with the given version is already installed --
Upgrade Id='{1F4F1D2A-D9DA-32CF-9909-48485DA06DD5}'
UpgradeVersion
OnlyDetect='yes'
Property='VC2010SP1REDIST_X86'
Minimum='10.0.40219'
IncludeMinimum='yes'/
/Upgrade
CustomAction Id=Install_2010SP1VCredist.x86 Impersonate=yes
Return=check Execute=immediate BinaryKey=vc2010SP1Redist_x86.exe
ExeCommand=/passive /norestart/
Binary Id=vc2010SP1Redist_x86.exe
SourceFile=$(sys.SOURCEFILEDIR)\vcredist_x86.exe/
InstallUISequence
Custom Action=Install_2010SP1VCredist.x86
After=ProgressDlgNot Installed And Not VC2010SP1REDIST_X86/Custom
/InstallUISequence

2011/4/27 Wilson, Phil phil.wil...@invensys.com:
A merge module is merged into your MSI and becomes part of it, so you'll
never find any evidence of VC runtime in Add/Remove Programs. If the VC++
files are already installed then yours won't be, perhaps subject to file
version replacement rules, but if it's in the WinSxS folder you may see
multiple version of the VC++ files.

I'm not sure that there are any registry entries for the VC files. You
could install with a verbose log and see what happens to the VC++ files, and
look in Windows\WinSxS for new files. And is that feature really being
installed? I also don't think the files will actually go into TARGETDIR
from meerge modules, just in case you were looking there.

Phil Wilson

-Original Message-
From: Francisco Gabriel Malbrán [mailto:fgmalb...@gmail.com]
Sent: Wednesday, April 27, 2011 10:48 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] VC++ reditributable questions

Hello.

First: the context: WiX v3.5, Windows 7

Re: [WiX-users] localized installer

Hi Helge,

Please consider e.g.
http://www.installsite.org/pages/en/msi/articles/embeddedlang/index.htm
(also available in German ;-) ). There is discussed an approach
without bootstrapper (think also with a discussion about the needed
transform generation):
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multilanguage-install-td6161866.html#none

Additionally maybe this link is helpful:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Dynamically-set-WixVariable-WixUILicenseRtf-td6039979.html#none

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix-users-f687560.html
btw. offers a good way to search this mailinglist ...

For a bootstrapper consider DotNetInstaller
(http://dotnetinstaller.codeplex.com/)

Best regards / Schöne Grüße
Tobias

2011/4/29 Helge Kruse helge.kruse-nos...@gmx.net:
Hello,

I know that a MSI file can handle only one locale. So I need a bootstrapper
to select a MSI file on customer's choise. Where can I find information, how
this can be done with WiX? I assume this can be a frequently asked question.

Thanks,
Helge

--
NEU: FreePhone - kostenlos mobil telefonieren und surfen!
Jetzt informieren: http://www.gmx.net/de/go/freephone

--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Wizard activates even though I installed the drivers via WIX Installer.

The described behavior sounds familiar. Assume the device driver is
not WHQL signed.For Win XP there is no workaround and you have a) do
the WHQL certification b) accept the situation with the driver
wizzard.

Also there should be a dialog Windows can't verify the publisher of
this driver for Win 7 (comp.
http://www.bing.com/images/search?q=windows+cannot+verify+the+publisher+of+this+driver+softwarego=form=QBIRqs=nsk=
). This dialog (Only Win 7 not sure if Vista as well) can be
eleminated by signing the device driver with a cross certificate (
driver dll + exe):
Signtool sign /v /ac C:\...\CrossCertificate\MyCrossCertificate.cer
/f c:\...\MyPFXFile.pfx /p PASSWORD /n COMPANYNAME /t
http://timestamp.verisign.com/scripts/timestamp.dll FileToSign

As you described nothing on windows 7 I assume already cross signed the files...



2011/4/28 Orlando javier.rami...@gmail.com:
 Hi to all,

 I am currently Installing drivers via WIX for Windows XP 32 bit.  The
 installer runs fine. My question is... once I connect my device. Windows XP
 runs a wizard... and tries to install the drivers for the device. It
 shouldn't do that. It should just recognized the device and say is ready to
 go... avoiding to run a wizard.   Probably I am doing something wrong
  If I run the same installer for windows 7, I don't get the wizard problem.
 It just detects the device and works.

 Does anyone know why this happens?

 I am adding the code here, maybe I am doing something wrong for Windows XP
 32 bit.
 ---
 ?xml version=1.0 encoding=UTF-8?
 Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
     xmlns:difx=http://schemas.microsoft.com/wix/DifxAppExtension;
 Product Id=1d68897d-fa74-49c7-9caf-17c25a0bd4ac
           Name=FlexInstaller_x32
           Language=1033
           Version=1.0.0.0
           Manufacturer=FlexComputing
           UpgradeCode=4f4b4a19-65da-4572-852f-9b87fbf3b3bf

 Package InstallerVersion=200 Compressed=yes /

    MajorUpgrade DowngradeErrorMessage=A newer version already installed
 /

 Media Id=1 Cabinet=FlexInstaller_x32.cab EmbedCab=yes /

    Icon Id=Flex_icon.exe
 SourceFile=..\FlexInstaller_x32\_files\Flex_icon.ico /
    Property Id=ARPPRODUCTICON Value=Flex_icon.exe /
    Property Id=ALLUSERS Value=1 /

    Directory Id=TARGETDIR Name=SourceDir
 Directory Id=ProgramFilesFolder
 Directory Id=INSTALLLOCATION Name=FlexInstaller_Drivers
          Directory Id=INSTALLLOCATION1 Name=FlexInstaller_Usb

            Component Id=USB_Component
 Guid=6be53a8c-a078-4e7a-a93c-129275f071f5

              File Id=WdfCoInstaller01007.dll
 Name=WdfCoInstaller01007.dll DiskId=1
 Source=..\FlexInstaller_x32\_files\i386\WdfCoInstaller01007.dll
 Vital=yes /
              File Id=WinUSBCoInstaller.dll Name=WinUSBCoInstaller.dll
 DiskId=1 Source=..\FlexInstaller_x32\_files\i386\WinUSBCoInstaller.dll
 Vital=yes /
              File Id=Android_Winusb_X32.inf
 Name=Android_Winusb_X32.inf DiskId=1
 Source=..\FlexInstaller_x32\_files\Android_Winusb_X32.inf Vital=yes  /
              File Id=Androidwinusb86.cat Name=Androidwinusb86.cat
 DiskId=1 Source=..\FlexInstaller_x32\_files\Androidwinusb86.cat
 Vital=yes /

              difx:Driver Legacy=yes /

              RemoveFolder Id=FlexInstaller_Usb On=uninstall/

              RegistryKey Id=FlexInstaller_UsbKey Root=HKLM
 Key=Software\Flextronics\FlexInstaller_Usb_x32
 Action=createAndRemoveOnUninstall
                RegistryValue Name=UsbInstaller Type=string
 Value=usb_driver_x32 /
                RegistryValue Name=Version Type=string Value=1.0.0.0
 /
              /RegistryKey

            /Component
          /Directory

          Directory Id=INSTALLLOCATION2 Name=FlexInstaller_Modem
            Component Id=Modem_Component
 Guid=f8af1cF8-17ba-468f-ab06-95af61112fb5

              File Id=Mousbser.sys Name=Mousbser.sys DiskId=1
 Source=..\FlexInstaller_x32\_files\android_modem_x86\Mousbser.sys
 Vital=yes /
              File Id=Momdm.inf Name=Momdm.inf DiskId=1
 Source=..\FlexInstaller_x32\_files\android_modem_x86\Momdm.inf
 Vital=yes/
              File Id=mousbser.cat Name=mousbser.cat DiskId=1
 Source=..\FlexInstaller_x32\_files\android_modem_x86\mousbser.cat
 Vital=yes /

              difx:Driver Legacy=yes/

              RemoveFolder Id=FlexInstaller_Modem On=uninstall/

              RegistryKey Id=FlexInstaller_ModemKey Root=HKLM
 Key=Software\Flextronics\FlexInstaller_Modem
 Action=createAndRemoveOnUninstall 
                RegistryValue Name=ModemInstaller Type=string
 Value=modem_driver_x32 /
                RegistryValue Name=Version Type=string Value=1.0.0.0
 /
              /RegistryKey

            /Component
          /Directory

 /Directory
 /Directory
 /Directory

 Feature Id=ProductFeature Title=FlexInstaller_x32 Level=1
      ComponentRef Id=USB_Component /
      ComponentRef Id=Modem_Component  /
 /Feature

    UIRef Id=WixUI_Minimal /
 /Product
 /Wix


 ---

 --
 ing. Javier Orlando Ramírez Martínez
 http://linux.mty.itesm.mx/~oramirez

Re: [WiX-users] Error 2726: Action not found: WelcomeForm

2011-05-02 Thread Tobias S

Hi,

maybe a bit late.. but better late then never ;-)

Got the issue when installing using reduced mode (msiexec /i
MySetup.msi /l*v MyLog.log /qr):

...
MSI (c) (74:0C) [07:19:07:760]: Doing action: WelcomeDlg
Action 7:19:07: WelcomeDlg.
Action start 7:19:07: WelcomeDlg.
DEBUG: Error 2726:  Action not found: WelcomeDlg
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2726. The arguments are: WelcomeDlg, ,
Action ended 7:19:07: WelcomeDlg. Return value 0.
...

MSI (c) (74:0C) [07:19:20:198]: Doing action: ExitDialog
Action 7:19:20: ExitDialog.
Action start 7:19:20: ExitDialog.
DEBUG: Error 2726:  Action not found: ExitDialog
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2726. The arguments are: ExitDialog, ,
Action ended 7:19:20: ExitDialog. Return value 0.


but not when installing the same package using normal UI (msiexec /i
MySetup.msi /l*v MyLogQR.log). For the product.wxs I just added

Property Id=WIXUI_INSTALLDIR Value=INSTALLLOCATION /
UIRef Id=WixUI_InstallDir/

and one component to a blank default Visual Studiu Setup Project Template.



Then did the same for a InstallShield 2010 Basic MSI project ... et voila:
...
MSI (c) (5C:18) [07:23:28:802]: Doing action: InstallWelcome
Action 7:23:28: InstallWelcome.
Action start 7:23:28: InstallWelcome.
Info 2726.Action not found: InstallWelcome.
Action ended 7:23:28: InstallWelcome. Return value 0.


MSI (c) (5C:18) [07:23:37:506]: Doing action: SetupCompleteSuccess
Action 7:23:37: SetupCompleteSuccess.
Action start 7:23:37: SetupCompleteSuccess.
Info 2726.Action not found: SetupCompleteSuccess.
Action ended 7:23:37: SetupCompleteSuccess. Return value 0.
...

Got the same error but with other logging as Info text.

So I assume it's some strange behavior in that case as no other issues
were detected and the log seems normal for both installers
(InstallShield one and WiX one)

Regards
Tobias


2010/9/3 Umesh Joglekar umesh_jogle...@hotmail.com:


 Hi,

 We have been seeing this error in our installs (both first time and repair 
 mode)

 Here is a relevant portion of the log.

 Action 14:15:27: ProgressForm. Dialog created
 DEBUG: Error 2726:  Action not found: WelcomeForm
 The installer has encountered an unexpected error installing this package. 
 This may indicate a problem with this package.
 The error code is 2726. The arguments are: WelcomeForm, ,
 Action ended 14:15:27: WelcomeForm. Return value 0.
 MSI (c) (E8:08) [14:15:27:527]: Doing action: ExecuteAction
 MSI (c) (E8:08) [14:15:27:572]: Note: 1: 2205 2:  3: ActionText
 Action 14:15:27: ExecuteAction.
 Action start 14:15:27: ExecuteAction.
 MSI (c) (E8:08) [14:15:27:751]: PROPERTY CHANGE: Adding SECONDSEQUENCE 
 property. Its value is '1'.
 MSI (c) (E8:08) [14:15:27:782]: Grabbed execution mutex.
 MSI (c) (E8:08) [14:15:27:808]: Incrementing counter to disable shutdown. 
 Counter after increment: 0

 Earlier in the log it is clear that all dialogs are found and created 
 successfully.

 Here is the earlier relevant portion of the log

 Action 14:15:18: WelcomeForm.
 Action start 14:15:18: WelcomeForm.
 Info 2898.For VsdDefaultUIFont.524F4245_5254_5341_4C45_534153783400 
 textstyle, the system created a 'MS Sans Serif' font, in 0 character set, of 
 13 pixels height.
 Info 2898.For TitleTextStyle textstyle, the system created a 'Arial' font, in 
 0 character set, of 22 pixels height.
 Info 2898.For SubTitleTextStyle textstyle, the system created a 'Arial' font, 
 in 0 character set, of 19 pixels height.
 Info 2898.For ButtonTextStyle textstyle, the system created a 'Arial' font, 
 in 0 character set, of 15 pixels height.
 Info 2898.For DescriptionTextStyle textstyle, the system created a 'Arial' 
 font, in 0 character set, of 16 pixels height.
 Info 2898.For SmallDescriptionTextStyle textstyle, the system created a 
 'Arial' font, in 0 character set, of 14 pixels height.
 Action 14:15:18: WelcomeForm. Dialog created

 WelcomeForm is shown and install completes successfully. There are no other 
 errors reported in the log.


 Similarly in the repair mode we get the error
 DEBUG: Error 2726:  Action not found: MaintenanceForm

 In the maintenance mode, MaintenanceForm is shown properly.

 There are no errors related to size of UI elements, bitmap paths etc.

 ORCA shows all dialogs in the dialog table.

 What could be the cause of this error. I have searched the forums but I have 
 not found any answer.
 Has anyone else seen similar behavior?

 WelcomeForm starts user interaction in install mode and MaintenanceForm does 
 it in the maintenance mode.

 WelcomeForm does not publish any DoAction events. It only publishes NewDialog 
 event for license dialog on next button push, or SpawnDialog event for cancel 
 button push spawning CancelDialog.

 Thanks

 Umesh

Re: [WiX-users] Localizing my setup

2011-05-07 Thread Tobias S

- Did you customize LicenseAgreementDlg.wxs accordingly ? A tutorial
to do so can be found here:
http://weblogs.sqlteam.com/mladenp/archive/2010/04/15/WiX-3-Tutorial-Custom-EULA-License-and-MSI-localization.aspx
(Or a german speaking blog
http://www.stummerweb.de/2009/wixuilicensertf-bei-mehrsprachigem-setup/
)
- Do the files LicEN.rtf and LicDE.rtf exist ? Try to reference a full
path for testing purposes (like e.g.
c:\MyFolder\WiX\LicenseAgreement\LicDE.rtf


Regards,
Tobias


2011/5/7 Helge Kruse helge.kruse-nos...@gmx.net:
 Hello,

 it's my first try to localize my setup. I am using WiX 3.5.

 The Product.wxs has these lines besides all others defining files etc.

 Product Id=ANY_GUID Name=Product Language=!(loc.LanguageId)
 Version=1.0.0.0 Manufacturer=Man UpgradeCode=ANY_GUID
 WixVariable Id=WixUILicenseRtf Value=!(loc.License) /
 /Product

 My localization files are:

 ?xml version=1.0 encoding=utf-8?
 WixLocalization Culture=en-us
 xmlns=http://schemas.microsoft.com/wix/2006/localization;
 String Id=LanguageId1033/String
 String Id=LicenseLicEN.rtf/String
 /WixLocalization

 ?xml version=1.0 encoding=utf-8?
 WixLocalization Culture=de-de
 xmlns=http://schemas.microsoft.com/wix/2006/localization;
 String Id=LanguageId1031/String
 String Id=LicenseLicDE.rtf/String
 /WixLocalization

 When running light.exe I get

 C:\delivery\Dev\wix35_public\src\ext\UIExtension\wixlib\LicenseAgreementDlg.wxs(35,0):
 error LGHT0103: The system cannot find the file '!(loc.License)'.

 The command line fpr light.exe arguments are
     -cultures:en-us
     -ext C:\Program Files (x86)\Windows Installer XML
 v3.5\bin\WixUIExtension.dll
     -ext C:\Program Files (x86)\Windows Installer XML
 v3.5\bin\WixNetFxExtension.dll
     -loc de-de.wxl
     -loc en-us.wxl
     -notidy
     -out bin\Release\en-us\Product.msi
     -pdbout bin\Release\en-us\Product.wixpdb
    -spdb
     obj\Release\Product.wixobj
     obj\Release\Product.Generated.wixobj

 Why does the linker resolves the !(loc.LanguageId) but fails with
 !(loc.License)?
 What should I do to localize the license file? The scheme above is taken
 from Nich Ramirez's book.

 Regards,
 Helge


 --
 WhatsUp Gold - Download Free Network Management Software
 The most intuitive, comprehensive, and cost-effective network
 management toolset available today.  Delivers lowest initial
 acquisition cost and overall TCO of any competing solution.
 http://p.sf.net/sfu/whatsupgold-sd
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Testing the UI

2011-05-11 Thread Tobias S

In general the given WiX translation should fit the UI already and I'd
consider only doing a short test of the given WiX translation. Maybe
check if the longest string (checked with Orca or InstEd in table
Error) fits. For the custom strings the same...

Regarding language placeholders and layout. Had an interesting
discussion with our guy from documentation and his recommendations
about needed space for the different languages. All values are
experience based may vary for certain strings.

His recommendations are: Calculating twice as much space as english
for a string placeholder should be ok. Russian seems to be the
language needing most space (approx. 1,9 as much as English), Spanish
and French follow thereafter with approx. 1,5 and German with 1,4.
Chinese for example is very short as they have few characters for
longer terms like e.g. 火车站 for train station...

Btw: User settings may lead to different Windows Installer layouts


2011/5/10 Francisco Gabriel Malbrán fgmalb...@gmail.com:
 Thank you very much Pally and Christopher.

 I am indeed intending to test texts  layout as part of the localization
 task. The information about Orca and InstEd was really helpful, I didn't
 know about that. However, it seem to not resolve the how to preview the
 ErrorDlg, since the message to be shown there may vary and the previewers
 (from Orca and from InstEd) show a generic text instead of any error text
 (makes sense). I've seen that I can manually replace that text there but I
 need something more straightforward for my localization team. I'm searching
 for a way to do this using these editors now.

 The information on testing installations with VMs was really interesting
 anyway. Thanks!

 Francisco Malbrán

 2011/5/10 Christopher Painter chr...@deploymentengineering.com

 As an aside, I also recommend Hyper-V.  It's also free and the latest R2
 SP1 adds the capabilities for dynamic memory allocation.  The advantage in
 Hyper-V to me is that it has much broader hardware support ( pretty much
 everything on the Windows HCL list ) where VMWare is more picky.

 For those with more money to spend,  hypervisors are pretty much commodity
 items now and the real magic is in the provisioning automation that you put
 around them.   At my day job we use a system called VMLogix Labmanager which
 allows me to create template and configurations for automating the
 deployment of all sorts of images.   If you are a TFS user then is also some
 pretty cool synergy between System Center Virtual Machine Manager and TFS.
 ( Think of a build that auto deploys a system, then some automated
 integration tests fail and a defect is automatically logged in the work item
 system.  Later a developer open the bug to work on it and he has the
 deployed VM available to him on the spot. )


 ---
 Christopher Painter, Author of Deployment Engineering Blog
 Have a hot tip, know a secret or read a really good thread that deserves
 attention? E-Mail Me

 --- On Tue, 5/10/11, Pally Sandher pally.sand...@iesve.com wrote:


 From: Pally Sandher pally.sand...@iesve.com
 Subject: Re: [WiX-users] Testing the UI
 To: General discussion for Windows Installer XML toolset. 
 wix-users@lists.sourceforge.net
 Date: Tuesday, May 10, 2011, 10:45 AM


 How do you mean test exactly? If you only want to check the text  layout
 of dialogs you can preview them using Orca or InstEd!
 The recommended approach for installation testing is to use virtual
 machines -
 http://www.joyofsetup.com/2007/09/24/test-your-setups-virtually/
 In addition to the products Bob A. recommends I'd add VMWare's ESXi (now
 known as vSphere Hypervisor) if you have hardware which it supports as it's
 pretty damn impressive as well as free.

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

 http://www.iesve.com
 **Design, Simulate + Innovate with the Virtual Environment**
 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: Francisco Gabriel Malbrán [mailto:fgmalb...@gmail.com]
 Sent: 09 May 2011 20:03
 To: General discussion for Windows Installer XML toolset.
 Subject: [WiX-users] Testing the UI

 Hello there.

 I've been struggling around this subject for some time now, and I'm
 wondering
 about the best approach to follow on achieving such objective.
 Right now, what I am thinking on is to mock all the installer by
 customizing
 the entire dialog set and placing all the dialogs one behind the other (so
 they
 can be tested on localization matters).Yet this is a partial solution
 because of
 all possible error messages. Besides makes me feel like a cave man
 intending
 to
 make fire :).

 Is there any recommended approach on the matter?

 Any previous experience story or custom approach would also be good :).

 Thanks in advance.

 --
 Francisco

Re: [WiX-users] Testing the UI

2011-05-12 Thread Tobias S

With settings affecting the layout I primarily mean settings affecting
the fonts. Play with things like
Windows XP:
Use large fonts

Windows 7:
DPI settings
Control Panel\Appearance and Personalization\Display - use larger here



2011/5/11 Francisco Gabriel Malbrán fgmalb...@gmail.com:
 Thanks Tobias. This is most interesting.
 I've got several custom texts that are not WiX's default, that's why I'm
 intending to test the layout.
 The information about languages and placeholders is pretty useful!

 Finally, I didn't quite get what user settings may affect the layout?

 Thanks

 2011/5/11 Tobias S tobias.s1...@gmail.com

 In general the given WiX translation should fit the UI already and I'd
 consider only doing a short test of the given WiX translation. Maybe
 check if the longest string (checked with Orca or InstEd in table
 Error) fits. For the custom strings the same...

 Regarding language placeholders and layout. Had an interesting
 discussion with our guy from documentation and his recommendations
 about needed space for the different languages. All values are
 experience based may vary for certain strings.

 His recommendations are: Calculating twice as much space as english
 for a string placeholder should be ok. Russian seems to be the
 language needing most space (approx. 1,9 as much as English), Spanish
 and French follow thereafter with approx. 1,5 and German with 1,4.
 Chinese for example is very short as they have few characters for
 longer terms like e.g. 火车站 for train station...

 Btw: User settings may lead to different Windows Installer layouts


 2011/5/10 Francisco Gabriel Malbrán fgmalb...@gmail.com:
  Thank you very much Pally and Christopher.
 
  I am indeed intending to test texts  layout as part of the localization
  task. The information about Orca and InstEd was really helpful, I didn't
  know about that. However, it seem to not resolve the how to preview the
  ErrorDlg, since the message to be shown there may vary and the previewers
  (from Orca and from InstEd) show a generic text instead of any error text
  (makes sense). I've seen that I can manually replace that text there but
 I
  need something more straightforward for my localization team. I'm
 searching
  for a way to do this using these editors now.
 
  The information on testing installations with VMs was really interesting
  anyway. Thanks!
 
  Francisco Malbrán
 
  2011/5/10 Christopher Painter chr...@deploymentengineering.com
 
  As an aside, I also recommend Hyper-V.  It's also free and the latest R2
  SP1 adds the capabilities for dynamic memory allocation.  The advantage
 in
  Hyper-V to me is that it has much broader hardware support ( pretty much
  everything on the Windows HCL list ) where VMWare is more picky.
 
  For those with more money to spend,  hypervisors are pretty much
 commodity
  items now and the real magic is in the provisioning automation that you
 put
  around them.   At my day job we use a system called VMLogix Labmanager
 which
  allows me to create template and configurations for automating the
  deployment of all sorts of images.   If you are a TFS user then is also
 some
  pretty cool synergy between System Center Virtual Machine Manager and
 TFS.
  ( Think of a build that auto deploys a system, then some automated
  integration tests fail and a defect is automatically logged in the work
 item
  system.  Later a developer open the bug to work on it and he has the
  deployed VM available to him on the spot. )
 
 
  ---
  Christopher Painter, Author of Deployment Engineering Blog
  Have a hot tip, know a secret or read a really good thread that deserves
  attention? E-Mail Me
 
  --- On Tue, 5/10/11, Pally Sandher pally.sand...@iesve.com wrote:
 
 
  From: Pally Sandher pally.sand...@iesve.com
  Subject: Re: [WiX-users] Testing the UI
  To: General discussion for Windows Installer XML toolset. 
  wix-users@lists.sourceforge.net
  Date: Tuesday, May 10, 2011, 10:45 AM
 
 
  How do you mean test exactly? If you only want to check the text 
 layout
  of dialogs you can preview them using Orca or InstEd!
  The recommended approach for installation testing is to use virtual
  machines -
  http://www.joyofsetup.com/2007/09/24/test-your-setups-virtually/
  In addition to the products Bob A. recommends I'd add VMWare's ESXi (now
  known as vSphere Hypervisor) if you have hardware which it supports as
 it's
  pretty damn impressive as well as free.
 
  Palbinder Sandher
  Software Deployment Engineer
  T: +44 (0) 141 945 8500
  F: +44 (0) 141 945 8501
 
  http://www.iesve.com
  **Design, Simulate + Innovate with the Virtual Environment**
  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: Francisco Gabriel Malbrán [mailto:fgmalb...@gmail.com]
  Sent: 09 May 2011 20:03
  To: General discussion for Windows Installer XML

Re: [WiX-users] Manually building a Votive project

2011-05-31 Thread Tobias S

Did you consider building it by a batch call of MSBuild with the
solution and platform like
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe
MyWixInstaller.sln /p:Configuration=Release /p:Platform=x64
?


2011/5/30 Francisco Gabriel Malbrán fgmalb...@gmail.com:
 Hey there.
 I am doing a simple test: I want to be able to manually build a project made
 with Votive and VS (WiX 3.5).

 My approach was to get the commands used by VS to compile and link and copy
 those into a batch file. It didn't work. I made some intents to correct it,
 but I keep hitting my head on a wall that says: candle.exe : error CNDL0103
 : The system cannot find the file 'obj\Debug\Product.Generated.wxs' with
 type 'Source'.

 If the candle command is itself looking for this Product.Generated.wxs file,
 then I should be doing something previous to compilation to generate such
 file right?

 My question is then: how do I do it in the command line?

 Best regards

 Francisco
 --
 vRanger cuts backup time in half-while increasing security.
 With the market-leading solution for virtual backup and recovery,
 you get blazing-fast, flexible, and affordable data protection.
 Download your free trial now.
 http://p.sf.net/sfu/quest-d2dcopy1
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Manually building a Votive project

2011-05-31 Thread Tobias S

Yes, possible. Just tried it myself and used the Build output script
from visual studio. Additionally I added quotes around Wix Candle +
Light path and removed obj\Debug\Product.Generated.wxs and the Candle
output obj\Debug\Product.Generated.wixobj. Then building from batch
works fine. Maybe try it once from within Votive and once from batch
and diff the 2 msis. They should be the same.

Regarding Product.Generated.wxs + wixobj I assume (actutally just a
guess!) this is some automatically generated code when using WiX to
use files built from the same Visual Studio solutions.

2011/5/31 Francisco Gabriel Malbrán fgmalb...@gmail.com:
 Hello Tobias.
 I haven't tried it before. I tried it now and it works smoothly.
 Yet I would like to establish the simplest dependencies to compile. ie: only
 Wix 3.5 (no need of .net framework)

 Is this possible?

 Who generates Product.Generated.wxs anyway? and what for? I cant seem to
 find any useful information regarding this.

 Thanks and regards!



 2011/5/31 Tobias S tobias.s1...@gmail.com

 Did you consider building it by a batch call of MSBuild with the
 solution and platform like
 C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe
 MyWixInstaller.sln /p:Configuration=Release /p:Platform=x64
 ?


 2011/5/30 Francisco Gabriel Malbrán fgmalb...@gmail.com:
  Hey there.
  I am doing a simple test: I want to be able to manually build a project
 made
  with Votive and VS (WiX 3.5).
 
  My approach was to get the commands used by VS to compile and link and
 copy
  those into a batch file. It didn't work. I made some intents to correct
 it,
  but I keep hitting my head on a wall that says: candle.exe : error
 CNDL0103
  : The system cannot find the file 'obj\Debug\Product.Generated.wxs' with
  type 'Source'.
 
  If the candle command is itself looking for this Product.Generated.wxs
 file,
  then I should be doing something previous to compilation to generate such
  file right?
 
  My question is then: how do I do it in the command line?
 
  Best regards
 
  Francisco
 
 --
  vRanger cuts backup time in half-while increasing security.
  With the market-leading solution for virtual backup and recovery,
  you get blazing-fast, flexible, and affordable data protection.
  Download your free trial now.
  http://p.sf.net/sfu/quest-d2dcopy1
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 


 --
 Simplify data backup and recovery for your virtual environment with
 vRanger.
 Installation's a snap, and flexible recovery options mean your data is
 safe,
 secure and there when you need it. Data protection magic?
 Nope - It's vRanger. Get your free trial download today.
 http://p.sf.net/sfu/quest-sfdev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

 --
 Simplify data backup and recovery for your virtual environment with vRanger.
 Installation's a snap, and flexible recovery options mean your data is safe,
 secure and there when you need it. Data protection magic?
 Nope - It's vRanger. Get your free trial download today.
 http://p.sf.net/sfu/quest-sfdev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] unhandled exception in light

2011-05-31 Thread Tobias S

http://wix.sourceforge.net/ - right hand side below Support - Bug
database (or directly
http://sourceforge.net/tracker/?group_id=105970atid=642714 ). Then
please log in or register at sourceforge and you should be able to
submit it...

2011/5/31 Thomas Svare thomas_sv...@symantec.com:
 Hello,

 I've done some cursory searching but I can't find how to submit a bug for 
 Wix.  Any pointers or links would be appreciated.

 Thanks,
 Tom

 -Original Message-
 From: Bob Arnson [mailto:b...@joyofsetup.com]
 Sent: Sunday, May 29, 2011 11:59 PM
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] unhandled exception in light

 On 25-May-11 15:31, Thomas Svare wrote:
 After several missed opportunities I've finally got a crash dump and was 
 able to run a quick analysis.  Using Wix 3.6.1706.0 light crashes 
 intermittently on our build machines.  This crash was also observed with 3.5 
 release.  I'm continuing to look into this but was wondering if those 
 familiar with the code might recognize the potential issue?  Below is the 
 windbg analysis:

 Please file a bug with the dump and !analyze output. I've seen failures
 but never from the GC.

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


 --
 vRanger cuts backup time in half-while increasing security.
 With the market-leading solution for virtual backup and recovery,
 you get blazing-fast, flexible, and affordable data protection.
 Download your free trial now.
 http://p.sf.net/sfu/quest-d2dcopy1
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

 --
 Simplify data backup and recovery for your virtual environment with vRanger.
 Installation's a snap, and flexible recovery options mean your data is safe,
 secure and there when you need it. Data protection magic?
 Nope - It's vRanger. Get your free trial download today.
 http://p.sf.net/sfu/quest-sfdev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Multi-Lingual MSI

2011-07-12 Thread Tobias S

Nope unfortunately not. For a good localization only embedding the
transforms, creating a bootstrapper to select the transform or even
handle the whole MSI installation are possible approaches.

2011/7/11 Brad Lemings b...@rebit.com:
 Greetings,

 Just wondering if there is an easier way to accomplish this: 
 http://www.geektieguy.com/2010/03/13/create-a-multi-lingual-multi-language-msi-using-wix-and-custom-build-scripts/?

 Thanks.

 --
 All of the data generated in your IT infrastructure is seriously valuable.
 Why? It contains a definitive record of application performance, security
 threats, fraudulent activity, and more. Splunk takes this data and makes
 sense of it. IT sense. And common sense.
 http://p.sf.net/sfu/splunk-d2d-c2
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Multi-Lingual MSI

2011-07-13 Thread Tobias S

Actually there are some discussions about related subjects here in the
mailing list. You can search the list e.g. here:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/
Points of interest are maybe:
- Create transforms:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multilanguage-install-td6161866i20.html#a6191971
- Integrate them into the bootstrapper: msiexec /i /qb (/qn)
TRANSFORM=1033.mst should be the parameters needed.
- If you are german speaking hold out for the samples of the book
Inside Windows Installer 4.5 from Andreas Kerl where he describes
usage of DTF and some samples of using DTF constructs for implement a
Bootstrapper / Chainer in C#
- BURN :-)

Unfortunately think there are few other good tutorials covering this subject.

Regards,
Tobias

2011/7/12 Brad Lemings b...@rebit.com:
Our product does utilize a bootstrapper so this is a distinct possibility.
Just wondering if there is a more illustrative tutorial or example somewhere
that does what you describe?

-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: Tuesday, July 12, 2011 12:35 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Multi-Lingual MSI

Nope unfortunately not. For a good localization only embedding the
transforms, creating a bootstrapper to select the transform or even handle
the whole MSI installation are possible approaches.

2011/7/11 Brad Lemings b...@rebit.com:
Greetings,

Just wondering if there is an easier way to accomplish this:
http://www.geektieguy.com/2010/03/13/create-a-multi-lingual-multi-language-msi-using-wix-and-custom-build-scripts/?

Thanks.

--
All of the data generated in your IT infrastructure is
seriously valuable.
Why? It contains a definitive record of application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on Lean Startup
Secrets Revealed. This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problems with the environment variable

2011-07-18 Thread Tobias S

Interesting approach even checking against a environment property in a
LaunchCondition. Didn't know Windows Installer can do that by default
with using %.

Actually the code sample gives me an
ICE03: Bad conditional string; Table: LaunchCondition, Column:
Condition, Key(s): [%testdir]  

This I could fix with removing 2 brackets:
Condition Message=Test must be set.
  ![CDATA[%testdir  ]]
/Condition

Afterwards the installer as expected. Runs when set
testdir=c:\someTestDir and aborts if launchCon is not fulfilled.

Regarding parent and child elements have a look at
http://wix.sourceforge.net/manual-wix3/wix_xsd_condition.htm



2011/7/18 Christoph Goetz christoph.go...@giepa.de:
 I tried it your way, but nothing happens.
 The installation just runs even if [%testdir] doesn´t exist.
 Where does the condition has to stay in the wix code?

 -Ursprüngliche Nachricht-
 Von: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
 Gesendet: Montag, 18. Juli 2011 12:18
 An: General discussion for Windows Installer XML toolset.
 Betreff: Re: [WiX-users] Problems with the environment variable

 That is what it tests. I'm not entirely sure what you're trying to do
 otherwise.

 -Original Message-
 From: Christoph Goetz [mailto:christoph.go...@giepa.de]
 Sent: 18 July 2011 11:08
 To: 'General discussion for Windows Installer XML toolset.'
 Subject: Re: [WiX-users] Problems with the environment variable

 Thanks,
 does your Condition not require that testdir exists?
 Because it does not. Only after another installation testdir exist.
 That means that only then the installation should start.
 Christoph

 -Ursprüngliche Nachricht-
 Von: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
 Gesendet: Montag, 18. Juli 2011 10:41
 An: General discussion for Windows Installer XML toolset.
 Betreff: Re: [WiX-users] Problems with the environment variable

 $(...) variables are evaluated at build-time by the preprocessor.
 For a run-time check, you want something like:

 Condition Message=Test must be set.![CDATA[
    [%testdir]  
 ]]/Condition

 http://msdn.microsoft.com/en-us/library/aa368012%28v=VS.85%29.aspx


 -Original Message-
 From: Christoph Goetz [mailto:christoph.go...@giepa.de]
 Sent: 18 July 2011 08:45
 To: 'General discussion for Windows Installer XML toolset.'
 Subject: [WiX-users] Problems with the environment variable

 Sorry

 -Ursprüngliche Nachricht-
 Von: Christoph Goetz [mailto:christoph.go...@giepa.de]
 Gesendet: Montag, 18. Juli 2011 09:42
 An: 'General discussion for Windows Installer XML toolset.'
 Betreff: Re: [WiX-users] DTE OutputFileName vs OutputName - possible wix
 bug?

 Hi,
 my installation should only start if an environment variable is set.
 But my installation start every time?
 I just want to check if the environment is set and not if it is set to an
 specific value.

 For example:



  ?if $(env.testdir)?

    Directory Id=TARGETDIR Name=SourceDir


     Directory Id=ProgramFiles64Folder
        Directory Id=INSTALLDIR
                   Name=Test /


  ...


                Feature Id=ProductFeature
             Title=test
             Level=1

 ...

   ?else?
    ?error Test must be set!?
   ?endif?

 Christoph



 
 --
 AppSumo Presents a FREE Video for the SourceForge Community by Eric
 Ries, the creator of the Lean Startup Methodology on Lean Startup
 Secrets Revealed. This video shows you how to validate your ideas,
 optimize your ideas and identify your business strategy.
 http://p.sf.net/sfu/appsumosfdev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




 
 -
 -
 AppSumo Presents a FREE Video for the SourceForge Community by Eric
 Ries, the creator of the Lean Startup Methodology on Lean Startup
 Secrets Revealed. This video shows you how to validate your ideas,
 optimize your ideas and identify your business strategy.
 http://p.sf.net/sfu/appsumosfdev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 SDL PLC confidential, all rights reserved.
 If you are not the intended recipient of this mail SDL requests and requires
 that you delete it without acting upon or copying any of its contents, and
 we further request that you advise us.
 SDL PLC is a public limited company registered in England and Wales.
 Registered number: 02675207.
 Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
 7DY, UK.


 
 --
 AppSumo Presents a FREE Video for the SourceForge Community by Eric
 Ries, the creator of the Lean Startup Methodology on Lean Startup
 Secrets Revealed. This video

Re: [WiX-users] Single Wix setup for Win7-32, 64 bit operating system

2011-07-19 Thread Tobias S

Not possible as you need OS type dependent DIFx libraries in the
resulting installer. You can simplify that by include different
fragments for x86 and x64 DIFx drivers like e.g. the following sample
feature:


Driver_x64.wxs
---
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
  xmlns:difx=http://schemas.microsoft.com/wix/DifxAppExtension;
  Fragment
DirectoryRef Id=INSTALLDIR
  Directory Id=DriverDir.x64 Name=Driver
Component Id=MyDriver_x64 Guid={GENERATE-A-NEW-GUID-HERE}
  difx:Driver AddRemovePrograms=no DeleteFiles=yes
PlugAndPlayPrompt=no ForceInstall=no Legacy=no/
  Files for drivers go here.../
/Component
  /Directory
/DirectoryRef
Feature Id=Drivers_x64 Title=Drivers_x64 Level=1
Display=hidden AllowAdvertise=no
  ComponentRef Id=MyDriver_x64 /
/Feature
  /Fragment
/Wix
---


Driver_x86.wxs
---
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
  xmlns:difx=http://schemas.microsoft.com/wix/DifxAppExtension;
  Fragment
DirectoryRef Id=INSTALLDIR
  Directory Id=DriverDir.x86 Name=Driver
Component Id=MyDriver_x86 Guid={GENERATE-A-NEW-GUID-HERE}
  difx:Driver AddRemovePrograms=no DeleteFiles=yes
PlugAndPlayPrompt=no ForceInstall=no Legacy=no/
  Files for drivers go here.../
/Component
  /Directory
/DirectoryRef
Feature Id=Drivers_x86 Title=Drivers_x86 Level=1
Display=hidden AllowAdvertise=no
  ComponentRef Id=MyDriver_x86 /
/Feature
  /Fragment
---


Referencing in wxs which is the built twice as x86 and x64 MSI:
---
?if $(var.Platform=x64 ?
   FeatureRef Id=Drivers_x64/
?else ?
   FeatureRef Id=Drivers_x86/
?endif ?
---



2011/7/19 Ravi Gupta ravigupta...@gmail.com:
 Has anyone implemented wix setup for both Win7-32,64 bit operating system
 with different drivers(using difx) for both OS.
 If any one implemented please share the knowledge.

 --
 *Regards
 T.Ravi Gupta*
 --
 Magic Quadrant for Content-Aware Data Loss Prevention
 Research study explores the data loss prevention market. Includes in-depth
 analysis on the changes within the DLP market, and the criteria used to
 evaluate the strengths and weaknesses of these DLP solutions.
 http://www.accelacomm.com/jaw/sfnl/114/51385063/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Single Wix setup for Win7-32, 64 bit operating system

2011-07-19 Thread Tobias S

If you build the project within votive then add the different wixlibs
for x86 and x64 in Project Properties - Tool Settings - Additional
parameters - Linker

Adding them directly as reference in the Setup Project not possible as
there are needed different ones for x86 and x64.



2011/7/19 Tobias S tobias.s1...@gmail.com:
 Not possible as you need OS type dependent DIFx libraries in the
 resulting installer. You can simplify that by include different
 fragments for x86 and x64 DIFx drivers like e.g. the following sample
 feature:


 Driver_x64.wxs
 ---
 ?xml version=1.0 encoding=UTF-8?
 Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
  xmlns:difx=http://schemas.microsoft.com/wix/DifxAppExtension;
  Fragment
    DirectoryRef Id=INSTALLDIR
      Directory Id=DriverDir.x64 Name=Driver
        Component Id=MyDriver_x64 Guid={GENERATE-A-NEW-GUID-HERE}
          difx:Driver AddRemovePrograms=no DeleteFiles=yes
 PlugAndPlayPrompt=no ForceInstall=no Legacy=no/
          Files for drivers go here.../
        /Component
      /Directory
    /DirectoryRef
    Feature Id=Drivers_x64 Title=Drivers_x64 Level=1
 Display=hidden AllowAdvertise=no
      ComponentRef Id=MyDriver_x64 /
    /Feature
  /Fragment
 /Wix
 ---


 Driver_x86.wxs
 ---
 ?xml version=1.0 encoding=UTF-8?
 Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
  xmlns:difx=http://schemas.microsoft.com/wix/DifxAppExtension;
  Fragment
    DirectoryRef Id=INSTALLDIR
      Directory Id=DriverDir.x86 Name=Driver
        Component Id=MyDriver_x86 Guid={GENERATE-A-NEW-GUID-HERE}
          difx:Driver AddRemovePrograms=no DeleteFiles=yes
 PlugAndPlayPrompt=no ForceInstall=no Legacy=no/
          Files for drivers go here.../
        /Component
      /Directory
    /DirectoryRef
    Feature Id=Drivers_x86 Title=Drivers_x86 Level=1
 Display=hidden AllowAdvertise=no
      ComponentRef Id=MyDriver_x86 /
    /Feature
  /Fragment
 ---


 Referencing in wxs which is the built twice as x86 and x64 MSI:
 ---
 ?if $(var.Platform=x64 ?
   FeatureRef Id=Drivers_x64/
 ?else ?
   FeatureRef Id=Drivers_x86/
 ?endif ?
 ---



 2011/7/19 Ravi Gupta ravigupta...@gmail.com:
 Has anyone implemented wix setup for both Win7-32,64 bit operating system
 with different drivers(using difx) for both OS.
 If any one implemented please share the knowledge.

 --
 *Regards
 T.Ravi Gupta*
 --
 Magic Quadrant for Content-Aware Data Loss Prevention
 Research study explores the data loss prevention market. Includes in-depth
 analysis on the changes within the DLP market, and the criteria used to
 evaluate the strengths and weaknesses of these DLP solutions.
 http://www.accelacomm.com/jaw/sfnl/114/51385063/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users



--
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to burn petrified wood? Upgrading from VS 2005 to 2010

2011-07-20 Thread Tobias S

VS2010 includes the same MSBuild concept than building within MSBuild
directly. Try to build it within VS2010 and then copy the commands
from build output and maybe remove the product.generated.* stuff and
try it that way.

What's the output when building it in visual studio Command Prompt ?
Mean there msbuild mySolution.sln ?

2011/7/20 Mark Modrall mmodr...@mzinga.com:
 Thanks for the link, Bob; I'll give it a read.

 By the by, are there known quirks when running a Wix solution via msbuild?  
 My build works just fine when I'm in VS 2010, but when I use msbuild to 
 launch it there's one module that doesn't build and doesn't give any errors.

 In the build log, I see candle and light getting run, but in obj\Release I 
 only see Product.Generated.wxs and nothing in bin\Release (no merge module).

 What's in the log is below.  The other wix projects are producing msm and msi 
 but for some reason this one quirks out.  Should I be using devenv.exe on the 
 command line instead?

 Thanks
 Mark

 Compile:
  C:\Program Files (x86)\Windows Installer XML v3.5\bin\candle.exe 
 -dDevEnvDir=*Undefined if not building from within Visual Studio* 
 -dSolutionDir=C:\svn\trunk\Installation\Wix\ -dSolutionExt=.sln 
 -dSolutionFileName=AllProducts.sln -dSolutionName=AllProducts 
 -dSolutionPath=C:\svn\trunk\Installation\Wix\AllProducts.sln 
 -dConfiguration=Release -dOutDir=bin\Release\ -dPlatform=x86 
 -dProjectDir=C:\svn\trunk\Installation\Wix\PttModule\ -dProjectExt=.wixproj 
 -dProjectFileName=PttModule.wixproj -dProjectName=PttModule 
 -dProjectPath=C:\svn\trunk\Installation\Wix\PttModule\PttModule.wixproj 
 -dTargetDir=C:\svn\trunk\Installation\Wix\PttModule\bin\Release\ 
 -dTargetExt=.msm -dTargetFileName=PttModule.msm -dTargetName=PttModule 
 -dTargetPath=C:\svn\trunk\Installation\Wix\PttModule\bin\Release\PttModule.msm
  -dPttPreBuild.Configuration=Release 
 -dPttPreBuild.FullConfiguration=Release|Win32 -dPttPreBuild.Platform=Win32 
 -dPttPreBuild.ProjectDir=C:\svn\trunk\Installation\Wix\PttModule\ 
 -dPttPreBuild.ProjectExt=.vcxproj 
 -dPttPreBuild.ProjectFileName=PttPreBuild.vcxproj 
 -dPttPreBuild.ProjectName=PttPreBuild 
 -dPttPreBuild.ProjectPath=C:\svn\trunk\Installation\Wix\PttModule\PttPreBuild.vcxproj
  -dPttPreBuild.TargetDir=C:\svn\trunk\Installation\Wix\PttModule\ 
 -dPttPreBuild.TargetExt=.wxi -dPttPreBuild.TargetFileName=Ptt.wxi 
 -dPttPreBuild.TargetName=Ptt 
 -dPttPreBuild.TargetPath=C:\svn\trunk\Installation\Wix\PttModule\Ptt.wxi -out 
 obj\Release\ -arch x86 PttModule.wxs obj\Release\Product.Generated.wxs
  Microsoft (R) Windows Installer Xml Compiler version 3.5.2519.0
  Copyright (C) Microsoft Corporation. All rights reserved.

  PttModule.wxs
  Product.Generated.wxs
 Link:
  C:\Program Files (x86)\Windows Installer XML v3.5\bin\Light.exe 
 -cultures:null -out 
 C:\svn\trunk\Installation\Wix\PttModule\bin\Release\PttModule.msm -pdbout 
 C:\svn\trunk\Installation\Wix\PttModule\bin\Release\PttModule.wixpdb 
 obj\Release\PttModule.wixobj obj\Release\Product.Generated.wixobj
  Microsoft (R) Windows Installer Xml Linker version 3.5.2519.0
  Copyright (C) Microsoft Corporation. All rights reserved.

 Done Building Project 
 C:\svn\trunk\Installation\Wix\PttModule\PttModule.wixproj (default targets).

 -Original Message-
 From: Bob Arnson [mailto:b...@joyofsetup.com]
 Sent: Wednesday, July 20, 2011 12:45 AM
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] How to burn petrified wood? Upgrading from VS 2005 
 to 2010

 On 19-Jul-11 12:25, Mark Modrall wrote:
 For #2, we have some installation stuff we only want done once (the stuff 
 that the custom action does).  So the first thing the custom action exe does 
 is try to check the registry setting to see if it's been done (that's what's 
 failing now).  When the custom action code is done, it sets that registry 
 flag to show it's been done.
 See http://www.joyofsetup.com/2007/07/01/semi-custom-actions/.

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


 --
 10 Tips for Better Web Security
 Learn 10 ways to better secure your business today. Topics covered include:
 Web security, SSL, hacker attacks  Denial of Service (DoS), private keys,
 security Microsoft Exchange, secure Instant Messaging, and much more.
 http://www.accelacomm.com/jaw/sfnl/114/51426210/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

 --
 10 Tips for Better Web Security
 Learn 10 ways to better secure your business today. Topics covered include:
 Web security, SSL, hacker attacks  Denial of Service (DoS), private keys,
 security Microsoft Exchange, secure Instant Messaging, and much more.
 http://www.accelacomm.com/jaw/sfnl/114/51426210/
 ___
 WiX-users mailing

Re: [WiX-users] Manifest for Burn Bootstrapper

2011-07-22 Thread Tobias S

Hi Rob,

Please correct me if I'm wrong. Elevation is done by the chained
installers itself and not Burn ? If so, and I run several MSI + Exe
packages thereafter each wants elevation. Then I'd highly vote at
least for an ability to embed an admin manifest without need of
mt.exe.

I mean I fully understand the concept of elevating just when needed
but from my point of view I need such a Bootstrapper elevation to run
all subsequent installers without additional UAC dialogs if needed.

Regards
Tobias



2011/7/21 Rob Mensching r...@robmensching.com:
 1. That is not the recommended way to deal with UAC from Windows. You're
 supposed to display UI and only elevate when the user does an action that
 requires it. This is how the Windows Installer behaves. You're also more
 likely to ensure that the elevation prompt appears on top of everything
 instead of stuck flashing in the task bar. Basically, much better user
 experience all the way around (funny, how following Windows guidelines helps
 smile/).

 Legacy setup programs are auto-elevated because the assumption was that they
 were written before UAC and thus will fail outright without elevation.
 RegEdit and MMC are my favorite example of annoying applications that don't
 let me just do read-only operations (which I do a lot more) then elevate for
 write operations.

 Anyway, if you want the elevate right away behavior, your BA can call
 IBootstrapperApplicationEngine-Elevate() right away. If you have a splash
 screen then you'll still have a better chance showing up on without being
 stuck blinking in the task bar.

 2. If you keep all of your machine configuration in your MSI (the goal), you
 won't have a problem. When per-machine MSIs are executed they are executed
 with elevated privileges.Your BA doesn't need to do anything. Where things
 are currently hoarked is when you need to populate UI with data from IIS7.

 3. Not in my experience. IIS7 was the first thing ever. We had to completely
 redesign the IIS7 custom action to read their data files elevated and still
 handle rollback. It was painful. II6 you could correctly read the metabase
 unelevated and all was good.

 It does not seem like a good idea to throw away the best practices simply
 because one component (IIS7) did the wrong thing. IMHO, a better path would
 be to get the best expeirence globally and find a good way to tackle the
 IIS7 problem.


 On Thu, Jul 21, 2011 at 8:37 AM, Roy Chastain r...@roychastain.org wrote:

  The goal is very much that a Bootstrapper Application is never
 elevated.

 Rob,
 I would very much like for you to rethink that goal.
 Granted BAs should not write to the system, but there are some
 compelling reasons for allowing the BA to run elevated.

 1) - Allows a user without elevation privileges to bother someone with
 them one time and one time only at the very beginning of the process
 2) - IIS as you said is a mess.  I have a Custom Action in my MSI that
 needs to read IIS configuration to present info to the user.  Therefore
 my .MSI must run elevated during the UI phase.  Since the user will
 never get it right to run the .MSI elevated, the answer became imbed the
 .MSI in a BA that forced the elevation via a manifest.  Do not ship the
 .MSI separately because again the user will try to run it instead of the
 .exe
 3) - I am sure that more than just IIS is going to be causing problems
 with .MSIs and/or BAs needing to run elevated.

 Please consider this as you respond to the feature suggestion about
 elevating the BA.  I believe that a simple switch to create the BA with
 an elevated vs. as invoker manifest is a reasonable answer.  Currently
 we can do this by a custom build event step to add our own manifest to
 the BA after it is built, but that just become more complicated and is
 subject to failure if you add/change things in Burn's manifest.

 --
 Roy Chastain




 --
 5 Ways to Improve  Secure Unified Communications
 Unified Communications promises greater efficiencies for business. UC can
 improve internal communications as well as offer faster, more efficient
 ways
 to interact with customers and streamline customer service. Learn more!
 http://www.accelacomm.com/jaw/sfnl/114/51426253/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




 --
 virtually, Rob Mensching - http://RobMensching.com LLC
 --
 5 Ways to Improve  Secure Unified Communications
 Unified Communications promises greater efficiencies for business. UC can
 improve internal communications as well as offer faster, more efficient ways
 to interact with customers and streamline customer service. Learn more!
 http://www.accelacomm.com/jaw/sfnl/114/51426253/

Re: [WiX-users] Std Bootstrapper failed: Error 0x800b010a

2011-07-22 Thread Tobias S

VMWares seem to be somehow tricky regarding retrieving the revocation
lists to verify the signatures. If your company policies allow does it
work if you connect the VM directly to the internet ? Did you try
different settings for Network Adapter like Host-only + Connect at
power on disabled ? Ipconfig /release on console ? Just some
thoughts...

Did you try to sign the exe with a test certificate and deploy these
testing certificates to that VM ? Sorry I'm not so common with such
certificates but in my understanding this should make the testing
certificate valid on that VM.

Regards
Tobias

2011/7/22  thomas.debo...@rohde-schwarz.com:
 Hi Rob,

 yes, the exe is signed, but I run the bootstrapper on a VMWare image
 without a connection to the internet :-(

 I have run it now on my host system and the bootstrapper was able to
 launch the chained installer (signature is valid and trusted).

 Is there a way to launch it on a system without internet connection?

 Thanks,
  Thomas



 Rob Mensching r...@robmensching.com
 21.07.2011 17:18
 Bitte antworten an
 General discussion for Windows Installer XML toolset.
 wix-users@lists.sourceforge.net


 An
 General discussion for Windows Installer XML toolset.
 wix-users@lists.sourceforge.net
 Kopie

 Thema
 Re: [WiX-users] Std Bootstrapper failed: Error 0x800b010a






 0x800B010A == A certificate chain could not be built to a trusted root
 authority. Is the exe signed? Is the signature valid and trusted on the
 machine?

 On Thu, Jul 21, 2011 at 2:48 AM, thomas.debo...@rohde-schwarz.com wrote:

 Hello,

 I'm a new WiX-user and just try to build a bootstrapper to customize a
 PostgreSQL installation.
 I use WIX 3.6.1915.0 in VS2010.

 I've added two ExePackages into a chain (64bit and 32bit package).
 Later I will pass additional parameters to these packages given from
 custom dialogs.

 ?xml version=1.0 encoding=UTF-8?
 Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
  Bundle Name=PostgreSQL_Bootstrapper
          Manufacturer=Thomas Deboben
          UpgradeCode=5ba5b32d-01d0-49b5-a683-1f24e09216af
          Version=1.0.0.0

    BootstrapperApplicationRef Id=
 WixStandardBootstrapperApplication.RtfLicense /
    WixVariable Id=WixStdbaLicenseRtf Value=lic\license.rtf /
    WixVariable Id=WixStdbaLogo Value=img\logo.bmp /

    Chain
      !-- TODO: Define the list of chained packages. --
      ExePackage SourceFile=pkg\postgresql-9.0.4-1-windows_x64.exe
                  InstallCommand=--mode unattended --datadir C:\PGData
                  InstallCondition=VersionNT64 = v5.1
                  /
      ExePackage SourceFile=pkg\postgresql-9.0.4-1-windows.exe
                  InstallCommand=--mode unattended --datadir C:\PGData
                  InstallCondition=NOT VersionNT64 AND VersionNT =
 v5.0
                 /

      !-- Note: The following PackageGroupRef is required to pull in
 generated authoring from project references. --
      PackageGroupRef Id=Bundle.Generated.Packages/
    /Chain

  /Bundle
 /Wix

 The build succeeded with one warning (Warning   1       Unable to reset
 acls on destination files.      light.exe       0       1
 Bootstrapper1).

 When I launch the Bootstrapper executable I get the Error 0x800b010a
 when
 the nested installer should be executed.

 What have I done wrong?

 Thanks in advance,
  Thomas

 Here is the full log:
 [01B4:05BC][2011-07-21T09:23:22.373+01:00]: Burn v3.6.1915.0, path:
 Z:\ddrive\Transfer\PostgreSQL\PostgreSQL_Bootstrapper2.exe, cmdline: ''
 [01B4:05BC][2011-07-21T09:23:22.389+01:00]: Setting string variable
 'BundleTag' to value ''
 [01B4:05BC][2011-07-21T09:23:22.389+01:00]: Setting string variable
 'WixBundleName' to value 'PostgreSQL_Bootstrapper'
 [01B4:05BC][2011-07-21T09:23:22.404+01:00]: Setting string variable
 'WixBundleLog' to value


 'C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\PostgreSQL_Bootstrapper_20110721092322.log'
 [01B4:05BC][2011-07-21T09:23:22.404+01:00]: Setting string variable
 'WixBundleOriginalSource' to value
 'Z:\ddrive\Transfer\PostgreSQL\PostgreSQL_Bootstrapper2.exe'
 [01B4:05BC][2011-07-21T09:23:22.451+01:00]: Detect 2 packages
 [01B4:05BC][2011-07-21T09:23:22.451+01:00]: Detected package:
 postgresql_9.0.4_1_windows_x64.exe, state: Absent, cached: No
 [01B4:05BC][2011-07-21T09:23:22.451+01:00]: Detected package:
 postgresql_9.0.4_1_windows.exe, state: Absent, cached: No
 [01B4:05BC][2011-07-21T09:23:22.451+01:00]: Detect complete, result: 0x0
 [01B4:05BC][2011-07-21T09:23:24.295+01:00]: Plan 2 packages, action:
 Install
 [01B4:05BC][2011-07-21T09:23:24.295+01:00]: Condition 'VersionNT64 AND
 VersionNT = v5.0' evaluates to false.
 [01B4:05BC][2011-07-21T09:23:24.295+01:00]: Planned package:
 postgresql_9.0.4_1_windows_x64.exe, state: Absent, default requested:
 Absent, ux requested: Absent, execute: None, rollback: None, cache: No,
 uncache: No, dependency: Unregister
 [01B4:05BC][2011-07-21T09:23:24.295+01:00]: Condition 'NOT VersionNT64
 AND
 VersionNT = v5.0' evaluates to true.

Re: [WiX-users] Std Bootstrapper failed: Error 0x800b010a

2011-07-22 Thread Tobias S

Hi Thomas,

Give it a try on that real restricted testsystem or some other system
without internet connection. Assume that this system migth behave
different than a VM. We had such experience when using VMs in our
testing environment where the certificates could not correctly be
updated.

My interpretation here was (sorry not very technical description): On
the real systems without internet connection this certificate
mechanism seemed to know that it could not update and didn't try to.
On the VMs the certificate mechanism didn't know whether being on or
offline and tried to but couldn't and so such strange behaviors
appeared.

Regards
Tobias


2011/7/22  thomas.debo...@rohde-schwarz.com:
 Hi Tobias,

 thanks for your hints.
 But the real problem is not VMWare.
 Our real target system will be restricted testsystem without internet
 connection.

 So I really need a way to launch the bootstrapper on a system without
 internet connection.

 Cheers,
  Thomas



 Tobias S tobias.s1...@gmail.com
 22.07.2011 11:40
 Bitte antworten an
 General discussion for Windows Installer XML toolset.
 wix-users@lists.sourceforge.net


 An
 General discussion for Windows Installer XML toolset.
 wix-users@lists.sourceforge.net
 Kopie

 Thema
 Re: [WiX-users] Std Bootstrapper failed: Error 0x800b010a






 VMWares seem to be somehow tricky regarding retrieving the revocation
 lists to verify the signatures. If your company policies allow does it
 work if you connect the VM directly to the internet ? Did you try
 different settings for Network Adapter like Host-only + Connect at
 power on disabled ? Ipconfig /release on console ? Just some
 thoughts...

 Did you try to sign the exe with a test certificate and deploy these
 testing certificates to that VM ? Sorry I'm not so common with such
 certificates but in my understanding this should make the testing
 certificate valid on that VM.

 Regards
 Tobias

 2011/7/22  thomas.debo...@rohde-schwarz.com:
 Hi Rob,

 yes, the exe is signed, but I run the bootstrapper on a VMWare image
 without a connection to the internet :-(

 I have run it now on my host system and the bootstrapper was able to
 launch the chained installer (signature is valid and trusted).

 Is there a way to launch it on a system without internet connection?

 Thanks,
  Thomas



 Rob Mensching r...@robmensching.com
 21.07.2011 17:18
 Bitte antworten an
 General discussion for Windows Installer XML toolset.
 wix-users@lists.sourceforge.net


 An
 General discussion for Windows Installer XML toolset.
 wix-users@lists.sourceforge.net
 Kopie

 Thema
 Re: [WiX-users] Std Bootstrapper failed: Error 0x800b010a






 0x800B010A == A certificate chain could not be built to a trusted root
 authority. Is the exe signed? Is the signature valid and trusted on the
 machine?

 On Thu, Jul 21, 2011 at 2:48 AM, thomas.debo...@rohde-schwarz.com
 wrote:

 Hello,

 I'm a new WiX-user and just try to build a bootstrapper to customize a
 PostgreSQL installation.
 I use WIX 3.6.1915.0 in VS2010.

 I've added two ExePackages into a chain (64bit and 32bit package).
 Later I will pass additional parameters to these packages given from
 custom dialogs.

 ?xml version=1.0 encoding=UTF-8?
 Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
  Bundle Name=PostgreSQL_Bootstrapper
          Manufacturer=Thomas Deboben
          UpgradeCode=5ba5b32d-01d0-49b5-a683-1f24e09216af
          Version=1.0.0.0

    BootstrapperApplicationRef Id=
 WixStandardBootstrapperApplication.RtfLicense /
    WixVariable Id=WixStdbaLicenseRtf Value=lic\license.rtf /
    WixVariable Id=WixStdbaLogo Value=img\logo.bmp /

    Chain
      !-- TODO: Define the list of chained packages. --
      ExePackage SourceFile=pkg\postgresql-9.0.4-1-windows_x64.exe
                  InstallCommand=--mode unattended --datadir C:\PGData
                  InstallCondition=VersionNT64 = v5.1
                  /
      ExePackage SourceFile=pkg\postgresql-9.0.4-1-windows.exe
                  InstallCommand=--mode unattended --datadir C:\PGData
                  InstallCondition=NOT VersionNT64 AND VersionNT =
 v5.0
                 /

      !-- Note: The following PackageGroupRef is required to pull in
 generated authoring from project references. --
      PackageGroupRef Id=Bundle.Generated.Packages/
    /Chain

  /Bundle
 /Wix

 The build succeeded with one warning (Warning   1       Unable to reset
 acls on destination files.      light.exe       0       1
 Bootstrapper1).

 When I launch the Bootstrapper executable I get the Error 0x800b010a
 when
 the nested installer should be executed.

 What have I done wrong?

 Thanks in advance,
  Thomas

 Here is the full log:
 [01B4:05BC][2011-07-21T09:23:22.373+01:00]: Burn v3.6.1915.0, path:
 Z:\ddrive\Transfer\PostgreSQL\PostgreSQL_Bootstrapper2.exe, cmdline: ''
 [01B4:05BC][2011-07-21T09:23:22.389+01:00]: Setting string variable
 'BundleTag' to value ''
 [01B4:05BC][2011-07-21T09:23:22.389+01:00]: Setting string variable
 'WixBundleName

Re: [WiX-users] DTF Equivalent of /l*v

Actually I also was the oppinion that
 
Microsoft.Deployment.WindowsInstaller.Installer.EnableLog(InstallLogModes.Verbose,
logFile + .install.log);
does the same as /L*v. At least I use ith for my implementations that way.

When doing a short diff with winmerge I mentioned just the
Property(S) missing in the DTF approach but the rest of the Log
being almost the same. (Didn't investigate much time in it).
For me I using this parameter will be ok.


2011/7/28 Peter Shirtcliffe pshirtcli...@sdl.com:
 You should only need InstalLogModes.Verbose. I'm assuming DTF just maps to
 the values for MSIEnableLog, as I do in my home-grown version.
 See the verbose value under
 http://msdn.microsoft.com/en-us/library/aa370091%28v=vs.85%29.aspx


 -Original Message-
 From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
 Sent: 27 July 2011 21:54
 To: General discussion for Windows Installer XML
 toolset.(wix-users@lists.sourceforge.net)
 Subject: [WiX-users] DTF Equivalent of /l*v

 I'm building a bootstrapper using DTF. I'd like to set the messageFilter to
 Installer.SetExternalUI() to be equivalent to the msiexec /l*v logging option
 but I can't quite figure out which combination of InstallLogModes values to
 use. At one point, I had nearly all values but I didn't see messages in my
 external UI handler for some of the messages I see in a msiexec /l*v log.

 Here's an example:

 InstallLogModes messageFilter =
    InstallLogModes.Error |
    InstallLogModes.Info |
    InstallLogModes.Warning |
    InstallLogModes.Verbose |
    InstallLogModes.ActionStart |
    InstallLogModes.ActionData |
    InstallLogModes.CommonData |
    InstallLogModes.PropertyDump |
    InstallLogModes.FilesInUse |
    InstallLogModes.RMFilesInUse |
    InstallLogModes.OutOfDiskSpace |
    InstallLogModes.ExtraDebug |
    InstallLogModes.User |
    InstallLogModes.Progress |
    InstallLogModes.Initialize |
    InstallLogModes.ResolveSource |
    InstallLogModes.ShowDialog |
    InstallLogModes.Terminate |
    //InstallLogModes.LogOnlyOnError |
    //InstallLogModes.None |
    InstallLogModes.FatalExit;

 Edwin G. Castro
 Software Developer - Staff
 Digital Channels
 Fiserv
 Office: 503-746-0643
 Fax: 503-617-0291
 www.fiserv.comhttp://www.fiserv.com/
 P Please consider the environment before printing this e-mail

 -
 -
 Got Input?   Slashdot Needs You.
 Take our quick survey online.  Come on, we don't ask for help often.
 Plus, you'll get a chance to win $100 to spend on ThinkGeek.
 http://p.sf.net/sfu/slashdot-survey
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 SDL PLC confidential, all rights reserved.
 If you are not the intended recipient of this mail SDL requests and requires 
 that you delete it without acting upon or copying any of its contents, and we 
 further request that you advise us.
 SDL PLC is a public limited company registered in England and Wales.  
 Registered number: 02675207.
 Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 
 7DY, UK.


 --
 Got Input?   Slashdot Needs You.
 Take our quick survey online.  Come on, we don't ask for help often.
 Plus, you'll get a chance to win $100 to spend on ThinkGeek.
 http://p.sf.net/sfu/slashdot-survey
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Got Input?   Slashdot Needs You.
Take our quick survey online.  Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Std Bootstrapper failed: Error 0x800b010a

issues can be opened at
http://sourceforge.net/tracker/?group_id=105970atid=642714 (or link
on http://wix.sourceforge.net/ right hand side below Support). Then a
registration at sourceforge is necessary and you can report a bug...


2011/7/28  thomas.debo...@rohde-schwarz.com:
 Hi,

 I've tried now to install on a real system without internet connection and
 not having the signatures of the PostgreSQL setup installed before.

 But the bootstrapper failed to launch the nested setup as well, but have a
 different error number (0x80096005).

 [0640:12D0][2011-07-28T09:45:09.734+01:00]: Error 0x80096005: Failed
 authenticode verification of payload:
 C:\DOKUME~1\tdeboben.MRR\LOKALE~1\Temp\postgresql_9.0.4_1_windows.exe
 [0640:12D0][2011-07-28T09:45:09.734+01:00]: Error 0x80096005: Failed to
 verify payload signature: C:\Dokumente und
 Einstellungen\tdeboben.MRR\Lokale Einstellungen\Anwendungsdaten\Package
 Cache\154C214AB639BFA3EBE23615D208EFBD391056E1\postgresql-9.0.4-1-windows.exe
 [0640:12D0][2011-07-28T09:45:09.734+01:00]: Error 0x80096005: Failed to
 layout or cache payload.
 [0640:12D0][2011-07-28T09:45:09.734+01:00]: Error 0x80096005: Failed to
 cache per-user payload.
 [0640:12D0][2011-07-28T09:45:09.734+01:00]: Error 0x80096005: Failed to
 cache packages.
 [0640:0C0C][2011-07-28T09:45:09.828+01:00]: Error 0x80096005: Failed while
 waiting for cache thread to complete before executing.

 When I try to launch postgresql_9.0.4_1_windows.exe manualy I get a
 security warning about an unknown publisher and that the system could not
 validate the signature.
 In this dialog I could choose if I will abort or launch the installation.

 I will open a bug as requested (need to check how to do).

 Many thanks so far,
  Thomas




 Von:    Rob Mensching r...@robmensching.com
 An:     General discussion for Windows Installer XML toolset.
 wix-users@lists.sourceforge.net
 Datum:  22.07.2011 18:26
 Betreff:        Re: [WiX-users] Std Bootstrapper failed: Error 0x800b010a



 Hmm, this is supposed to work, Thomas. Can you open a bug with as much
 detail as possible. I think it basically comes down to getting the right
 flags passed to WinVerifyTrust(), which is unfortunately no easy task.
 On Fri, Jul 22, 2011 at 3:35 AM, Tobias S tobias.s1...@gmail.com wrote:

 Hi Thomas,

 Give it a try on that real restricted testsystem or some other system
 without internet connection. Assume that this system migth behave
 different than a VM. We had such experience when using VMs in our
 testing environment where the certificates could not correctly be
 updated.

 My interpretation here was (sorry not very technical description): On
 the real systems without internet connection this certificate
 mechanism seemed to know that it could not update and didn't try to.
 On the VMs the certificate mechanism didn't know whether being on or
 offline and tried to but couldn't and so such strange behaviors
 appeared.

 Regards
 Tobias


 2011/7/22  thomas.debo...@rohde-schwarz.com:
  Hi Tobias,
 
  thanks for your hints.
  But the real problem is not VMWare.
  Our real target system will be restricted testsystem without internet
  connection.
 
  So I really need a way to launch the bootstrapper on a system without
  internet connection.
 
  Cheers,
   Thomas
 
 
 
  Tobias S tobias.s1...@gmail.com
  22.07.2011 11:40
  Bitte antworten an
  General discussion for Windows Installer XML toolset.
  wix-users@lists.sourceforge.net
 
 
  An
  General discussion for Windows Installer XML toolset.
  wix-users@lists.sourceforge.net
  Kopie
 
  Thema
  Re: [WiX-users] Std Bootstrapper failed: Error 0x800b010a
 
 
 
 
 
 
  VMWares seem to be somehow tricky regarding retrieving the revocation
  lists to verify the signatures. If your company policies allow does it
  work if you connect the VM directly to the internet ? Did you try
  different settings for Network Adapter like Host-only + Connect at
  power on disabled ? Ipconfig /release on console ? Just some
  thoughts...
 
  Did you try to sign the exe with a test certificate and deploy these
  testing certificates to that VM ? Sorry I'm not so common with such
  certificates but in my understanding this should make the testing
  certificate valid on that VM.
 
  Regards
  Tobias
 
  2011/7/22  thomas.debo...@rohde-schwarz.com:
  Hi Rob,
 
  yes, the exe is signed, but I run the bootstrapper on a VMWare image
  without a connection to the internet :-(
 
  I have run it now on my host system and the bootstrapper was able to
  launch the chained installer (signature is valid and trusted).
 
  Is there a way to launch it on a system without internet connection?
 
  Thanks,
   Thomas
 
 
 
  Rob Mensching r...@robmensching.com
  21.07.2011 17:18
  Bitte antworten an
  General discussion for Windows Installer XML toolset.
  wix-users@lists.sourceforge.net
 
 
  An
  General discussion for Windows Installer XML toolset.
  wix-users@lists.sourceforge.net
  Kopie
 
  Thema
  Re: [WiX-users] Std

[WiX-users] Burn: Select Language

Hi,

will the following scenario be possible with burn:

Have a Select Language dialog to select the current language for
Burn and then show the Burn UI + License Agreement in the selected
language ? All without creating an own custom UI, mean using
WixStandardBootstrapperApplication.RtfLicense or
WixStandardBootstrapperApplication.HyperlinkLicense?

Thanks and best regards,
Tobias

--
Got Input?   Slashdot Needs You.
Take our quick survey online.  Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn: Select Language