[WiX-users] search based properties

jrcolons wrote: > > I was reviewing some of our setup code, and updating it to ask for some > new requirements. two of them are Office Word and office excel 2007 > release installed. I tried several times with almost any advance at all to > make a condition out of my properties. Here's the code

[WiX-users] search based properties

I was reviewing some of our setup code, and updating it to ask for some new requirements. two of them are Office Word and office excel 2007 release installed. I tried several times with almost any advance at all to make a condition out of my properties. Here's the code:

Re: [WiX-users] Having PathEdit control blank associated to Browse Dialog

Thanks. You're right the directory needs to have a default value so that it can have a root to start with. But I think there has to be a way of having an "Edit" or "PathEdit" control to have a blank entry at the same time associating with a property. Bhavesh Bob Arnson-6 wrote: > > Bhavesh

Re: [WiX-users] Wix - Prevent XMLFile updates on Repair option

Thanks for your reply. I cannot use XmlConfig as I need to update value for the XML elements and XmlConfig I guess only has create and delete options. The other option which I thought and used while repair was to set the condition for the component by having transitive to yes and then checking f

Re: [WiX-users] Having PathEdit control blank associated to Browse Dialog

BhaveshG wrote: > 1. Have the PathEdit control blank? > 2. When the user selects the path it should populate in the PathEdit field > 3. A way for the user to RESET already selected value to blank. > See my reply to your other message: In short, no; directories must have a default value, starti

Re: [WiX-users] Wix - Prevent XMLFile updates on Repair option

BhaveshG wrote: > 1. Typically when you do a repair only the files that are missing or corrupt > are deployed which happens to me as well. But even for the existing file > XMLFile statement is executed and my files are updated on "Repair". The > XMLFile tag does not accept any "Condition" text as t

Re: [WiX-users] MinorUpdateTargetRTM problem using Wix v2.0.5002

Nick Nieslanik wrote: When I try to build the MSP with msimsp.exe after creating the PCP including MinorUpdateTargetRTM, I get the following error: ERROR: Patch Metadata property: 'MinorUpdateTargetRTM' is not a generic MSI property. You need to use MsiMsp 3.1 or later -- older versions d

Re: [WiX-users] How to use the output of Heat?

Afshin Sepehri wrote: I am trying to use Heat to auto generate the list of my files to install. However, I do not know how to use the Heat's output file. There are several Fragments, DirectoryRefs, and Components. How can I include this file in my existing project? Do I need to use a set of

Re: [WiX-users] Heat and vb6 dll?

Wilson, Phil wrote: Well the issue is basically that registration of VB6 Dlls requires the VB6 runtime to be installed on the system. That means you need the VB6 runtime on your dev machine where you're running Heat. Heat is calling DllRegisterServer, which is calling into the VB6 runtime. T

Re: [WiX-users] How to correct ICE19 and ICE50 errors in .MSI package

Venkatesh Malepati wrote: ICE19: Shortcut 'startmenuTeamsDesigner10Uni' advertises component:' Component24': This component cannot be advertised because the keypath type disallowed AND ICE50:Component 24 has an advertised shortcut,but the keypath cannot be found. My shortcut has the foll

Re: [WiX-users] If , Assembly added but file not installed?

Julie Campbell wrote: > The assembly gets gac'd, but the actual file does not get installed. Is > this the expected behavior? > If a file is marked for the GAC, it goes there only. MSI doesn't install the file, then run gacutil or equivalent -- it uses Fusion interfaces directly to install

[WiX-users] Having PathEdit control blank associated to Browse Dialog

http://www.nabble.com/file/p11091564/Tool_Setup.jpg Hi, I have just started with Wix and have the following questions. In a dialog I have an optional field for which I have the property linked to the Browse dialog. Currently I am not able to leave this blank as peroperties cannot be left blank

Re: [WiX-users] How to use the output of Heat?

Hi, You can use tallow to add the entire structure. Bhavesh Afshin Sepehri wrote: > > Hi, > > I am trying to use Heat to auto generate the list of my files to install. > However, I do not know how to use the Heat's output file. There are > several Fragments, DirectoryRefs, and Components.

[WiX-users] How to use the output of Heat?

Hi, I am trying to use Heat to auto generate the list of my files to install. However, I do not know how to use the Heat's output file. There are several Fragments, DirectoryRefs, and Components. How can I include this file in my existing project? Do I need to use a set of ComponentRef to refe

[WiX-users] Wix - Prevent XMLFile updates on Repair option

Hi, I am stuck with few issues and trying to find a solution for it. Please do let me know few pointers if you are aware of their solution. I am developing an installer for my application using WIX (ver 2.0.5325). I am deploying XML files that I modify while installation based on the user input.

Re: [WiX-users] Heat and vb6 dll?

Well the issue is basically that registration of VB6 Dlls requires the VB6 runtime to be installed on the system. That means you need the VB6 runtime on your dev machine where you're running Heat. Heat is calling DllRegisterServer, which is calling into the VB6 runtime. That much seems obvious, s

[WiX-users] Question about VS property sheets

Hi, sorry if I missed that somewhere, but I couldn't find references to it anywhere. Is it possible to use the "variables" (macros in the sense of either environment variables or plain) defined in VS property sheets? This is a highly useful feature of VS and it would make it possible for WiX to u

Re: [WiX-users] Heat and vb6 dll?

As Neil's reply is actually a solution to my other post: http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg09440.htm l I thought I'd restate _this_ problem, which remains unsolved. The problem here is that I run heat.exe on a VB6 DLL that I authored, as a way to generate a *.wxs fi

Re: [WiX-users] VB6 runtime merge modules problem SOLUTION

Neil was right on. First of all, if I'd installed orca.exe first, I could have answered my first question by examining the guts of the MSMs. Not the easiest tool to get ahold of, but I found a guy who linked it to his blog: http://blogs.msdn.com/astebner/archive/2004/07/12/180792.aspx As for my s

[WiX-users] Service failed to start. Verify that you have sufficient privileges to start system services

Hi, I have two versions of the same installer (installing a windows Service) - V1 & V2 and perform the following steps - 1) Install Version V2 - (it creates the application in Program Files\ folder.) 2) Make a copy of the installed folder Program Files\ folder in another location. 3) Uninstal

Re: [WiX-users] Heat and vb6 dll?

It looks like this has come up before: http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg01619.htm l I found I needed to add: Neil From: Neil Sleightholm Sent: 12 June 2007 22:19 To: 'Cheyne, Mark A - DNR'; wix-users@lists.sourceforge

Re: [WiX-users] How to correct ICE19 and ICE50 errors in .MSI package

Also my Icon has the follwoing definition: Venkatesh > -Original Message- > From: Venkatesh Malepati > Sent: Tuesday, June 12, 2007 5:13 PM > To: 'wix-users@lists.sourceforge.net' > Subject: How to correct ICE19 and ICE50 errors in .MSI package > > Hi > I am trying

Re: [WiX-users] Heat and vb6 dll?

I can't help but I see exactly the same errors. As a work around I am ignoring the ICE03 errors but I am not sure this is a good move. Hopefully someone else will enlighten us. Neil From: Cheyne, Mark A - DNR [mailto:[EMAIL PROTECTED] Sent: 12 June 2007 22:13 To: Neil Sleightholm; wix-user

[WiX-users] How to correct ICE19 and ICE50 errors in .MSI package

Hi I am trying to test my .MSI with ORCA and I am getting the following error messages: ICE19: Shortcut 'startmenuTeamsDesigner10Uni' advertises component:' Component24': This component cannot be advertised because the keypath type disallowed AND ICE50:Component 24 has an advertised shortcut

Re: [WiX-users] Heat and vb6 dll?

yes, that is precisely the source of the merge modules I describe in my original post. thanks. since that post, I have tried running smoke.exe on a few of those merge modules, which results in all the errors I am seeing in my build. I take that to mean that the modules are somehow 'bad'. Can anyo

Re: [WiX-users] VB6 runtime merge modules problem

That's funny I was just looking at exactly the same thing, here is what I found: oleaut32.msm - installs olepro32.dll, stdole2.tlb, asycfilt.dll and oleaut32.dll msvbvm60.msm - installs msvbvm60.dll comcat.msm - installs comcat.dll Hope this helps. If you need to find out what the ot

Re: [WiX-users] Heat and vb6 dll?

It might be easier to use the VB6 merge modules from Microsoft: http://www.microsoft.com/downloads/details.aspx?familyid=f9d19334-61ec-4 8cf-bb4e-3aec65edd50b&displaylang=en. Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] From: [EMAIL PROTECTED

Re: [WiX-users] Clear out directory before install?

I recommend they use xcopy exclusively. Give them a ZIP file. Actually, the installer should overwrite whatever's already there. The rules for first installs and major upgrades are clear: If both the existing file and the new file have a version number, highest version wins. If the version

[WiX-users] VB6 runtime merge modules problem

Hope I'm not wearing out my welcome on this list with all my queries in the last few days... As I understand, a VB6 program is at a minimum dependent on the following files that constitute the VB6 runtime: 1. msvbvm60.dll 2. oleaut32.dll 3. olepro32.dll 4. comcat.dll 5. a

[WiX-users] If , Assembly added but file not installed?

Using WiX v3.0.2813, If I set the Assembly attribute on a File element to '.net', like this: The assembly gets gac'd, but the actual file does not get installed. Is this the expected behavior? Julie Campbell [EMAIL PROTECTED] __

Re: [WiX-users] Adding User Interface to Setup Project in Visual Studio

Sorry, but I missed that part from your email and I did not receive any email from "Cheyne, Mark A - DNR". I added the culture and it worked. Thanks, Afshin From: Simon Dahlbacka [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 12, 2007 11:47 AM To: Afshin Sepehri Cc: Bob Arnson; wix-users@lists.s

Re: [WiX-users] Adding User Interface to Setup Project in Visual Studio

Add "-cultures:en-us" (or your supported language of choice) to the light command line as well. - Brett _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Afshin Sepehri Sent: Tuesday, June 12, 2007 1:40 PM To: Bob Arnson Cc: wix-users@li

Re: [WiX-users] Adding User Interface to Setup Project in Visual Studio

both I and "Cheyne, Mark A - DNR" have already replied that you also need to specify Cultures, re-read the post from Mark for detailed instructions. On 6/12/07, Afshin Sepehri <[EMAIL PROTECTED]> wrote: When I add a reference to WixUIExtension.dll, I get so many errors such as: "The localiz

Re: [WiX-users] Clear out directory before install?

Why doesn't RemoveFile work? Did you set On="install"? -Brian Simoneau -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Janulewicz Sent: Tuesday, June 12, 2007 1:08 PM To: wix-users@lists.sourceforge.net Su

Re: [WiX-users] Adding User Interface to Setup Project in Visual Studio

When I add a reference to WixUIExtension.dll, I get so many errors such as: "The localization variable !(loc.WixUIOK) is unknown. Please ensure the variable is defined." Any idea? Afshin From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Monday, June 11, 2007 11:12 PM To: Afshin Sepehri Cc: wix

[WiX-users] Clear out directory before install?

I realize this is a certifiable Bad Thing(tm), but it's a situation I haven't much control over. Here's what's going on. Deployment crew deploys website or application .msi's to one set of our production servers. Instead of using the .msi's on all our redundant servers, they xcopy it over t

Re: [WiX-users] Upgrade InstallShield package

Hi Phil, This is what I did actually, I scheduled my RemoveExistsingProducts immediately after InstallInitialize instead of InstallFinalize like I had it before. Now, I have my files removed first then the new ones deployed correctly, which looks ok. Thx for the help, Dacian - Original

[WiX-users] Heat and vb6 dll?

I ran heat.exe on a COM dll created in VB6, to automagically get a fragment of all the stuff necessary to register my DLL on installation. When I try to build the project, I get 3 errors on the output *.wxs that heat.exe gave me: 1) Error CNDL0010: The Class/@Server attribute was not found; it is

Re: [WiX-users] Upgrade InstallShield package

If you're really doing a major upgrade, this sounds like maybe you have RemoveExistingProducts after InstallFinalize. Immediately after InstallInitialize is better if you expect a major upgrade to behave like an uninstall of the old product followed by an install of the new. Phil Wilson _

[WiX-users] Where and why does this tallow Warning message come from?

When I run tallow -s on COM server files to create registry entries I get a warning at the end of the file after the XML such as: I18N Runtime Warning: Missing ICU data file detected while processing $(MWE_INSTALL)/bin/$(MWE_ARCH). Hint: Check for a misconfigured environment o

Re: [WiX-users] Upgrade InstallShield package

fiordean dacian wrote: Now the problem is IS component I want to upgrade contained, when the setup was built, both File1 and File2, without a KeyPath. What I tried is I used new GUIDs for both Component1 and Component2 in my new WiX source. What I was expecting is: 1. File1.exe and File2.exe

Re: [WiX-users] Where and why does this tallow Warning message come from?

Steven Chin wrote: I18N Runtime Warning: Missing ICU data file detected while processing $(MWE_INSTALL)/bin/$(MWE_ARCH). Hint: Check for a misconfigured environment or installation. I don't see where this is generated in the source code and some of the message uses our env

Re: [WiX-users] Future of Votive?

John Hall wrote: > Would adding this to the light property page be the kind of thing that > patches would be welcome for? > I won't speak for Justin but in general, patches are pretty much always welcome. -- sig://boB http://joyofsetup.com/

Re: [WiX-users] Upgrade InstallShield package

Hi, I ran into some extra problems with my InstallShield upgrade. Looking with Orca throughout the Component table on the IS msi installation file, I saw some of the components don't have a KeyPath set (the KeyPath column is empty). The WiX source for my new version of the product has KeyPath

Re: [WiX-users] Adding User Interface to Setup Project in Visual Studio

I'm new to WiX myself and just ran into this one yesterday. I presume you are using VS2005 and WiX 3.0? The instructions at http://wix.sourceforge.net/manual-wix2/WixUI_dialog_library.htm to add a *.wixlib and *.wxl file to the Light command line do not apply to WiX 3.0, nor do they work with the V

[WiX-users] Centrally postition error dialogs

Is there a way to ensure that the error dialogs spawned are positioned centrally with respect to the parent dialog? Thanks and regards, Saraswathy - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the

Re: [WiX-users] Adding User Interface to Setup Project in Visual Studio

I am trying to use Votive and Visual Studio to build my WiX Steup project, but to be able to add User Interface, I need to add parameters to light. For example: light.exe -out SampleWixUI.msi SampleWixUI.wixobj path\wixui.wixlib -loc path\WixUI_en-us.wxl

Re: [WiX-users] Future of Votive?

> > Is there a way of specifying the -b switch when building from Visual > > Studio? > Assuming you mean using Votive, it doesn't appear to be > exposed through the project property pages. But you can edit > the .wixproj file outside VS and add a LinkerBaseInputPaths > property to be a semi-col

Re: [WiX-users] Upgrade InstallShield package

Hi Bob, I just reviewed the REINSTALL/REINSTALLMODE which indeed is used for minor upgrades. My fault... Thanks for the help, Dacian - Original Message From: Bob Arnson <[EMAIL PROTECTED]> To: fiordean dacian <[EMAIL PROTECTED]> Cc: wix-users@lists.sourceforge.net Sent: Tuesday, Jun

Re: [WiX-users] Adding User Interface to Setup Project in Visual Studio

On 6/12/07, Bob Arnson <[EMAIL PROTECTED]> wrote: Afshin Sepehri wrote: light.exe -out SampleWixUI.msi SampleWixUI.wixobj *path*\wixui.wixlib -loc *path*\WixUI_en-us.wxl That command line is for WiX v2. In v3, you just need to add a reference to WixUIExtension.dll. and specify Cultures