Re: [WiX-users] How to add All user option?

Hi, I think this is what you're looking for: Add this in your dialogs Dialog Id=CustomerInfo Width=370 Height=270 Title=[ProductName] Setup Control Id=Next Type=PushButton X=236 Y=243 Width=56 Height=17 Default=yes Text=Next /

[WiX-users] how to supress cmd prompt in custom action

Hi Eitan, When i run custom action(which calls msbuild prof file) it is poping up cmd prompt window. I want to supress this cmd prompt, how to do this any idea? My sample CustomAction Id=InvokeSampleEXESSO Property=SampleEXE

Re: [WiX-users] invoking batch file inside wxs file

Tallow is a v2 tool which is (supposed to be) replaced by heat in v3. However the functionality you're trying to use isn't available by heat so you have to do some extra work to get valid WiX v3 code generated. There is a tool called WiXCop.exe which is used to transform v2 code into v3 code.

Re: [WiX-users] how to supress cmd prompt in custom action

Use QtExec. It's in the WiX.chm. Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No.

Re: [WiX-users] how to modify proprty value in wix

msbuild is expecting the string surrounded with , i.e. D:\Program Files\Microsoft BizTalk Server 2006, you don't need the %20 character. On Wed, Nov 19, 2008 at 11:23 AM, Chandra Vuppala [EMAIL PROTECTED] wrote: Hi, How to modify the property value in wix? I have property called

[WiX-users] LaunchConditions

Hi all, Will the LaunchConditions be checked during the uninstall process? I need some helps to overcome the uninstall problem. I have a Condition checking the existence of the dependent software - SQL server SSAS 2005 SP2. However, user can go ahead uninstall SQL server without knowing my

Re: [WiX-users] LaunchConditions

Modify your LaunchConditions so they have OR Installed in the inner text. That way your LaunchCondition will be true when the user attempts to uninstall. This (unknowingly) caught me out for a while too until my excellent QA colleagues noticed it alerted me to it. Palbinder Sandher Software

[WiX-users] LaunchConditions Dialogbox

Hi All, I am developing an MSI with WiX v3, I want to perform some pre-requisites checks i.e. Launch Conditions before launching the installation. Example CodeSnippet: !-- Launch conditions -- Condition Message='You have to be a local administrator to install

[WiX-users] daisy chaining DLLs in custom actions

hi all, I'm trying to do a system verification step as part of my install, but I've encountered a small problem with the standard custom action dll solution. I've created a CustomActions.dll to contain a isValidSystem call. unfortunately, the algorithm to validate the system is inside yet another

Re: [WiX-users] wix v3 question

There is no Property to set but you can Condition your Components so they only install things that are supported by the underlying OS. Someone else just asked this question yesterday, I think. -Original Message- From: Yung Wu [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2008

Re: [WiX-users] daisy chaining DLLs in custom actions

If you own the code for tools.dll, you can change it to a library and link the library in CustomActions.dll. Otherwise, you will have to extract tools.dll onto the system before using it. There is no built-in way to do this. -Brian Simoneau -Original Message- From: Oren Mazor

Re: [WiX-users] how to supress cmd prompt in custom action

WiX.chm shows how to do this. -Original Message- From: Chandra Vuppala [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 00:49 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] how to supress cmd prompt in custom action Hi Eitan, When i run custom

Re: [WiX-users] LaunchConditions

Yes. http://robmensching.com/blog/archive/2008/11/03/How-to-determine-if-you-are-installing-on-Windows-Client.aspx suggests using the Installed property. -Original Message- From: Jiang, Tony [Avanade] [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 06:24 To: WiX-users

Re: [WiX-users] daisy chaining DLLs in custom actions

Oren, you should include tools.dll as a resource inside CustomActions.dll (or just include it at the end of the file using some mechanism whereby you can pull it back out), and then extract it to a temp folder during your initial processing in CustomActions.dll and load it using LoadLibrary.

[WiX-users] Adding buttons to the ProgressDlg

HI, A tough problem - I'm not sure if it can be done with Wix/WI Is it possible to add a hidden control (in my case a button) to the ProgressDlg, which is hidden until a specific DEFERRED custom action is executed? Thanks Karl -- View this message in context:

Re: [WiX-users] Adding buttons to the ProgressDlg

In article [EMAIL PROTECTED], Karl Denning [EMAIL PROTECTED] writes: Is it possible to add a hidden control (in my case a button) to the ProgressDlg, which is hidden until a specific DEFERRED custom action is executed? What is it you really want to achieve with this mechanism? And no,

[WiX-users] Modifying the MSI file at runtime using DTF

Hi, I am trying to modify the MSI file at runtime, basically, I am running a DTF Custom Action (immediate, after InstallInitialize) that extract certain Binary files, modify them, and save them back into the MSI file. The problem is that I cannot save the files back to the binary table. I am

Re: [WiX-users] Modifying the MSI file at runtime using DTF

You can't do that. The MSI is readonly. What are you trying to accomplish? -Original Message- From: Eitan Behar [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 09:47 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Modifying the MSI file at

Re: [WiX-users] daisy chaining DLLs in custom actions

what about creating a separate feature+component that installs that DLL into the temp folder, somewhere, does the evaluation required, and then does a rollback? actually, that may not be possible, since my custom actions need to occur before launch conditions, which occurs before any features

Re: [WiX-users] Adding buttons to the ProgressDlg

Sorry - I was trying to reduce the task to a minimal sentence because the big picture is fairly complicated, and I think will turn off most people. Here goes The application relies on a database, which is unique per installation. The database, although is not very large, takes 2-5minutes to

Re: [WiX-users] Adding buttons to the ProgressDlg

Async CustomAction? -Original Message- From: Karl Denning [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 10:29 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Adding buttons to the ProgressDlg Sorry - I was trying to reduce the task to a minimal sentence

[WiX-users] Removing registry key that is under HKCU fails to compile

Hello Everyone, I am trying to remove a registryentry which is under HKCU. Component Id=3DRemoveLicenseAgreementRead Guid=3D{0A820032-635B-4f23-AF53-F1832F866525} CreateFolder/ RemoveRegistryKey Action=3DremoveOnUninstall Root=3DHKCU Key=3DSoftware\Test\LicenceAgreementRead/ /Component This

[WiX-users] FW: Removing registry key that is under HKCU fails tocompile

This is the code... Component Id=3DRemoveLicenseAgreementRead Guid={0A820032-635B-4f23-AF53-F1832F866525} CreateFolder/ RemoveRegistryKey Action=removeOnUninstall Root=HKCU Key=Software\Siemens\GMS\LicenceAgreementRead/ /Component Thanks and Regards, Surekha -Original Message- From:

Re: [WiX-users] Modifying the MSI file at runtime using DTF

I am trying to do the almost famous replaces on SQL Scripts before running them. I only have a few days to do that, and cannot get into writing a generic C++ as an add-on to the existing SQL Extensions. There are a bunch of SQL scripts, which I cannot modify, and they have a lot of replaceable

Re: [WiX-users] Modifying the MSI file at runtime using DTF

Hmm, yeah, sorry, I don't know of a hacked way around the scenario. -Original Message- From: Eitan Behar [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 10:54 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Modifying the MSI file at

Re: [WiX-users] Modifying the MSI file at runtime using DTF

There is an alternative approach here http://neilsleightholm.blogspot.com/2008/08/executing-sqlcmd-from-wix.html that might be useful. Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] From: Eitan Behar [mailto:[EMAIL

Re: [WiX-users] Modifying the MSI file at runtime using DTF

Hi Neil, Thanks, I already went to it, and even recommended to a few people. But, I cannot use it on my scenario since the MSI are deployed on servers without SQL installed. SQL is running in a different server where I don't have access. Thanks, Eitan - beginning to be frustrated

Re: [WiX-users] Modifying the MSI file at runtime using DTF

Well, not good, not good, what would u suggest? A bright idea might save my day -Original Message- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 9:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Modifying

Re: [WiX-users] Modifying the MSI file at runtime using DTF

I will help you. Chris On Wed, Nov 19, 2008 at 2:12 PM, Eitan Behar [EMAIL PROTECTED] wrote: Well, not good, not good, what would u suggest? A bright idea might save my day -Original Message- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008

Re: [WiX-users] Modifying the MSI file at runtime using DTF

Heya Rob, I asked once before, but I guess I got lost in the crush... I have improvements to submit, where should I send them? I've added some things to heat, and I'd be willing to muck around in there a bit more if there are any serious issues pending. I also would like to make some changes to

Re: [WiX-users] what is the recommended way for setting the AppPool associated with a new iis:WebSite?

Thanks this helps. Btw - are there currently any plans to remove the wix3 requirement for w08/iis7 installs to have the iis6 metabase mgmt compatibility features installed in order for iis:* / installer activities to do their thing? -Original Message- From: Amy Rosewater

Re: [WiX-users] Modifying the MSI file at runtime using DTF

Derr, sorry, this was supposed to be just to Rob. :-D Chris On Wed, Nov 19, 2008 at 2:26 PM, Christopher Karper [EMAIL PROTECTED] wrote: Heya Rob, I asked once before, but I guess I got lost in the crush... I have improvements to submit, where should I send them? I've added some things

Re: [WiX-users] Adding buttons to the ProgressDlg

I'm on the verge of trying that. async + wait for return code looks like the type I should use. I've been digging around MSDN, but cannot find info... Rob - could you answer some general Qs regarding async CAs? 1. Does WI display the ProgressDlg until all async CAs have finished? 2. What

Re: [WiX-users] Adding buttons to the ProgressDlg

1. Don't think so. 2. Not sure. 3. Not sure it can participate in rollback. 4. I don't know if the Windows Installer cares. Note: I didn't read the MSI SDK closely so you'll probably get more specific answers there. -Original Message- From: Karl Denning [mailto:[EMAIL PROTECTED]

Re: [WiX-users] what is the recommended way for setting the AppPool associated with a new iis:WebSite?

There is a bug open. There is a tremendous amount of work to fix that bug. I'm not particularly happy with the IIS team. So I'm not particularly motivated to spend my free time cleaning up after them again. Maybe someone else is more interested in making the story work better. What is

Re: [WiX-users] Modifying the MSI file at runtime using DTF

Very easy to get lost in the crush. Especially since only this week have I finally felt like I'm able to breathe again. Send the information to wix-devs. I'm *way* behind on processing data there. Make sure you've already signed the assignment agreement. -Original Message- From:

[WiX-users] cpa:ComPlusSubscription failing

Hi, I'm having issues trying to use wix to set up a complus application. Wonder if anyone can provide any insight... It all works fine for the components and event classes, but as soon as I include the subscriptions, the install fails. After failure, the msiexec log contains:

[WiX-users] WiXLib installed files not being uninstalled

I've created a very simple installer to test some things.  In this case, we deploy 32-bit and 64-bit assemblies that are very similar.  I thought it would be easiest to make a WixLib project, write the logic to get the assemblies based on the Platform.  This has so far worked very well.  I

Re: [WiX-users] LaunchConditions Dialogbox

sujanakar reddy wrote: When the launch conditions fail the Error Message(dialog box) is coming at the top of the screen and the UserExit dialog (my custom dialog) also shifted to top of the screen. My requirement is to display these dialog boxes at the center of the screen. Change the

Re: [WiX-users] WiXLib installed files not being uninstalled

David Terrell wrote: However, upon uninstall only the files/keys listed in the main MSI's XML are uninstalled, while the WiXLib's files/keys are left behind. Get a verbose log on uninstall and check around the InstallValidate action to see the actions MSI is taking for the component. MSI

Re: [WiX-users] Adding buttons to the ProgressDlg

In article [EMAIL PROTECTED], Karl Denning [EMAIL PROTECTED] writes: The application relies on a database, which is unique per installation. The database, although is not very large, takes 2-5minutes to build. [...] What I would do is: 1) Have a CA that does the necessary part (I

Re: [WiX-users] daisy chaining DLLs in custom actions

In article [EMAIL PROTECTED], Oren Mazor [EMAIL PROTECTED] writes: what about creating a separate feature+component that installs that DLL into the temp folder, somewhere, does the evaluation required, and then does a rollback? You can't rollback features, only products. The typical

[WiX-users] Votive (3.0.4318.0) with VS2005

I am wondering if I have missed any steps to install Votive for use with VS2005 ... ProjectAggregator2.msi was installed first, then Wix-3.0.4318.0.msi. Other than not getting descriptive error messages (just error code numbers - the subject of my earlier posting), things seem to be working until

[WiX-users] correct way to enable commadn line support for defining features/subfeatures that are selected and unselected by default when you step into interactive install UI experience

I have the following logic in each of my feature/subfeature settings so that from the command line users can easily define what features/subfeatures are selected and unselected by default when they step into the interactive install or run and unattended install. When I run my msi in

Re: [WiX-users] using a variable for Component Win64 attribute value still generating generic warning not uniquely suppressible in wixproj | build | suppress specific warnings field

So basically I no longer need to include the Win64 attribute except in cases where the value for a specific component has to be a specific value regardless of what the Platform setting is? -Original Message- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2008

Re: [WiX-users] Adding buttons to the ProgressDlg

That's roughly what we have. The algorithm that generates the records is CPU hungry, which is one reason to offload it to the installer - get as many records generated when user doesn't care so much about performance issues. We have a load of other optimization tricks in place, but this one

Re: [WiX-users] WiXLib installed files not being uninstalled

Thanks, Bob. It appears that somehow my Component ID got tied up with another client. I swapped in a fresh GUID and all is fixed. I have another question in that original email, but because I search so often, I think I'm going to start a new thread so other people searching will have something

[WiX-users] Multiple instance patches

I've been playing around with installing multiple instances of an application used the InstanceTransforms / element, works quite well. I'm trying to create a patch between 2 versions and apply that one patch to multiple installed instances and according to

[WiX-users] Install fails when calling NetFxScheduleNativeImage

The following is a portion of an MSI log that I believe shows the problem. I could be wrong about that, reading MSI logs isn't the easiest thing in the world. The way I read this, it's removing files and then calls the NetFxScheduleNativeImage. Is that called when an assembly is being removed?

Re: [WiX-users] Combobox not refreshing

siaj wrote: Thanks ! but dont think this solution will work becuase I need to have the server name and the database name on the same screen and I would like to refresh the database name changed on click of the button (on same screen) or value changed of Server Name drop down. Thanks,

[WiX-users] CreateDatabase processing failing because databasehostname public property assignment using [%ComputerName] doesn't appear to be working

If I use the following Property Id=DATABASESHOSTNAME Value=[%ComputerName] my log output shows something other than what I'd expect Property(S): DATABASESHOSTNAME = [%ComputerName] and my CreateDatabase call that uses the public property DATABASESHOSTNAME fails If I use the following Property

[WiX-users] what's the custom action name I use to sequence a custom action to process just before/after CreateDatabase activities?

I have a custom action that I wanted to schedule to happen just before CreateDatase processing occurs. I tried the following custom action sequencing statement Custom Action=QtExecCmdLineRun5 Before=CreateDatabaseNot Installed/Custom and when I compile I get the following error Error 1

Re: [WiX-users] CreateDatabase processing failing because databasehostname public property assignment using [%ComputerName] doesn't appear to be working

Hello Robert You can't set the value of a property from another property that way. Not supported in the MSI. If you wish to do this you need to use a custom action type 51 to do this. Regards Michael -Original Message- From: Robert O'Brien [mailto:[EMAIL PROTECTED] Sent: Thursday,

Re: [WiX-users] Adding buttons to the ProgressDlg

In article [EMAIL PROTECTED], Karl Denning [EMAIL PROTECTED] writes: That's roughly what we have. Except you're doing the CPU hungry bit as part of the install transaction. It doesn't need to be there. Trying to put it there is giving you the headache of trying to figure out how to

Re: [WiX-users] Combobox not refreshing

siaj wrote: Thanks ! but dont think this solution will work becuase I need to have the server name and the database name on the same screen [...] Its been my experience that these needs are being dictated by someone inside your company, but the actual user could care less. -- The

Re: [WiX-users] Adding buttons to the ProgressDlg

Plus, the install is already I/O heavy. You might just be slowing slow stuff down more and actually get better performance the way Richard is suggesting. -Original Message- From: Richard [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 18:47 To: General discussion for

Re: [WiX-users] correct way to enable commadn line support for defining features/subfeatures that are selected and unselected by default when you step into interactive install UI experience

MSI also has ways of controlling features using ADDLOCAL and friends. That might work better... -Original Message- From: Robert O'Brien [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 14:05 To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users]

Re: [WiX-users] Install fails when calling NetFxScheduleNativeImage

Is that the first instance of value 3 in the log file? If not can you share that part of the log file. If so, it does appear that the SchedNetFx entry point failed. I don't know that code well and there is nothing useful in the log, unfortunately. -Original Message- From: John

Re: [WiX-users] Install fails when calling NetFxScheduleNativeImage

Yes, that's the first value 3 in the log file. -Original Message- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 10:56 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Install fails when calling

Re: [WiX-users] what's the custom action name I use to sequence a custom action to process just before/after CreateDatabase activities?

Try ConfigureSql On Wed, Nov 19, 2008 at 9:24 PM, Robert O'Brien [EMAIL PROTECTED] wrote: I have a custom action that I wanted to schedule to happen just before CreateDatase processing occurs. I tried the following custom action sequencing statement Custom Action=QtExecCmdLineRun5

Re: [WiX-users] CreateDatabase processing failing because databasehostname public property assignment using [%ComputerName] doesn't appear to be working

And I don't think you need it as an env. var. [ComputerName] is a built-in msi property if I'm not mistaken. But Michael is right, type 51 CA On Wed, Nov 19, 2008 at 9:23 PM, Robert O'Brien [EMAIL PROTECTED] wrote: If I use the following Property Id=DATABASESHOSTNAME Value=[%ComputerName]

Re: [WiX-users] Install fails when calling NetFxScheduleNativeImage

John Vottero wrote: Yes, that's the first value 3 in the log file. See http://www.joyofsetup.com/2008/07/15/verbose-logging-from-wcautil/ for how to enable verbose logging. The NativeImage CAs log a fair bit of additional info. -- sig://boB http://joyofsetup.com/

Re: [WiX-users] using a variable for Component Win64 attribute value still generating generic warning not uniquely suppressible in wixproj | build | suppress specific warnings field

Robert O'Brien wrote: So basically I no longer need to include the Win64 attribute except in cases where the value for a specific component has to be a specific value regardless of what the Platform setting is? Yes, but it's only valid when you need to specify a 32-bit component in a