Re: [WiX-users] error compiling large MSI

2011-01-12 Thread Tim McDaniel
If this isn't a 2 GB limitation, then it's a serious coincidence. :) Light successfully builds the cab files. In this case, the two big ones are just under 2 GB each (so the final msi should be almost 4 GB). Then it starts building the msi file. The msi file grows until it reaches 2,147,418,1

Re: [WiX-users] error compiling large MSI

2011-01-12 Thread Rob Mensching
That doesn't sound right to me. Also, the error you're getting is about _Validation table failing to IDT file is corrupt or something more sinister. Tim, can you try running light with the "-notidy" switch and capture the _Validation.idt file? From there we should begin the diagnosis. On Wed, Jan

Re: [WiX-users] Burn issue

2011-01-12 Thread Rob Mensching
One very important clarification I want to make, the WiX Standard Bootstrapper Application is *native* code. It will run on WinXP+ with no dependencies. The wixstdba is also somewhat customizable but definitely does not support as much as the UI element does for MSI packages. Most of the scenarios

Re: [WiX-users] Burn issue

2011-01-12 Thread Christopher Painter
I think I feel the same way about internal UI as you do. For the most part, it was 'good enough'. And I liked that it was declarative. There were some annoying things such as the way control validation behaved and not having any concept of 'custom controls', how overlapping behaved and some

Re: [WiX-users] error compiling large MSI

2011-01-12 Thread Michael Urman
The underlying storage for the .msi database cannot handle sizes over 2GB, so your assessment seems correct. Unfortunately the only workaround I'm aware of is to move the large data outside the .msi, necessitating external files (either .cab or raw source files). On Wed, Jan 12, 2011 at 15:47, Tim

Re: [WiX-users] Running Burn-driven installer in quiet mode (command line parameters)

2011-01-12 Thread Vitalii Dolia
Thank you for the answer, Rob. > From: r...@robmensching.com > Date: Wed, 12 Jan 2011 14:22:33 -0800 > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Running Burn-driven installer in quiet mode (command > line parameters) > > 1. /? is there. The WiX Standard Bootstrapper Applica

Re: [WiX-users] Burn issue

2011-01-12 Thread Vitalii Dolia
> From: r...@robmensching.com > Date: Tue, 11 Jan 2011 23:13:34 -0800 [...] > In your first example, I don't understand, why you have to create a UI in > your MSI. Burn will show UI for all scenarios (install, repair, uninstall, > upgrade patch) so you do not need a UI in your MSIs. > I agree that

Re: [WiX-users] Running Burn-driven installer in quiet mode (command line parameters)

2011-01-12 Thread Rob Mensching
1. /? is there. The WiX Standard Bootstrapper Application just doesn't support it yet. You can see bits and pieces where it will go. 2. Yes, the XxxPackage/@Name can contain relative paths. 3. Right. The command-line is provided very early because you could technically create different Bootstrapp

Re: [WiX-users] Java check

2011-01-12 Thread Neil Sleightholm
For Java I would suggest checking the registry key "HKLM\SOFTWARE\JavaSoft\Java Runtime Environment\CurrentVersion". I have had trouble checking the upgradecode as they sometimes install side-by-side. Also, don't forget that this is an install for 32 bit and 64 bit and therefore different registr

[WiX-users] error compiling large MSI

2011-01-12 Thread Tim McDaniel
I have a very simple WiX project which has worked without problems for many installers. But I am now running into an error with the latest attempted installer. The only difference I can see is that this is the first time the MSI has tried to grow above 2 GB. The error from Light is this: C:\

Re: [WiX-users] Running Burn-driven installer in quiet mode (command line parameters)

2011-01-12 Thread Vitalii Dolia
> From: r...@robmensching.com > Date: Tue, 11 Jan 2011 23:20:35 -0800 > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Running Burn-driven installer in quiet mode (command > line parameters) > > 1. Yes, absolutely. Burn supports parsing the "standard package switches" It would

Re: [WiX-users] Burn issue

2011-01-12 Thread Daniel Moody
I find myself in a similar situation as Vitalii. Our situation is thus: - The MSI file for our product has a large number of features which the end-user needs to be able to select between. Most of these features are optional and based upon what software the end-user wants our product to integr

Re: [WiX-users] Condition check and Next Button

2011-01-12 Thread Thom Leigh
I've never done it myself, but most people seem to use SpawnDialog (with a dialog they create themselves that looks like a message box.) (Some people have in the past recommended using a CA to show a message box, but this is bad practice as CAs should never show a UI) -Original Message-

Re: [WiX-users] Condition check and Next Button

2011-01-12 Thread Leonidas Spyropoulos
On 12/01/2011 15:14, Thom Leigh wrote: > This type of thing has been asked about before and as far as I > understand it is not possible - due to limitations in Windows Installer > itself, not WIX. > > Instead, consider always having Next enabled, and then when the user > clicks Next, display an err

Re: [WiX-users] Condition check and Next Button

2011-01-12 Thread Thom Leigh
This type of thing has been asked about before and as far as I understand it is not possible - due to limitations in Windows Installer itself, not WIX. Instead, consider always having Next enabled, and then when the user clicks Next, display an error message if either textbox is empty. -Ori

[WiX-users] Condition check and Next Button

2011-01-12 Thread Leonidas Spyropoulos
Hey all, I think I am stuck on a feature / bug of WIX. In a Dialog while installing I ask the user for username/password. The Next button is disabled until these two properties are set. But the thing is that these Properties are only Set after the user "leave" the EditBox. So the only way to En

[WiX-users] Setting ASP.NET 4.0 version for Virtual Directory

2011-01-12 Thread Dandre Jansen van Vuuren
Hi all I have a frustrating issue with getting the Virtual directories that get created from the installer to point to ASP.NET 4.0 but some of our environments where the installer gets executed ranges from Windows 2003 - Windows 2008, IIS 6 - IIS 7, from x86 architecture to x64 architecture. This

Re: [WiX-users] Java check

2011-01-12 Thread Thom Leigh
As this is a pre-requisite I'm glad you're plan is to block the install from the MSI with a meaningful error message if Java isn't installed. That is definitely the right thing to do. Fortunately the Java installer is MSI based (or at least the one installed on my PC is), so detecting it from your

[WiX-users] Java check

2011-01-12 Thread Leonidas Spyropoulos
Hey all, Is there a way to check if Java is installed while installation? Also what kind of versions and if not is it possible to ask the user to download & install? Thanks, Leonidas -- Leonidas Spyropoulos Formicary - delivering quality financial technology solutions www.formicary.net o : +4

[WiX-users] HA: LCIDs of the supported languages of WixUIExtension

2011-01-12 Thread maksim.vazhenin
In our product we are moving from InstallShield to WiX. In the current installer 3082 LCID is used (among others). Is it save to use WiX Spanish localization for it? Or some additionally check for this is required? Thanks, Maksim. От: Tobias S [tobias.s

Re: [WiX-users] Dutil PathExtension function query

2011-01-12 Thread Rob Mensching
You have access to the source code. Quick look shows: // Find the last dot in the last thing that could be a file. . . . else if (L'.' == *wz) { wzExtension = wz; } return wzExtension; } On Wed, Jan 12, 2011 at 12:01 AM, Sean Farrow wrote: > Hi: > Does the DUtil supplied Pat

Re: [WiX-users] LCIDs of the supported languages of WixUIExtension

2011-01-12 Thread Tobias S
Hope there is no typo in the before mentioned overview. So this overview without any warranty of correctness. 2011/1/12 Tobias S : > Following a list of LCIDs which are used in InstallShield as Transform > Identifier (e.g. 1031.mst for a german transform) and within the > solution (ism file) for

[WiX-users] Dutil PathExtension function query

2011-01-12 Thread Sean Farrow
Hi: Does the DUtil supplied PathExtension function omit the period "." From an extension it retrives? For example a file "test.txt" Would I be returned ".txt" or "txt"? Any help appreciated. Cheers Sean. -- Protect Your Si

Re: [WiX-users] LCIDs of the supported languages of WixUIExtension

2011-01-12 Thread Tobias S
Following a list of LCIDs which are used in InstallShield as Transform Identifier (e.g. 1031.mst for a german transform) and within the solution (ism file) for identifying the languages. NSIS uses these languages as well as Language ID in their NLF localization files (NSISINSTALLDIR\Contrib\Languag