Re: [WiX-users] How do you fix this error? (id is too long, 72 characters max)

[James Johnston]

Windows Installer limits directory identifiers to 72 characters max; that ID
is 73 chars.

http://msdn.microsoft.com/en-us/library/aa368295(VS.85).aspx

You can see this in ORCA by running Orca, making a new MSI file and adding
the Directory table.  Then Adjust Schema and look at the data type of the
directory ID column.  So, the directory ID will need to be shortened.

James

-Original Message-
From: John Bergman [mailto:john.berg...@xpedienttechnologies.com] 
Sent: Monday, December 06, 2010 22:48
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] How do you fix this error? (id is too long, 72
characters max)

I need some guidance as to how to fix this error... it looks like the id is
generated during the compile process... 

I am getting this error:

The DirectoryRef/@Id of attributes value,
'Application.managementserver.plugins.authentication.native.client.symbols'
is too long for an identifier, standard identifiers are 72 characters or
less.

This is what is in my wxs source (that I wrote)


  
  


It appears that this is the location of the error, it is in a generated
file.












--
What happens now with your Lotus Notes apps - do you make another costly
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] How do you fix this error? (id is too long, 72 characters max)

[John Bergman]

I need some guidance as to how to fix this error... it looks like the id is 
generated during the compile process... 

I am getting this error:

The DirectoryRef/@Id of attributes value, 
'Application.managementserver.plugins.authentication.native.client.symbols' is 
too long for an identifier, standard identifiers are 72 characters or less.

This is what is in my wxs source (that I wrote)


  
  


It appears that this is the location of the error, it is in a generated file.











--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] What version of DIFxApp is in DIFxAppExtension?

[James Johnston]

(You can just open the difxapp_.wixlib files in 7-Zip to get to
the DLLs; I believe they are just MS cabinet files with some XML appended.
No need to look at WiX source code; just extract and rename.)

>From the OP:  "It would also be good if someone could verify with the
DIFxApp team that WiX should update to this version. They are quite poor at
documenting what's changed and versioning clearly, so there is some doubt in
my mind."  I am in 100% agreement with this.  I did some rooting around in
the WDK and WiX sources and came to some observations to summarize.

First, I wondered whether an update occurred from WiX 3.0 to WiX 3.5.  The
answer is no.  I compared DIFxApp DLL versions in Wix 3.0 vs. WiX 3.5
(escrow version from a couple days ago).  They have identical DIFxApp DLLs
(compared with diff).  Therefore, simply upgrading to WiX 3.5 probably won't
help anyone having problems with DIFx unless the WiX extension was having
trouble sequencing the custom actions, or some such problem like that and
was fixed in WiX 3.5 (I am not aware of a change like that, although I
didn't look).  These DIFxApp files included with WiX are dated 5/15/2009
02:27 UTC with a file version of 2.1.1.0; product version 2.1.1.  The
signing time of the digital signature was 8/27/2008 00:06 UTC.

Then I downloaded the Windows driver kit 7.1.0 a few days ago; it installed
to directory named 7600.16385.1 so I guess that is the exact version.  Under
C:\WinDDK\7600.16385.1\redist\DIFx\DIFxApp\WixLib\x86 I found some DIFxApp
DLLs.  They are not the same as the files included with WiX.  Strangely
enough, I also found a 3 KB wixlib file in that directory with only the XML.
These DLLs are dated 2/8/2010 21:59 UTC with a file version 2.1.0.0; product
version 2.1.  The signing time on the digital signature was 2/9/2010 06:00
UTC.

To summarize:

 * WiX 3.0/3.5: DIFxApp version 2.1.1 signed 8/27/2008.
 * WDK 7.1.0: DIFxApp version 2.1.0 signed 2/09/2010.

Some conclusions:

 * Apparently the DIFx team at Microsoft isn't properly versioning DIFxApp.
How do we have newer files being distributed with older version numbers?
Probably the only reliable method of versioning DIFxApp at this point is
using the digital signatures!

 * Communication between the DIFx team and the WiX team could be improved.
Why is there a wixlib file included with the WDK yet no mention is made of
an update to DIFxApp in WiX?  I searched the WiX bug tracker for DIFx; the
only thing I have seen is the ticket submitted by Quinton earlier today.  It
would be great if they could take responsibility & contribute DIFx updates
to the WiX project?  The actual MSDN pages regarding DIFxApp have
documentation on using DIFxApp with WiX; it would be only logical to assume
that they would be helping to maintain the system that they advocate in the
documentation.  Updating WiX's DIFxApp only when users have problems seems
like a poor long-term strategy.  Perhaps the best thing might be if the DIFx
wixlib files were removed completely from WiX if they aren't maintained?
The definitive place to get these wixlib files could then become the WDK.

(Side note:  it would be very useful if Microsoft could publish a changelog
for DIFxApp; I am wondering whether the new version might fix some of the
problems Quinton Tormanen and I have been having with DIFxApp...)

In the meantime, perhaps the best strategy for DIFxApp users to take might
be to link in the wixlib file from the WDK and avoid what comes bundled with
WiX?

The OP created a ticket at:
http://sourceforge.net/tracker/?func=detail&aid=3130590&group_id=105970&atid
=642717
but since OP didn't include this link I thought I would add it to this
discussion.

James

-Original Message-
From: Quinton Tormanen [mailto:quint...@deltamotion.com] 
Sent: Monday, December 06, 2010 18:38
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] What version of DIFxApp is in DIFxAppExtension?

Sorry to subject you all to my conversation with myself as I figure out
what's what, but I thought one final(?) update on what I found out may be
useful to someone else out there:

* The latest version of the DIFx tools was included in WDK 7.1.0
  (7600.16385.1) and includes files built on 2/8/2010. The WDK
  documentation recommends that although previous WDK's included
  2.1 DIFx tools, the ones from WDK 7.1.0 should be used, which
  they are currently not.

Hopefully the DIFxAppExtension can be updated soon with the current
versions.

--Quinton

-Original Message-
From: Quinton Tormanen
Sent: Monday, December 06, 2010 10:17 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: What version of DIFxApp is in DIFxAppExtension?

I think I figured it out. The files do appear to match the MultiLin versions
of the 8/26/2008 versions (shipped with WinDDK 6001.18002) (I was comparing
with the English versions).

So, what can be done about getting DIFxAppExtension to use the latest
versions of DIFxApp.dll 

Re: [WiX-users] What version of DIFxApp is in DIFxAppExtension?

[Quinton Tormanen]

Sorry to subject you all to my conversation with myself as I figure
out what's what, but I thought one final(?) update on what I found
out may be useful to someone else out there:

* The latest version of the DIFx tools was included in WDK 7.1.0
  (7600.16385.1) and includes files built on 2/8/2010. The WDK
  documentation recommends that although previous WDK's included
  2.1 DIFx tools, the ones from WDK 7.1.0 should be used, which
  they are currently not.

Hopefully the DIFxAppExtension can be updated soon with the current
versions.

--Quinton

-Original Message-
From: Quinton Tormanen 
Sent: Monday, December 06, 2010 10:17 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: What version of DIFxApp is in DIFxAppExtension?

I think I figured it out. The files do appear to match the MultiLin
versions of the 8/26/2008 versions (shipped with WinDDK 6001.18002) (I
was comparing with the English versions).

So, what can be done about getting DIFxAppExtension to use the latest
versions of DIFxApp.dll and DIFxAppA.dll from v7600.16385? I did just go
in an enter a Feature Request for this, although I assume it's too late
for the v3.5 build.

I would also be good if someone could verify with the DIFxApp team that
WiX should update to this version. They are quite poor at documenting
what's changed and versioning clearly, so there is some doubt in my
mind.
 
--Quinton

On Mon, Dec 6, 2010 10:00 AM, Quinton Tormanen
(quint...@deltamotion.com) wrote:
> What version of DIFxApp DLLs is in the DIFxAppExtension included with
WiX v3.0?
> v3.5 appears to use the same-the sizes match anyway. I have downloaded
the WiX
> source, but it doesn't appears to include the DLLs themselves.

> Notice that the version itself isn't sufficient, since the DIFxApp
DLLs haven't
> been versioned very well. For example, the version shipped with WinDDK
> 6001.18002 are version 2.1.1.0, with build dates of 8/26/2008, and the
version
> shipped with WinDDK 7600.16385 are 2.1.0.0 with build dates of
7/13/2009. So,
> the version looks backwards, although the I know that the DIFxInst
shipped with
> WinDDK 6001.18002 doesn't work on 32-bit Win7, so I'd definitely like
the ones
> that go with the later DDK.
>
> I extracted the DLLs from my final MSI files using Orca, but am
confused because
> the file sizes don't match either, although the digital signature is
timestamped
> 8/26/2008.
>
> Quinton Tormanen
> Software Engineer
> Delta Computer Systems, Inc.
> http://www.deltamotion.com


--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] What version of DIFxApp is in DIFxAppExtension?

[Quinton Tormanen]

I think I figured it out. The files do appear to match the MultiLin
versions of the 8/26/2008 versions (shipped with WinDDK 6001.18002) (I
was comparing with the English versions).

So, what can be done about getting DIFxAppExtension to use the latest
versions of DIFxApp.dll and DIFxAppA.dll from v7600.16385? I did just go
in an enter a Feature Request for this, although I assume it's too late
for the v3.5 build.

I would also be good if someone could verify with the DIFxApp team that
WiX should update to this version. They are quite poor at documenting
what's changed and versioning clearly, so there is some doubt in my
mind.
 
--Quinton

On Mon, Dec 6, 2010 10:00 AM, Quinton Tormanen
(quint...@deltamotion.com) wrote:
> What version of DIFxApp DLLs is in the DIFxAppExtension included with
WiX v3.0?
> v3.5 appears to use the same-the sizes match anyway. I have downloaded
the WiX
> source, but it doesn't appears to include the DLLs themselves.

> Notice that the version itself isn't sufficient, since the DIFxApp
DLLs haven't
> been versioned very well. For example, the version shipped with WinDDK
> 6001.18002 are version 2.1.1.0, with build dates of 8/26/2008, and the
version
> shipped with WinDDK 7600.16385 are 2.1.0.0 with build dates of
7/13/2009. So,
> the version looks backwards, although the I know that the DIFxInst
shipped with
> WinDDK 6001.18002 doesn't work on 32-bit Win7, so I'd definitely like
the ones
> that go with the later DDK.
>
> I extracted the DLLs from my final MSI files using Orca, but am
confused because
> the file sizes don't match either, although the digital signature is
timestamped
> 8/26/2008.
>
> Quinton Tormanen
> Software Engineer
> Delta Computer Systems, Inc.
> http://www.deltamotion.com


--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] What version of DIFxApp is in DIFxAppExtension?

[Quinton Tormanen]

What version of DIFxApp DLLs is in the DIFxAppExtension included with
WiX v3.0? v3.5 appears to use the same-the sizes match anyway. I have
downloaded the WiX source, but it doesn't appears to include the DLLs
themselves.

 

Notice that the version itself isn't sufficient, since the DIFxApp DLLs
haven't been versioned very well. For example, the version shipped with
WinDDK 6001.18002 are version 2.1.1.0, with build dates of 8/26/2008,
and the version shipped with WinDDK 7600.16385 are 2.1.0.0 with build
dates of 7/13/2009. So, the version looks backwards, although the I know
that the DIFxInst shipped with WinDDK 6001.18002 doesn't work on 32-bit
Win7, so I'd definitely like the ones that go with the later DDK.

 

I extracted the DLLs from my final MSI files using Orca, but am confused
because the file sizes don't match either, although the digital
signature is timestamped 8/26/2008.

 

Quinton Tormanen

Software Engineer

Delta Computer Systems, Inc.

http://www.deltamotion.com  

 

--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Ignoring DIFxApp Return Codes

[Quinton Tormanen]

Related to the stability problems with DIFxApp (see
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg42659.htm
l for example), I had an idea on how to bypass it's finickiness.

To summarize briefly, the problem that DIFxApp gets into is that in some
cases the registry entries it relies on get messed up (I was able to
reproduce this by having a failed major update (caused by a goof on my
part) and after the rollback, the driver store registry entries were not
restored). Once in this state, attempts to uninstall the application
fails, as do major updates (since they do an uninstall as part of the
update). (Attempts for help from the DIFxApp team have got me nowhere,
which is why I'm now looking at working around instead of fixing.)

What I was considering was setting the @Return attribute for the
DIFxAppExtension's CAs to "ignore" since I'm more concerned about
getting my application updated successfully than DIFxApp giving up
prematurely on registry entries that it messed up itself. That is, it
appears to work to force the uninstall (using the msicuu2.exe util) and
then reinstall--the drivers are made available correctly--so I am
willing to ignore the error it has when uninstalling.

So, here are my specific questions:

1. Is there a way to override the custom actions included by the
DIFxAppExtension without modifying the extension? For example, the wxs
from the DIFxAppExtension source, includes the following lines:

  
  
  
  
  

I'd like to replace some of them with CustomActions that have
@Return="ignore" but are otherwise equivalent. Can I just add these same
items to my project's WXS and they will automatically override the ones
in the DIFxAppExtension? Obviously, I could skip the extension and just
do it myself--which is what I did before the extension was added in
v3.0--but it'd be easier to use the extension.

2. Is there as way to ignore the return code only on uninstall? Notice
that I can't change the CA IDs since they call each other, which seems
to rule out making two CAs--one with and one without--and giving them
different conditions.

3. What are some reasons why I shouldn't do this hack?

4. Does anyone (particularly at MSFT) have an inside track to getting
the DIFxApp team to fix this long-standing issue? It seems to me that
the uninstall should gracefully handle mangled driver store records
(cleaning them up), and rollbacks on major updates shouldn't mess up the
install.

Quinton Tormanen
Software Engineer
Delta Computer Systems, Inc.
http://www.deltamotion.com


--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] packaging large number of files

[Christopher Painter]

I once observed that adding Infragistics to an ASP.NET project added about 
5,500 
files to the installer.   These were resources like below that would probably 
never change.

I always wished there was a pattern where you could drop an uncompressed 
archive 
into windows / iis and have it virtualized as the actual file paths.  If the 
archive could also have a version number that would solve a lot of 
these servicing strategy problems.

I once interviewed for a company that told me they had about 250,000 files ( 
30GB ) in their install.  It would have been an interesting project to work on 
but in the end another company made me a better offer.

Chris

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: James Johnston 
To: General discussion for Windows Installer XML toolset. 

Sent: Mon, December 6, 2010 9:39:06 AM
Subject: Re: [WiX-users] packaging large number of files

I was also immediately concerned with the serviceability ramifications as
outlined by Rob below.

What kind of files are being installed?  With some applications there might
not be much you can do about it.  But for other applications, you can do a
lot.  For example, the video game industry will compile the thousands of
constant, non-changing assets (textures, sounds, etc.) into a small number
of files so that the installer and the computer's file system don't have to
deal with so many files.

James

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: Saturday, December 04, 2010 07:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] packaging large number of files

No, nothing in the Windows Installer supports that sort of scenario. Not
exactly sure what that would accomplish anyway. How would you patch or
update such files? Presumably you'd have to list them with the Windows
Installer somehow and that would get you right back where you are.

Now, it would be nice if the Windows Installer installed files faster than
it does... but that isn't something we can really fix in the WiX toolset.

On Fri, Dec 3, 2010 at 10:24 AM, Sanjay Rao
wrote:

> Hi All,
>
> Our software has to install a large number(more than 50,000) of files 
> at target machine and We followed one component per file strategy(as 
> recommended by WIX and MSI). While doing major upgrades it consumes a 
> lot of time(sometimes 30 minutes) on some of the screens.
>
> I want to compress some folders (holding larger number of files 25000) 
> and make a single file and then include the compresses file into msi 
> installer. After installer finishes, I want to decompress this 
> compressed file.
> My questions is :
> Is there any way in WIX to decompress the file after installation 
> completes ?
>
> Regards,
> Sanjay Rao
>


--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



  

--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] cabbing for both 32-64-bit files

[Blair]

@James: you will be happy to know that Fredrik is an excellent developer. I
have only managed to teach him very little over the short number of years I
have known him ;)

@Pally: you will be happy to know that Fredrik does, in fact, work for
Microsoft for his day job, and produces a lot of very good, high-quality
code.

Blair

-Original Message-
From: James Johnston [mailto:johnst...@inn-soft.com] 
Sent: Monday, December 06, 2010 7:22 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] cabbing for both 32-64-bit files

LOL!  Naaah... if contributors know what they're doing and commit good
patches then the quality will be good and I don't care who they work for.
No offense intended to anybody.  :)

James

-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: Monday, December 06, 2010 12:10
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] cabbing for both 32-64-bit files

I hope he works for Microsoft Rob otherwise James might be disappointed at
the quality of Burn ;)

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

http://www.iesve.com
**Design, Simulate + Innovate with the ** Integrated
Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow
G20 0SP Email Disclaimer

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 04 December 2010 07:29
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] cabbing for both 32-64-bit files

Fredrik is working on Burn. Therefore, it rocks! 

On Fri, Dec 3, 2010 at 10:06 AM, James Johnston
wrote:

> Probably, except that there were some reasons why I decided against 
> dotNetInstaller.  In the end, given that I had only one prereq 
> (DOTNETFX 2.0), I used the VS2008 bootstrapper because it's supported 
> by Microsoft; seems to work well at what it does.  Also works with 
> MSBuild.  If I replace this with something I'm guessing it might be 
> something like Burn, since that has the backing and expertise of 
> Microsoft employees; if Burn is anything like the quality of WiX 
> itself I expect it to be top-notch.
>
> -Original Message-
> From: Pally Sandher [mailto:pally.sand...@iesve.com]
> Sent: Friday, December 03, 2010 16:40
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] cabbing for both 32-64-bit files
>
> Wouldn't it be simpler to have 1 executable that does all the work for

> you rather than this chain of executables ending in MSI's?
>
> dotnetinstaller (http://dotnetinstaller.codeplex.com/) for example 
> could simplify that whole convoluted process to 1 executable 
> containing both your MSI's & all your cab files.
>
> Palbinder Sandher
> Software Deployment & IT Administrator
> T: +44 (0) 141 945 8500
> F: +44 (0) 141 945 8501
>
> http://www.iesve.com
> **Design, Simulate + Innovate with the ** 
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park, 
> Glasgow G20 0SP Email Disclaimer
>
> -Original Message-
> From: James Johnston [mailto:johnst...@inn-soft.com]
> Sent: 03 December 2010 16:06
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] cabbing for both 32-64-bit files
>
> Right; it comes in a self-extracting EXE that then launching the
> VS2008 bootstrapper.  The generated VS2008 bootstrapper EXEs have the 
> MSI name embedded in them so there are two VS2008 bootstrapper EXEs:
> one for each MSI.  I wrote a custom program in C that the
self-extracting EXE launches.
> This app determines which VS2008 bootstrapper EXE to start based on 
> the platform.  Also it moves the setup files to a different temp 
> directory to avoid trying to delete setup files that are still in use 
> (see issue where
> VS2008 bootstrapper returns immediately instead of waiting for the app

> to finish installing).
>
> -Original Message-
> From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
> Sent: Friday, December 03, 2010 05:20
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] cabbing for both 32-64-bit files
>
> Hi James:
> Thanks for this, I'm assuming you then used a bundle to deal with the 
> extraction/running the msi?
> Cheers
> Sean.
> -Original Message-
> From: James Johnston [mailto:johnst...@inn-soft.com]
> Sent: 02 December 2010 22:01
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] cabbing for both 32-64-bit files
>
> I wanted a unified self-extracting EXE for both 32- and 64-bit
versions.
> What I wound up doing was this:
>
> 1.  The build script combined with WiX conditional compilation / 
> preprocessor was used to compile to two different MSI files: one 
> 32-bit and o

Re: [WiX-users] cabbing for both 32-64-bit files

[James Johnston]

LOL!  Naaah... if contributors know what they're doing and commit good
patches then the quality will be good and I don't care who they work for.
No offense intended to anybody.  :)

James

-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: Monday, December 06, 2010 12:10
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] cabbing for both 32-64-bit files

I hope he works for Microsoft Rob otherwise James might be disappointed at
the quality of Burn ;)

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

http://www.iesve.com
**Design, Simulate + Innovate with the ** Integrated
Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow
G20 0SP Email Disclaimer

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 04 December 2010 07:29
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] cabbing for both 32-64-bit files

Fredrik is working on Burn. Therefore, it rocks! 

On Fri, Dec 3, 2010 at 10:06 AM, James Johnston
wrote:

> Probably, except that there were some reasons why I decided against 
> dotNetInstaller.  In the end, given that I had only one prereq 
> (DOTNETFX 2.0), I used the VS2008 bootstrapper because it's supported 
> by Microsoft; seems to work well at what it does.  Also works with 
> MSBuild.  If I replace this with something I'm guessing it might be 
> something like Burn, since that has the backing and expertise of 
> Microsoft employees; if Burn is anything like the quality of WiX 
> itself I expect it to be top-notch.
>
> -Original Message-
> From: Pally Sandher [mailto:pally.sand...@iesve.com]
> Sent: Friday, December 03, 2010 16:40
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] cabbing for both 32-64-bit files
>
> Wouldn't it be simpler to have 1 executable that does all the work for

> you rather than this chain of executables ending in MSI's?
>
> dotnetinstaller (http://dotnetinstaller.codeplex.com/) for example 
> could simplify that whole convoluted process to 1 executable 
> containing both your MSI's & all your cab files.
>
> Palbinder Sandher
> Software Deployment & IT Administrator
> T: +44 (0) 141 945 8500
> F: +44 (0) 141 945 8501
>
> http://www.iesve.com
> **Design, Simulate + Innovate with the ** 
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park, 
> Glasgow G20 0SP Email Disclaimer
>
> -Original Message-
> From: James Johnston [mailto:johnst...@inn-soft.com]
> Sent: 03 December 2010 16:06
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] cabbing for both 32-64-bit files
>
> Right; it comes in a self-extracting EXE that then launching the
> VS2008 bootstrapper.  The generated VS2008 bootstrapper EXEs have the 
> MSI name embedded in them so there are two VS2008 bootstrapper EXEs:
> one for each MSI.  I wrote a custom program in C that the
self-extracting EXE launches.
> This app determines which VS2008 bootstrapper EXE to start based on 
> the platform.  Also it moves the setup files to a different temp 
> directory to avoid trying to delete setup files that are still in use 
> (see issue where
> VS2008 bootstrapper returns immediately instead of waiting for the app

> to finish installing).
>
> -Original Message-
> From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
> Sent: Friday, December 03, 2010 05:20
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] cabbing for both 32-64-bit files
>
> Hi James:
> Thanks for this, I'm assuming you then used a bundle to deal with the 
> extraction/running the msi?
> Cheers
> Sean.
> -Original Message-
> From: James Johnston [mailto:johnst...@inn-soft.com]
> Sent: 02 December 2010 22:01
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] cabbing for both 32-64-bit files
>
> I wanted a unified self-extracting EXE for both 32- and 64-bit
versions.
> What I wound up doing was this:
>
> 1.  The build script combined with WiX conditional compilation / 
> preprocessor was used to compile to two different MSI files: one 
> 32-bit and one 64-bit.  Each was compiled individually.  (For example,

> 32-bit MSI has a launch condition preventing use on 64-bit Windows).
> 2.  Files that are shared go into a common external cabinet file.
> Because they are shared, each variation of the build script 
> compile/link should produce the same CAB file.  I use a diff command 
> just to make sure this is the case before merging the 32-bit and 
> 64-bit build output directories.
> 3.  Files that are not shared go into two cabinets: one for 32-bit 
> files to go with 32-bit MSI, and one for 64-bit files to go 

Re: [WiX-users] packaging large number of files

[James Johnston]

I was also immediately concerned with the serviceability ramifications as
outlined by Rob below.

What kind of files are being installed?  With some applications there might
not be much you can do about it.  But for other applications, you can do a
lot.  For example, the video game industry will compile the thousands of
constant, non-changing assets (textures, sounds, etc.) into a small number
of files so that the installer and the computer's file system don't have to
deal with so many files.

James

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: Saturday, December 04, 2010 07:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] packaging large number of files

No, nothing in the Windows Installer supports that sort of scenario. Not
exactly sure what that would accomplish anyway. How would you patch or
update such files? Presumably you'd have to list them with the Windows
Installer somehow and that would get you right back where you are.

Now, it would be nice if the Windows Installer installed files faster than
it does... but that isn't something we can really fix in the WiX toolset.

On Fri, Dec 3, 2010 at 10:24 AM, Sanjay Rao
wrote:

> Hi All,
>
> Our software has to install a large number(more than 50,000) of files 
> at target machine and We followed one component per file strategy(as 
> recommended by WIX and MSI). While doing major upgrades it consumes a 
> lot of time(sometimes 30 minutes) on some of the screens.
>
> I want to compress some folders (holding larger number of files 25000) 
> and make a single file and then include the compresses file into msi 
> installer. After installer finishes, I want to decompress this 
> compressed file.
> My questions is :
> Is there any way in WIX to decompress the file after installation 
> completes ?
>
> Regards,
> Sanjay Rao
>


--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Transitive not evaluated

[Jeffrey Bindinga]

Hi All,

I've got a problem with the evaluation of transitive components. We need to
install services as being automatic or manual depending on another
installation, we've got a property called STANDBY if the other product is
installed. 

To get a situation where the service is installed auto or manual depending
on the property, we create two components with the same file and service but
with different serviceinstall and servicecontrol elements. I set the
transitive bit for those components to true. Now when we do a new install,
we get the right service installation. But when we do a minor upgrade, it
doesn't reevaluate the condition of the components, even though they are
transitive. The code looks like the following:


NOT STANDBY

  

  
  



STANDBY







We use the properties REINSTALLMODE="vmos" REINSTALL=ALL for the minor
upgrade.

Is there a better way to conditionally install the services with other
settings? Or is there an easier way to do this?

Regards,
Jeffrey Bindinga
-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Transitive-not-evaluated-tp5808253p5808253.html
Sent from the wix-users mailing list archive at Nabble.com.

--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] What does Custom/@OnExit do?

[Neil Sleightholm]

The first two links are what I was questioning i.e. "Mutually exclusive
with Before, After, and Sequence attributes TODO: What does this type
mean?".

The third is the key to its function.

Neil

-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com] 
Sent: 06 December 2010 14:12
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] What does Custom/@OnExit do?

Checkout:

http://wix.sourceforge.net/manual-wix3/wix_xsd_custom.htm

http://wix.sourceforge.net/manual-wix3/wix_xsd_simple_type_exittype.htm

Possible values: {success, cancel, error, suspend} 

http://msdn.microsoft.com/en-us/library/aa369543(v=VS.85).aspx

msiDoActionStatusSuccess
msiDoActionStatusUserExit
msiDoActionStatusFailure
msiDoActionStatusSuspend

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: Neil Sleightholm 
To: wix-users@lists.sourceforge.net
Sent: Mon, December 6, 2010 7:44:45 AM
Subject: [WiX-users] What does Custom/@OnExit do?

Does anyone know what Custom/@OnExit does? In the help it says "Mutually
exclusive with Before, After, and Sequence attributes TODO: What does
this type mean?".



Neil



Neil Sleightholm
X2 Systems Limited
n...@x2systems.com  




--
What happens now with your Lotus Notes apps - do you make another costly

upgrade, or settle for being marooned without product support? Time to
move
off Lotus Notes and onto the cloud with Force.com, apps are easier to
build,
use, and manage than apps on traditional platforms. Sign up for the
Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



  


--
What happens now with your Lotus Notes apps - do you make another costly

upgrade, or settle for being marooned without product support? Time to
move
off Lotus Notes and onto the cloud with Force.com, apps are easier to
build,
use, and manage than apps on traditional platforms. Sign up for the
Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] What does Custom/@OnExit do?

[Christopher Painter]

Checkout:

http://wix.sourceforge.net/manual-wix3/wix_xsd_custom.htm

http://wix.sourceforge.net/manual-wix3/wix_xsd_simple_type_exittype.htm

Possible values: {success, cancel, error, suspend} 

http://msdn.microsoft.com/en-us/library/aa369543(v=VS.85).aspx

msiDoActionStatusSuccess
msiDoActionStatusUserExit
msiDoActionStatusFailure
msiDoActionStatusSuspend

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: Neil Sleightholm 
To: wix-users@lists.sourceforge.net
Sent: Mon, December 6, 2010 7:44:45 AM
Subject: [WiX-users] What does Custom/@OnExit do?

Does anyone know what Custom/@OnExit does? In the help it says "Mutually
exclusive with Before, After, and Sequence attributes TODO: What does
this type mean?".



Neil



Neil Sleightholm
X2 Systems Limited
n...@x2systems.com  



--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



  

--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] What does Custom/@OnExit do?

[Neil Sleightholm]

Does anyone know what Custom/@OnExit does? In the help it says "Mutually
exclusive with Before, After, and Sequence attributes TODO: What does
this type mean?".

 

Neil

 

Neil Sleightholm
X2 Systems Limited
n...@x2systems.com  

 

--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Scheduling includes invalid actions

[Neil Sleightholm]

I scheduled a custom action after SchedSecureObjects but I didn't
actually have the SecureObjects table in my code. The code compiled ok
but it added the SchedSecureObjects action to the
InstallExecuteSequence. When I ran the install SchedSecureObjects tried
to run but failed because SecureObjects didn't exist.

 

Is this a bug in WiX? Should there have been a warning that I had
schedule a custom action after something that didn't exist?

 

Neil

 

Neil Sleightholm
X2 Systems Limited
n...@x2systems.com  

 

--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] packaging large number of files

[Pally Sandher]

One possible solution is to split your installation into 2 (or more)
parts & use separate MSI's for each part. That way you're only patching
or upgrading a smaller set of the whole. If your installation has files
which very rarely change if at all, you could put those into their own
MSI which installs to it's own location & are used by your application
from there (this may require code changes in your application to access
the files at the new location). You can then treat your "data" installer
as a pre-requisite of your "application" installer & bundle them
together using a bootstrapper such as dotnetinstaller if you wish.

This worked for us as we had the same issue with patches & upgrades
taking a very long time. Our application used to be >1 GB with >6500
files. Now it's ~5000 files in the "data" installer (~900 MB installed,
~400 MB MSI) & ~1700 in the "application" installer (200 MB installed,
60 MB MSI) which cuts down on waiting time when patching & upgrading
both packages tremendously.

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

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: 04 December 2010 07:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] packaging large number of files

No, nothing in the Windows Installer supports that sort of scenario. Not
exactly sure what that would accomplish anyway. How would you patch or
update such files? Presumably you'd have to list them with the Windows
Installer somehow and that would get you right back where you are.

Now, it would be nice if the Windows Installer installed files faster
than it does... but that isn't something we can really fix in the WiX
toolset.

On Fri, Dec 3, 2010 at 10:24 AM, Sanjay Rao
wrote:

> Hi All,
>
> Our software has to install a large number(more than 50,000) of files 
> at target machine and We followed one component per file strategy(as 
> recommended by WIX and MSI). While doing major upgrades it consumes a 
> lot of time(sometimes 30 minutes) on some of the screens.
>
> I want to compress some folders (holding larger number of files 25000)

> and make a single file and then include the compresses file into msi 
> installer. After installer finishes, I want to decompress this 
> compressed file.
> My questions is :
> Is there any way in WIX to decompress the file after installation 
> completes ?
>
> Regards,
> Sanjay Rao
>
>
> --
>  Increase Visibility of Your 3D Game App & Earn a Chance To 
> Win $500!
> Tap into the largest installed PC base & get more eyes on your game by

> optimizing for Intel(R) Graphics Technology. Get started today with 
> the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for
grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


--
virtually, Rob Mensching - http://RobMensching.com LLC

--
What happens now with your Lotus Notes apps - do you make another costly
upgrade, or settle for being marooned without product support? Time to
move off Lotus Notes and onto the cloud with Force.com, apps are easier
to build, use, and manage than apps on traditional platforms. Sign up
for the Lotus Notes Migration Kit to learn more.
http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] cabbing for both 32-64-bit files

[Pally Sandher]

I hope he works for Microsoft Rob otherwise James might be disappointed
at the quality of Burn ;)

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

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: 04 December 2010 07:29
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] cabbing for both 32-64-bit files

Fredrik is working on Burn. Therefore, it rocks! 

On Fri, Dec 3, 2010 at 10:06 AM, James Johnston
wrote:

> Probably, except that there were some reasons why I decided against 
> dotNetInstaller.  In the end, given that I had only one prereq 
> (DOTNETFX 2.0), I used the VS2008 bootstrapper because it's supported 
> by Microsoft; seems to work well at what it does.  Also works with 
> MSBuild.  If I replace this with something I'm guessing it might be 
> something like Burn, since that has the backing and expertise of 
> Microsoft employees; if Burn is anything like the quality of WiX 
> itself I expect it to be top-notch.
>
> -Original Message-
> From: Pally Sandher [mailto:pally.sand...@iesve.com]
> Sent: Friday, December 03, 2010 16:40
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] cabbing for both 32-64-bit files
>
> Wouldn't it be simpler to have 1 executable that does all the work for

> you rather than this chain of executables ending in MSI's?
>
> dotnetinstaller (http://dotnetinstaller.codeplex.com/) for example 
> could simplify that whole convoluted process to 1 executable 
> containing both your MSI's & all your cab files.
>
> Palbinder Sandher
> Software Deployment & IT Administrator
> T: +44 (0) 141 945 8500
> F: +44 (0) 141 945 8501
>
> http://www.iesve.com
> **Design, Simulate + Innovate with the ** 
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park, 
> Glasgow G20 0SP Email Disclaimer
>
> -Original Message-
> From: James Johnston [mailto:johnst...@inn-soft.com]
> Sent: 03 December 2010 16:06
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] cabbing for both 32-64-bit files
>
> Right; it comes in a self-extracting EXE that then launching the 
> VS2008 bootstrapper.  The generated VS2008 bootstrapper EXEs have the 
> MSI name embedded in them so there are two VS2008 bootstrapper EXEs: 
> one for each MSI.  I wrote a custom program in C that the
self-extracting EXE launches.
> This app determines which VS2008 bootstrapper EXE to start based on 
> the platform.  Also it moves the setup files to a different temp 
> directory to avoid trying to delete setup files that are still in use 
> (see issue where
> VS2008 bootstrapper returns immediately instead of waiting for the app

> to finish installing).
>
> -Original Message-
> From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
> Sent: Friday, December 03, 2010 05:20
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] cabbing for both 32-64-bit files
>
> Hi James:
> Thanks for this, I'm assuming you then used a bundle to deal with the 
> extraction/running the msi?
> Cheers
> Sean.
> -Original Message-
> From: James Johnston [mailto:johnst...@inn-soft.com]
> Sent: 02 December 2010 22:01
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] cabbing for both 32-64-bit files
>
> I wanted a unified self-extracting EXE for both 32- and 64-bit
versions.
> What I wound up doing was this:
>
> 1.  The build script combined with WiX conditional compilation / 
> preprocessor was used to compile to two different MSI files: one 
> 32-bit and one 64-bit.  Each was compiled individually.  (For example,

> 32-bit MSI has a launch condition preventing use on 64-bit Windows).
> 2.  Files that are shared go into a common external cabinet file.
> Because they are shared, each variation of the build script 
> compile/link should produce the same CAB file.  I use a diff command 
> just to make sure this is the case before merging the 32-bit and 
> 64-bit build output directories.
> 3.  Files that are not shared go into two cabinets: one for 32-bit 
> files to go with 32-bit MSI, and one for 64-bit files to go with
64-bit MSI.
> Again, the preprocessor is used to make this happen.
>
> The final layout looks something like:
> MyApp.cab
> MyApp_x64.cab
> MyApp_x86.cab
> MyApp_x64.msi
> MyApp_x86.msi
>
> In my case, the application is 32-bit but I had to split the install 
> like this due to driver-related reasons.
>
> -Original Message-
> From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
> Sent: Thursday, Dec

[WiX-users] Need Help for "Invalid web address" during install of web site (WiX 3.5 & 3.6)

[Pound, Robert (CDC/OCOO/ITSO) (CTR)]

A bug (#3109682,
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=3109682&group_id=105970)
 has been reported on this issue for WiX versions 3.6 & 3.5.

My question here is can anyone tell me is there a prior version of WiX that can 
build an install for a non-default web site that will work?  I'm willing to 
consider falling back to a previous version to be able to get the install to 
work properly.  The problem is occurring on 2008R2 and IIS 7.x servers.  
Unfortunately I do not have an option to fall back to previous server OS or IIS 
version.

Thanks,
Bob

--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Define Bootstrapper Order???

[Simon Chromow]

I can't wrap my head around it.
Could you please point me in the right direction.
Any hint would be appreciated.

Thank you.

-Ursprüngliche Nachricht-
Von: Rob Mensching [mailto:r...@robmensching.com] 
Gesendet: Samstag, 4. Dezember 2010 08:18
An: General discussion for Windows Installer XML toolset.
Betreff: Re: [WiX-users] Define Bootstrapper Order???

Yes. Actually, it's required. The Chain defines the Package order. You can also 
Fragment your PackageGroups and tie the chain back together using the After 
attribute.

On Thu, Dec 2, 2010 at 6:49 AM, Simon Chromow wrote:

> Hello,
>
>
>
> I'm using WIX 3.6.
>
> Is it possible to define the order, how the bootstrapper packages are 
> installed???
>
>
> --
>  Increase Visibility of Your 3D Game App & Earn a Chance To 
> Win $500!
> Tap into the largest installed PC base & get more eyes on your game by 
> optimizing for Intel(R) Graphics Technology. Get started today with 
> the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


--
virtually, Rob Mensching - http://RobMensching.com LLC
--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move off 
Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, 
and manage than apps on traditional platforms. Sign up for the Lotus Notes 
Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn Code sample

[Tobias S]

Ok, got it working:


http://schemas.microsoft.com/wix/2006/wi";>










Then I forgot to include WixBalExtension for linking:
candle.exe" setup.wxs
light.exe" -out setup.exe -ext WixBalExtension setup.wixobj -v


This should build the setup.exe

For calling a ExePackage I got it working but not for the MsiPackage.
Seems that burn is here under heavy development :-)

> It looks like you can set your EULA but I haven't gotten that far yet.

Think that cannot be done right now as a reference is set to

and it seems that this has no ability to be configurable. Maybe in an
upcoming release...

Regards
Tobias

2010/12/3 Daniel Moody :
> Like you, I've been playing around with Burn.  Here's what I got to work in
> the 3.6-1125 build:
> ---
> 
> http://schemas.microsoft.com/wix/2006/wi";>
>   UpgradeCode="537641ca-e876-4bcb-8d57-c6cdc8940c84">
>     Id="WixStandardBootstrapperApplication.RtfLicense" />
>    
>       SourceFile="$(var.SolutionDir)GibbsCAMx64\bin\x64\Release\en-us\GibbsCAM2011
> _x64_v9.9.4.1.msi"/>
>    
>  
> 
> ---
>
> This builds a setup.exe with its own GUI.  I don't know if there is a way to
> use whatever UI the MSI incorporates, and I haven't yet looked into writing
> my own UI.
>
> I've tried adding a few MSIs to the chain, but it has unpredictable results
> and hangs outright on a few of my "testing environment" VMs.
>
> It looks like you can set your EULA but I haven't gotten that far yet.
>
> I hope this helps.  Be sure to share any discoveries you make that might be
> helpful.
>
> Daniel Moody | QA Engineer | Gibbs and Associates
>
> Phone: 805-523-0004
> Email: dani...@gibbscam.com
>
> www.GibbsCAM.com
>
> -Original Message-
> Date: Fri, 3 Dec 2010 10:05:43 +0100
> From: Tobias S 
> Subject: [WiX-users] Burn Code sample
> To: "General discussion for Windows Installer XML toolset."
>        
> Message-ID:
>        
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
>
> Am just playing a bit with burn from the newest build. My goal is just
> to have a working setup.exe package containing a msi to be installed.
> Can anybody post me a workign simple sample for that use case or give
> me a hint based on my below described solution? Based on the actual
> help and the included sample in the wix sources I don't get it.
>
> Thanks,
> Tobias
>
>
>
> Additionally my current code:
>
> --- BEGIN: setup.wxs ---
> 
> 
>         UpgradeCode='9072A488-D27B-4443-B147-56D8C47E0E4E'>
>                
>                         Name='test' />
>                
>        
> 
> --- END: setup.wxs ---
>
>
> --- BEGIN: setup.bat ---
> set wivVer=Wix36
>
> "%~dp0%wivVer%\candle.exe" setup.wxs
> "%~dp0%wivVer%\light.exe" -out setup.exe setup.wixobj -v
> --- END: setup.bat ---
>
>
> Given error:
> light.exe : error LGHT0001 : The given key was not present in the
> dictionary.
>
> Exception Type: System.Collections.Generic.KeyNotFoundException
>
> Stack Trace:
>   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
>   at Microsoft.Tools.WindowsInstallerXml.Binder.BindBundle(Output bundle,
> Strin
> g bundleFile)
>   at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output, String
> file
> )
>   at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args)
> Binder temporary directory located at
> 'C:\Users\TobSch01\AppData\Local\Temp\noqf
> 2omy'.
>
>
>
> --
>
> 
> --
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
>
> --
>
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> End of WiX-users Digest, Vol 55, Issue 13
> *
>
>
>
> --
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

--
What happens now with your Lotus Notes apps - do