Re: [WiX-users] Future of Votive?

Yes, there are plans to add designers to Votive. It's been on my list for a while, but unfortunately my spare time has been rare the past few months. I think the first designers will probably be very basic and rudimentary (I'm thinking of registry and file/directory editors), but eventually more wi

Re: [WiX-users] Future of Votive?

Not sure about the Votive information, but if you pass -gg to heat as an option it will generate guids for you instead of inserting the "PUT-GUID-HERE" message. On 6/8/07, Christopher Painter <[EMAIL PROTECTED]> wrote: I've been playing with Votive and I really like the way it plugs into VS and

[WiX-users] Future of Votive?

I've been playing with Votive and I really like the way it plugs into VS and uses MSBuild. My installs are primarily InstallShield based, and they will remain that way, but I would like to break some of the xcopy type logic out into seperate merge modules and let developers maintain them.

Re: [WiX-users] Shared files

Are these files being installed in a shared location? If so, the Component GUIDs need to be the same. That's what the Component Rules are all about. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roy Riegel Sent: Friday, June 08, 2007 4:52 PM To: wix-users@lists.sourceforge.net

[WiX-users] Shared files

Hello All, This has got to be a common problem with a known solution. We are installing 35 -> 40 files into a \system\bin directory in an XP Windows environment with two separate but similar module WIX/MSI installers. By design, it is possible for the user to install this file list once or

Re: [WiX-users] x64 and x86 both use same data files

My company really wants it to only be 1 installer, is there any dangerous reasons not to do it that way. John Vottero wrote: > > It sounds like you're trying to create a single MSI that installs either > 32 bit or 64 bit executables, is that correct? If so, you shouldn't, > you need one MSI for

Re: [WiX-users] Check for 'power user' in Condition

You can register COM information in either HKEY_LOCAL_MACHINE\Software\Classes or in HKEY_CURRENT_USER\Software\Classes. HKEY_CLASSES_ROOT is a merged view of those keys. If you specify HKCR in your Registry elements Windows Installer places them in HKLM for a per-machine install and HKCU for a per

[WiX-users] Check for 'power user' in Condition

All - Starting from the Condition element schema documentation at http://wix.sourceforge.net/manual-wix2/wix_xsd_condition.htm, and also trying this list's archives, I'm failing to find documentation on what inner text values are allowed in a Product Condition (e.g. LaunchCondition). The excellen

Re: [WiX-users] Error in Installing to GAC

Just to note I expect it's failing on Windows 2000 because that operating system does not support Win32 side-by-side assemblies (which do have an external manifest file). In both cases the 'manifest' contains a list of all the files making up the assembly. For example, the Visual C++ 2005 C runtime

Re: [WiX-users] Error in Installing to GAC

I would say that only the DLL file should go in the GAC, the other files should go elsewhere. AssemblyManifest really only applies to multi-file assemblies and it should point to the file that contains the assembly's manifest. For .NET assemblies this is the DLL file, all other files are typically

Re: [WiX-users] Directory in user profile but not in RemoveFile table

See Rob Mensching's blog entry "How to create an uninstall shortcut (and pass all the ICE validation)" for information on how to do this. http://robmensching.com/blog/archive/2007/04/27/How-to-create-an-uninstall-s hortcut-and-pass-all-the.aspx -- Mike Dimmick _ From: [EMAIL

[WiX-users] Directory in user profile but not in RemoveFile table

WiX: 3.0.2925 I'm adding a program menu which should be created if it's not there. Other programs install to this menu so I do not want to delete it at uninstall. My XML looks like this: I'm getting a Light error of: error LGHT0204 : ICE64: The directory

Re: [WiX-users] Error in Installing to GAC

I ran across a GAC problem today, did my due Google-ance before bothering the list, and found an old e-mail chain with the same problem. Unfortunately, the resolution wasn't posted. Here is the link to jog your memory: http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg03509.html

Re: [WiX-users] Upgrade InstallShield package

If you can locate the cached MSI file in Windows\installer, opening it with Orca will show the UpgradeCode in the Property table. That might help see if you're on the right track. Versions are also another reason why a major upgrade won't detect an older one. Phil Wilson ___

Re: [WiX-users] wix as a wrapper for NSIS

You may want to consider writing a bootstrapper that strings together your MSI and NSIS packages and installs them sequentially. You can write the bootstrapper in NSIS as well. Then all you need is a simple NSIS uninstall script that calls uninstall on your packages. This way you can avoid a

Re: [WiX-users] Conditionally installing components based on user's locale

I wrote custom action in a DLL which identifies country (specifically North America or Europe) and saves result in a WiX property (it uses MSI API to store property into the table). Then I use this property in component conditions Scott Palmer-3 wrote: > > As part of my setup I would like to

Re: [WiX-users] WiX 3 and the wixui

Problem fixed -checking reveals that this was a fossil left in my folder after Wix 2 was replaced by Wix 3. Failure to remove the reference Wixui.wixlib in the example command line caused the problem. -rob - This SF.net

[WiX-users] Problems with Visual Studio Sp Merge Modules

Hello @All, I am currently having a weird problem with my setup. I have a merge module, which is installed successfully if I run the vcredist_x86.exe for Visual Studio 2005 SP1. This merge need to install some services and run some custom actions. Now, I tried to add the merge modules for VSSP

Re: [WiX-users] wix as a wrapper for NSIS

How is that a change to your requirement? I could tell you how to do this, but I don't feel like advocating what I consider to be a horrible design. This should get you the information you need, but I guarantee you'll be back on this mailing list in a short period of time trying to resolve issues

Re: [WiX-users] Upgrade InstallShield package

Hi Phil, Looking through IS log I see ALLUSERS with a value of 1. Running your script displays "Context 4", so there is a per-machine install done by IS. I have ALLUSERS set to 1 in my WiX source, but there is no detection for the product IS created. A strange thing I saw running your script:

Re: [WiX-users] Detectng Windows XP with Service Pack 2.

((VersionNT > 501) OR ((VersionNT = 501) AND (ServicePackLevel >= 2))) AND MsiNTProductType = 1 This will check for all workstation level OSes that are XP SP2 or higher. If you want to allow servers as well, drop the ' AND MsiNTProductType = 1' from the condition Regards, //aj On 6/8/07, Richar

Re: [WiX-users] Detectng Windows XP with Service Pack 2.

In article <[EMAIL PROTECTED]>, Sankaranarayanan <[EMAIL PROTECTED]> writes: > > Is there any other property wich will distinguish between the different Servi ce Packs. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft availabl

[WiX-users] Detectng Windows XP with Service Pack 2.

Hi, >From WIX 2 - I would like to detect if the client OS is Windows XP with >Service Pack 2. The "VersionNT" property for all Service Packs is 501. Is there any other property wich will distinguish between the different Service Packs. Thanks, Sankaranarayanan MG __

[WiX-users] Are you really big man?

We are delighted to offer you a great deal! You have an extremely great chance to improve your sex life and make yourself twice sexier, because only our clinically tested medicine can guarantee that YOUR DICK will get TWICE as BIGGER as it used to be IN only 6 MONHTS! Check for details: http://ww

Re: [WiX-users] Using variable information in WIX tag attributes

Steve Walch wrote: > As you can see, I know how to use variable [string] attributes, but I can > not figure out how convert my user input into variable YesNo attributes, > Enum attributes, attributes that are references to other tags, attributes > that should be omitted in certain cases, and even

Re: [WiX-users] WiX 3 and the wixui

Robert McConnell wrote: > The offending wixui.wixlib version accompanied the Wix 3 download > dated 5/25/2007 5:36 AM. > Where did you get this download? Wixui.wixlib isn't part of WiX v3; it's been embedded in WixUIExtension.dll for a long time now. -- sig://boB http://joyofsetup.com/ -

[WiX-users] WiX 3 and the wixui

I too have installed Wix 3 to get around the 8.3 issue. I've been working through the example SampleWixUI making changes where necessary to be compatible with Wix 3. I've now encountered the following error: wixui.wixlib : error LGHT0141 : The library file format version 2.0.2207.0 is not comp

Re: [WiX-users] wix as a wrapper for NSIS

Slight change to our requirement here as I can see why the other method would be unreliable. 1 - Launch the MSI, this launches our NSIS installer which installs silently (I've already got this working). This also installs our NSIS uninstall exe. 2 - Running the MSI uninstaller should launch our

Re: [WiX-users] Avoiding registry entries being modified with REINSTALL=ALL REINSTALLMODE=vos

I think you might have to use a RegistrySearch to get the current values and use those as the values to write. Rob Rennie Petersen wrote: > No answers. :-( > > Of course, this is not WiX specific, but I'm wondering if someone could > help me anyway. > > To elaborate, the situation is that

Re: [WiX-users] Avoiding registry entries being modified with REINSTALL=ALL REINSTALLMODE=vos

No answers. :-( Of course, this is not WiX specific, but I'm wondering if someone could help me anyway. To elaborate, the situation is that in my MSI I have not written any mailto:[EMAIL PROTECTED] On Behalf Of Rennie Petersen Sent: 6. juni 2007 19:18 To: wix-users@lists.sourcef

[WiX-users] Using variable information in WIX tag attributes

I have built my user interface for prompting users with setup information and I am having trouble figuring out how to use it all in my WIX tags. For example, I prompt for database creation parameters, which might translate to one of the following, depending on what the user selected: #1 #2 #

Re: [WiX-users] Define constants not working with candle in 3.0.2921.0?

Send us a patch for changes to the html files in the wix\src\chm\html directory. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Fischer Sent: Thursday, June 07, 2007 12:56 PM To: Brian Simoneau; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Define constants not wor

Re: [WiX-users] IISReset

When are you doing iisreset? If you're doing it in the middle of the install then it is possible the rollback system is getting confused. Why are you doing iisreset? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Krishna Kishore Sent: Thursday, June 07, 2007 2:47 PM To: wix-user

Re: [WiX-users] Problems with Major Upgrade

First of all, did your initial installer have an Upgrade Code specified? If it did then this will be fairly straightforward. To make a Major Upgrade, take your current WiX file and: Change the Product Version Change the Product Code Change the Package Code Leave the Upgrade Code the same Crea

Re: [WiX-users] how to do this in wix?

You're going to need a Custom Action, but thankfully it's the simple kind which can be done in WiX. You want a Property like this: http://url-prod.com"; /> And a Custom Action like this: http://url-test.com"; /> Then in your InstallExecuteSequence, and possibly the InstallUISequence if you