Re: [WiX-users] Problem with CDATA and default values in Conditionstatements

Did you try using lt;gt; instead of in your condition? Like: ConditionFOOVAR lt;gt; /Condition Iso: ConditionFOOVAR /Condition Regards, Albert van Peppen -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Geoff Finger Verzonden: maandag 29

Re: [WiX-users] Password protected web-based installation

Anyone? Rob Rob Hamflett wrote: I posted this in microsoft.public.platformsdk.msi but didn't get a response. Hopefully someone here can help me. I've been looking at a web-based installation using msistuff.exe and setup.exe from the Platform SDK. I've got is all up and running, but

[WiX-users] After SQL Database created

Dear All, First of all thanks for the useful QA mailing lists that helps me survive in my Wix adventure. Especially thanks to Phil who respond to one of my questions. Have been in Wix for a month and half. So far so good. However life is not always with sunshine and flowers. Here again, comes a

[WiX-users] Gentlemanlady who is doing business with China

Dear Partner friends, With the time we come into new year. First of all, let me wish you and all yours a prosperous 2007! As you know Integrate Shipping Limited is a China based freight agent established in 1997, with our own offices located in Shenzhen, Shanghai and Beijing

Re: [WiX-users] WiX3 Error: The primary key xxx is duplicated in table 'Registry'

Neil, I had the same issue when using tallow on a .reg file for an ActiveX.exe. It turned out that tallow was creating nested registry keys, and those don’t compile. For example (and this is from memory, so I’m sure it’s not syntactically correct): registry root=”HLCR”

Re: [WiX-users] Kernel Drivers

Alright, I'm trying to give this DIFxApp a shot. I'm using Version 3 of WiX, and it will not allow me to put DriverXXX attributes in the component. Nor will it allow me to use the Driver/ element inside my component. I've been trying to go through the article found here (

[WiX-users] ServiceInstall/ Type Attribute

I know that Windows Installer doesn't support the SERVICE_KERNEL_DRIVER flag in the ServiceType field of the ServiceInstall table, but why would candle return an error (CNDL0073)? If it's unsupported, shouldn't it just be a warning? I say this, because if I manually set the type field to be

Re: [WiX-users] WiX3 Error: The primary key xxx is duplicated in table 'Registry'

Thanks that gave me the clue I was missing. I think the problem is that the code fragment is followed by: RegistryKey Root=HKCR Key=CLSID\{1F235F80-8889-4C2D-96E5-B4C3D4C186C9}\InprocServer32 Action=createAndRemoveOnUninstall RegistryValue Value=mscoree.dll Type=string Action=write /

Re: [WiX-users] Per-User install warnings on files

Any hints on fixing the remaining warnings? JVE -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Van Eaton Sent: Monday, January 29, 2007 12:50 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Per-User install warnings on files I have

Re: [WiX-users] Kernel Drivers

I've been using WiX version 2 and just used the Driver* attributes. I put all the files for a given .INF in a single component, which can go against the general principal of one .dll per component, but someone recommended that I do that way; either from this mailing list or the DIFx support team.

Re: [WiX-users] Per-User install warnings on files

If you're intent on installing to a per-user directory, I don't think there's anything you can do about this warning. Rob Jason Van Eaton wrote: Any hints on fixing the remaining warnings? JVE -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of

Re: [WiX-users] Any documentation on WiX/Windows Installer limits?

Ahh...that makes sense (with also additionally experimenting by me confirming some of that). So, I'm still experimenting - splitting up the files across cabs/media - but light.exe seems to choke on the large MSI it outputs in the temp directory. I see this error: light.exe : error LGHT0001 :

Re: [WiX-users] Any documentation on WiX/Windows Installer limits?

The programmer in me can't help but wonder if Light is using an int for the file size, instead of an unsigned int. The former's top end is just over 2GB, and would explain what you're seeing. Whether or not that's the problem, I don't know. It's just what immediately jumped out at me. Rob

Re: [WiX-users] How does Candle or Light determine if an assembly is.Net or Win32?

Assuming for the sake of argument that Wix uses the IReferenceIdentity interface, is there actually a mismatch occurring? The point I'm making here is that it's normal for the 32-bit-only assemblies to go to GAC_32 and the portable ones to GAC_MSIL, depending on how they were built. Phil Wilson

Re: [WiX-users] Any documentation on WiX/Windows Installer limits?

The FileSize column in the File table has a datatype of DoubleInteger. From the documentation: The DoubleInteger data type is a four-byte integer value. Unless otherwise restricted, the range of legal values is from -2,147,483,647 to +2,147,483,647. Also, it is a known issue that cabinet

Re: [WiX-users] WiX3 Error: The primary key xxx is duplicated in table 'Registry'

This bug in heat has been reported a couple times. Unfortunately, people just keep working around the bug instead of helping make a fix for it. So, it hasn't been fixed because no one is currently maintaining heat.exe. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil

Re: [WiX-users] Kernel Drivers

There is a bug open on WiX v3 about not quite integrating correctly with DIFxApp. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Levi Wilson Sent: Tuesday, January 30, 2007 5:27 AM To: Quinton Tormanen Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Kernel Drivers

Re: [WiX-users] WiX3 Error: The primary key xxx is duplicated in table 'Registry'

I'll see if I can contribute by working out what the problem is. Neil From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: 30 January 2007 17:41 To: Neil Sleightholm; wix-users@lists.sourceforge.net Subject: RE: Re: [WiX-users] WiX3 Error: The primary key xxx is duplicated in table

Re: [WiX-users] WiX3 Error: The primary key xxx is duplicated in table 'Registry'

Is this a bug in tallow/heat (I’m using tallow) or is it an issue with the compiler? The xml makes sense, and I’m just using a xls to transform de-normalize it. It seems like the compiler is at fault for not creating the registry table entries correctly from seemingly valid xml. John

Re: [WiX-users] uninstall LaunchCondition

I have reached a solution that makes everyone here happy. It incorporates what you suggest but adds a small detail. I cannot display a dialog from the ARP uninstall, but I can display a dialog from my custom action that informs the user of what is happening. It offers two buttons: Retry and

[WiX-users] my installer has flab

After an installer for our product is built, it may undergo a transformation by a utility that we wrote...i.e. some properties are changed, Binary table entries updated, and SummaryInformation updated. This tool uses the installer COM API. After this operation, the installer inexplicably grows

Re: [WiX-users] Start application after installation

Hi, Thanks for the reply. I tried starting the app after InstallFinalize. The application starts but the msi installation just hangs in there forever The CustomAction is defined as follows CustomAction Id=ChangePropStartEXE Property=QtExecCmdLine Value='[TARGETDIR]Notify.exe' /

[WiX-users] SqlDatabase creation and collation

Hello, Is there any way I can control the collation of the database when the DB is created via SqlDatabase. No attribute on SqlDatabase element seems to take this in account. Thank you. Regards, Marius

Re: [WiX-users] SQL Database problem

Thanks for your suggestion Duan. I've tried making the changes you suggested but I'm still not having any luck creating the database. The log is showing a bit more and I'm now getting: MSI (s) (88:E0) [19:41:10:218]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI8E.tmp,

Re: [WiX-users] Triggering a rollback

I tried incorporating that into my installer and it works, just too well. The installer errors every time, even if the condition is not met. Any ideas on what might be causing this? The code I'm using is as follows: Property Id=FILEEXISTS DirectorySearch Id=CheckFileDir

Re: [WiX-users] Any documentation on WiX/Windows Installer limits?

0x80070020 is SHARING_VIOLATION. Do you have a virus scanner watching the built files? That's the way this happens most often. Virus scanners are notorious for locking up compressed files. I always exempt the build drives from our virus scanners. -Original Message- From: [EMAIL

Re: [WiX-users] SQL Database problem

The 128 characters are the magic character the CustomAcitons use to marshal strings through. You should see valid data in between the magical characters. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Graham Martin Sent: Tuesday, January 30, 2007 12:19

Re: [WiX-users] Problem with CDATA and default values in Conditionstatements

Swapping in lt;gt; fixed both issues! Thank you! Why is it necessary to use that in some cases though when in other spots I used without any problem? Shouldn't using the CDATA wrapper have prevented it from being an issue? On 1/30/07, Albert van Peppen [EMAIL PROTECTED] wrote: Did you try

Re: [WiX-users] Any documentation on WiX/Windows Installer limits?

Ahh...whoops...I think I invoked a build at the same time as that particular error. But that still doesn't address the problem I consistently see when I increase the overall MSI size (with multiple cabs of 2GB size) seems to be 2GB... filenames and paths removed to protect the innocent. =)

Re: [WiX-users] uninstall LaunchCondition

John Lalande wrote: I have reached a solution that makes everyone here happy. It incorporates what you suggest but adds a small detail. I cannot display a dialog from the ARP uninstall, but I can display a dialog from my custom action that informs the user of what is happening. It

Re: [WiX-users] Per-User and Per-Machine

Rob Hamflett wrote: If your installing per-user, make sure it really is. The Windows Installer guys put out a video about Windows Installer 4.0 for Vista. They recommended always doing a per-machine installer. The typical everyone/just for me radio buttons (as from VS setup projects)

Re: [WiX-users] Any documentation on WiX/Windows Installer limits?

Alex Lian wrote: But that still doesn't address the problem I consistently see when I increase the overall MSI size (with multiple cabs of 2GB size) seems to be 2GB... Have you tried using external cabs? My day job is working with a multi-gigabyte package but the .msi itself is only

Re: [WiX-users] Triggering a rollback

Ian Couper wrote: I tried incorporating that into my installer and it works, just too well. The installer errors every time, even if the condition is not met. Any ideas on what might be causing this? The code I'm using is as follows: Check a verbose log around the AppSearch action; it

Re: [WiX-users] ServiceInstall/ Type Attribute

Levi Wilson wrote: I know that Windows Installer doesn't support the SERVICE_KERNEL_DRIVER flag in the ServiceType field of the ServiceInstall table, but why would candle return an error (CNDL0073)? If it's unsupported, shouldn't it just be a warning? The WiX philosophy is to make good

Re: [WiX-users] WiX3 Error: The primary key xxx is duplicated in table 'Registry'

John Cole wrote: Is this a bug in tallow/heat (I’m using tallow) or is it an issue with the compiler? The xml makes sense, and I’m just using a xls to transform de-normalize it. It seems like the compiler is at fault for not creating the registry table entries correctly from seemingly

Re: [WiX-users] Shared Files in diifferent locations?

Ed Abshire wrote: I have a question concerning how I can get a set of shared files into 2 different locations. Separate products can install shared files into different directories but a single product can install them to just one. -- sig://boB http://bobs.org

Re: [WiX-users] Registry keys not being removed

Simon Topley wrote: I have a few shared compoents that I will add the same guids back to as the previous version, I'm sure that will kill off a few error messages in the log file. When I uninstall the previous version after uninstalling the current version, the current version reg keys are

Re: [WiX-users] light.exe - System.NullReferenceException

Levi Wilson wrote: In addition to the first message, I can't say for sure that I know WHICH Merge module is causing the problem, since I tried including it by itself and it worked. Also, it's just weird that my other product that uses the same merge modules works fine. On 1/26/07, *Levi

[WiX-users] Light System.AccessViolationException error (Microsoft.Tools.WindowsInstallerXml.Cab.Interop.CabInterop.CreateCabFinish)

We are seeing an access violation in light.exe (filever 2.0.4103.0) when creating the cab file for the debug target (happens when the cab file size exceeds 2 GB) - light.exe : error LGHT0001 : Attempted to read or write protected memory. This is often an indication that other memory is corrupt.