[WiX-users] Fragment/Ref in Merge Module?

Hello, I have the following challenge: 1. I transformed the heat-output for my purposes with xslt to a files.wxs so that I can use it within the build-process. 2. I created a slim merge module: I found out that it is not possible to have Fragments in MergeModule for any reason. How can I ge

Re: [WiX-users] Latest build - specifically MSMQ extension

Both files have 5/10 as time stamps on my machine. In an earlier release (2 weeks ago or so) I had problems with the strong names too. After installing the latest build using the .msi (not the zip) it's now working again. Best regards, Sebastian Brand Instyler Software - http://www.instyle

[WiX-users] (no subject)

Can you recommend another bootstrapper that can kick off an .exe (instead of the .msi)? Something tells me I might be writing my own bootstrapper tomorrow. -Original Message- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 17, 2007 00:09 AM To: Nick Cc: wix-users@lis

Re: [WiX-users] WixUI_Mondo.wxs + AdminInstallUI

RussGreen wrote: > Thanks. Any idea where I can get the standard AdminUI dialogs in WXS format? > I'm not aware of any. > Product: eProject -- The installer has encountered an unexpected error > installing this package. This may indicate a problem with this package. The > error code is 2265.

Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data

Karim MacDonald wrote: >> would replace the element, or if this particular Heat bug (think I >> saw it logged but can't find it now!) is likely to be fixed any time soon? >> So far, nobody's volunteered to maintain Heat so the bug isn't likely to fixed soon. > I've no idea which of these i

Re: [WiX-users] Bootstrapper/Decryption

Nick wrote: > I should probably be hung for doing this... > Certainly shunned. > I run the VS2005 bootstrapper to install C++ and .NET runtimes. Then the > bootstrapper starts an ORCA'd MSI. This MSI asks the user to enter the > correct > password. If the user does so, the custom action de

Re: [WiX-users] 64-bit Questions

[EMAIL PROTECTED] wrote: * I have seen that you can mark a Component as 64 bit (i.e. Win64='yes'). However I am not 100% clear on whether this is neccessary for .Net Assemblies as they are effectively only copied to my deployment directory. If a component is marked as 32

Re: [WiX-users] Registry and Permission

Harini Gurusamy wrote: To whom should the bug be assigned to ? Please leave it assigned to the default (None, I believe). Whoever volunteers to fix the bug will assign it to him/herself. -- sig://boB http://joyofsetup.com/

[WiX-users] Bootstrapper/Decryption

I should probably be hung for doing this... I run the VS2005 bootstrapper to install C++ and .NET runtimes. Then the bootstrapper starts an ORCA'd MSI. This MSI asks the user to enter the correct password. If the user does so, the custom action de-crypts (that's why I need the C++ and .NET runt

[WiX-users] Problems Deploying an ASP.NET Website

So, in a nutshell, I'm getting everything deployed as expected. The Virtual Directory is being setup as an app and all appears good EXCEPT the global.asax file is getting stomped. I initially tried harvesting it then just decided to deploy into a folder. Same issue. I end up with a 1K file and

Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data

Karim MacDonald wrote: > > > Eric Hybner wrote: >> >> Thanks Bob. FWIW, the problem appears to be with a default value. >> Removing the following registry value gets me past the issue for now. >> >> > Key="CLSID\{01D6FA3C-BCF4-35AB-820A-49ACAF99F5F8}\InprocServer32" >> Value="mscoree.dll" Typ

Re: [WiX-users] Silent Installation

Guna, Silent installations are built in to the Windows Installer service. There isn't really anything special you have to do to make it work. Take a look at the Windows Installer command line switches for more information: http://support.microsoft.com/kb/227091 You will also want to take a look

[WiX-users] Eliminating a directory

There is already an msi and subsequent patches. In my msi I have the following dir structure(simplification): root \ d1 \- good d2 \ wrong d2 (same name as other d2) I guess this came about from an accidental file explorer copy and is now in the msi. This is creating pr

Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data

Hello, Eric Hybner wrote: > > Thanks Bob. FWIW, the problem appears to be with a default value. > Removing the following registry value gets me past the issue for now. > > Key="CLSID\{01D6FA3C-BCF4-35AB-820A-49ACAF99F5F8}\InprocServer32" > Value="mscoree.dll" Type="string" Action="write" /> >

Re: [WiX-users] Adding Bootstrapper code to wxs file. (Somebody, please guide....)

You don't include the bootstrapper xml in the WiX file. You build your app.msi from the WiX file. Then you build your bootstrapper by doing: msbuild bootstrapper_project_file.xml > -Original Message- > From: [EMAIL PROTECTED] [mailto:wix-users- > [EMAIL PROTECTED] On Behalf Of hina1703

Re: [WiX-users] Handling Feature Dependencies

I once wrote a CA that was data driven something like: Table CustomFeatureConstraints Column Condition Column Desc Column Order I then had a ControlEvent on the Next button of the CustomSetup dialog that returned all of the rows by order, evaluated the conditions, built a list of

Re: [WiX-users] Adding Bootstrapper code to wxs file. (Somebody, please guide....)

Please reply. Hina hina1703 wrote: > > Thanks for the reply. So will the bootstrapper file be .xml file? How can > I include xml file into wxs file? > Is there any good tutorial avaliable on bootstrapper? I find it very > confusing topic with very little help available. > > Hina > > Sebas

Re: [WiX-users] NOT PRIVILEDGED Condition

The MSI property for that condition needs to be spelt right and cased right. It's Privileged. Phil Wilson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nitin Chaudhari Sent: Tuesday, October 16, 2007 5:36 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] NOT PRI

Re: [WiX-users] Patch element and creation of patch in 3.0

Delta patching is not supported using the Patch element yet. Also, using the WiX 3.0 patch build system, you cannot patch things that come from MSM's. The suggested way to share setup logic is to use Wixlibs, if your msm's are built using wix, then you could consider that. Alternatively, you ca

Re: [WiX-users] Handling Feature Dependencies

Thanks for the info guys. I will try these solutions and let you know how it goes. From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 16, 2007 1:10 AM To: John Hall Cc: Robert Priest; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Handling Feature Dependencies Joh

Re: [WiX-users] Latest build - specifically MSMQ extension

The weekly release can be downloaded here: http://wix.sourceforge.net/releases/ Best regards, Sebastian Brand Instyler Software - http://www.instyler.com On Oct 16, 2007, at 4:33 PM, VaclavK wrote: > > Hi, > > is it possible for someone to share latest build - official v3 > build is 2925 >

[WiX-users] Latest build - specifically MSMQ extension

Hi, is it possible for someone to share latest build - official v3 build is 2925 but it does not contain msmq extension. I am unable to connect to cvs server now. -- View this message in context: http://www.nabble.com/Latest-build---specifically-MSMQ-extension-tf4634567.html#a13234759 Sent from

Re: [WiX-users] Adding Bootstrapper code to wxs file.

Thanks for the reply. So will the bootstrapper file be .xml file? How can I include xml file into wxs file? Is there any good tutorial avaliable on bootstrapper? I find it very confusing topic with very little help available. Hina Sebastian Brand-2 wrote: > > Hina, > > You have to split up tha

Re: [WiX-users] Adding Bootstrapper code to wxs file.

Hina, You have to split up that file into 2 files, one for the bootstrapper and one for wix. Best regards, Sebastian Brand Instyler Software - http://www.instyler.com On Oct 16, 2007, at 4:06 PM, hina1703 wrote: > > Hello, > > I have a basic question. I am new to XML. I am trying to add a

Re: [WiX-users] Getting started web page (authoring_first_file.htm) missing

If you are using WiX2, the http://www.tramontana.co.hu/wix/ tutorial is a much better starting point. To find the missing file, look in the wix.chm help file. Best regards, Sebastian Brand Instyler Software - http://www.instyler.com On Oct 16, 2007, at 3:52 PM, John H. E. wrote: > Hi, > > p

Re: [WiX-users] NOT PRIVILEDGED Condition

Correction: the expression must evaluate to True for installation to begin. So you need to use "Privileged" instead of "NOT Privileged", like this: Privileged Hth, Franz > -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] [mailto:wix-users- > [EMAIL PROTECTED] Im Auftrag von Strele F

Re: [WiX-users] IniFile - Getting user input

Yes. Just add it in a component, like all the other components: I don't know when exactly MSI will put the value in the ini file, but I suspect it will be done after the files are copied. Best regards, Sebastian Brand Instyler Software - http://www.instyler.com On Oct 12, 2007, at

[WiX-users] Adding Bootstrapper code to wxs file.

Hello, I have a basic question. I am new to XML. I am trying to add a bootstrapper code to my wxs file. http://schemas.microsoft.com/developer/msbuild/2003";> .NET Framework 2.0 Windows Installer 3.1 Visual J# redistributable

[WiX-users] Getting started web page (authoring_first_file.htm) missing

Hi, pardon me for asking, but is the information that is supposed to be on http://wix.sourceforge.net/manual-wix2/authoring_first_file.htm available somewhere? The page is empty apart from the navigational elements. I'm a complete Wix newbie, trying to get my head around this Wix thing (for autho

Re: [WiX-users] NOT PRIVILEDGED Condition

Properties are case sensitive (and you have a spelling error too). You need to use "NOT Privileged". NOT Privileged Hth, Franz Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Nitin Chaudhari Gesendet: Dienstag, 16. Oktober 2007 14:36 An: wix-users@lists.sourceforge.net Betre

[WiX-users] NOT PRIVILEDGED Condition

Hi, I created a default Limited user account in windows XP and my wxs has NOT PRIVILEDGED Inspite of this, when I start installing, it does not prompt, and then when my the msi tried to access HKCR it throws error Msiexec log is as follows : MSI (s) (20:60) [18:00:52:378]: Skipping App

[WiX-users] Patch element and creation of patch in 3.0

Hallo all, could you anybody explain me, how to create patch in 3.0 WiX version? I've read any samples from Peter Marcu (e.g. http://blogs.msdn.com/pmarcu/archive/2007/06/28/sample-patch.aspx) but it is not enough for solution of my problem. I also can't find any documentation of "Patch" 3.0 WiX el

Re: [WiX-users] How to display text in /qb! dialog

A little late for a reply but... Ben Greenberg-3 wrote: > > I have both Product/@Language and Package/@Languages set to 1033. When I > open the package in Orca, I can see that Language is set to 1033 in the > Property table. But I still get the blank window behavior. > I'm using WiX 3.0.2925

Re: [WiX-users] WixUI_Mondo.wxs + AdminInstallUI

Thanks. Any idea where I can get the standard AdminUI dialogs in WXS format? Also, just looked at the logs and I've got an error with an event ID of 10005 that relates to the error dialog I have described. Product: eProject -- The installer has encountered an unexpected error installing this pa

[WiX-users] 64-bit Questions

I am attempting to package a .Net 2.0 application for deployment to a server running the 64-Bit version of Windows 2003. Having never attempted a 64 Bit deployment before I would appreciate feedback on the following: * I have seen that you can mark a Component as 64 bit (i.e. Win64='yes'). H