[WiX-users] Problem in using Conditions.

Hi All, I have a problem in using condition. I have used the Condition like below. It works fine While installing, But after installing if I tried to uninstall the condition is getting failed and could not able to uninstall. Please help me out in this regard . Condition Message='The UDDI DB

[WiX-users] Obtaining a property and running an exe if, and only if a property contains a value

Hi: I am testing a registry value (a string) for a previous installer written with another product, if the installation exe is found, I want to firstly obtain another registry value (a string) and then run the previous installer before re-installing the product using my installer. What is the

[WiX-users] Problem about installing windows services, need help!

Hi, all~I ran into this weird problem as follows: I'm using WiX3.0 to build an installation package which will install several windows services, but I can't start the service correctly, every time I got the message: Service 'PublishService' failed to start. Verify that you have sufficient

Re: [WiX-users] Problem about installing windows services, need help!

Sorry to bother, the command line I used in the Visual Studio 2008 Command Prompt is InstallUtil PublishService.exe. 2009/8/20 bonn deng bonnd...@gmail.com Hi, all~ I ran into this weird problem as follows: I'm using WiX3.0 to build an installation package which will install

[WiX-users] Actions from Execute sequence in UI

Hi guys, Does anybody know why the following standard sequence actions are allowed in the adminUIsequence table? I thought they should be authored into adminEXECUTEsequence only. Wix though allows to add them to adminUIsequence as well: - InstallValidate, InstallInitialize, InstallAdminPackage,

Re: [WiX-users] Problem in using Conditions.

If you want a launch condition to be always true after first-time installation, so you can uninstall, repair etc, just add Installed or to it. In your case: Condition Message='The UDDI DB Service is not installed' Installed or UDDIDBSERVICE /Condition The condition is case-sensitive.

Re: [WiX-users] Problem about installing windows services, need help!

Hi, Can the service be started manually after it got installed? Best regards, Sebastian Brand Instyler Setup - Creating WiX-based MSI installations, elegantly. http://www.instyler.com -Original Message- From: bonn deng [mailto:bonnd...@gmail.com] Sent: Thursday, August 20, 2009

Re: [WiX-users] Obtaining a property and running an exe if, and only if a property contains a value

Hi Sean, To get the registry values use the RegistrySearch element to set the value to a property. Then use a CustomAction with a condition using that property. Schedule that custom action after InstallInitialize in the InstallExecuteSequence. Best regards, Sebastian Brand Instyler Setup -

[WiX-users] Prevent file deletion duting upgrade

Hello, I have the case below: 1. product.msi 1.0.0 deletes all files (even created by user) on uninstallation 2. product.msi 1.0.1 (RemoveExistingProducts Before=InstallInitialize /) How to prevent particular file deletion on 1.0.0 uninstallation. Maybe it is possible to read file

Re: [WiX-users] SpawnDialog doesn't work

Hello, Check the order of the events in the resulting MSI in the ControlEvent table. Maybe the Publish event you are adding with Order=1 is set after the NewDialog element to show the next page... Best regards, Sebastian Brand Instyler Setup - Creating WiX-based MSI installations, elegantly.

Re: [WiX-users] Prevent file deletion duting upgrade

Hello, By default, Windows Installer never deletes files it doesn't know of (user files). So how is this accomplished in v1.0.0? Best regards, Sebastian Brand Instyler Setup - Creating WiX-based MSI installations, elegantly. http://www.instyler.com -Original Message- From:

Re: [WiX-users] Obtaining a property and running an exe if, and only if a property contains a value

Hi: When is the Install initialize executed. Sean. -Original Message- From: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com] Sent: 20 August 2009 11:30 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Obtaining a property and

Re: [WiX-users] Prevent file deletion duting upgrade

Yes, I know. But for some reasons I have implemented this custom action on uninstall. CustomAction Id=REMOVEDIRS Property=CMD ExeCommand=/C rd /S /Q quot;[INSTALLDIR]quot; Return='asyncNoWait' Impersonate=yes / :) 2009/8/20 Sebastian Brand (Instyler Software)

Re: [WiX-users] Obtaining a property and running an exe if, and only if a property contains a value

Right after InstallValidate. Just set @After=InstallInitialize when adding the custom action to the sequence Best regards, Sebastian Brand Instyler Setup - Creating WiX-based MSI installations, elegantly. http://www.instyler.com -Original Message- From: Sean Farrow

Re: [WiX-users] Prevent file deletion duting upgrade

Uh that's bad. Then I'd create a new custom action to copy user files to the new folder before removing the the old version. Using properties to store the contents of a file is probably not working... Also applications shouldn't store user files in the Program Files installation folder. Since

Re: [WiX-users] Obtaining a property and running an exe if, and only if a property contains a value

Ok: Does the InstallInitialize action ocure before any ui for the new installer? Ideally, I would like all this to occure before any new ui. Sean. -Original Message- From: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com] Sent: 20 August 2009 12:34 To: 'General

Re: [WiX-users] Obtaining a property and running an exe if, and only if a property contains a value

To schedule it before any UI is shown, it must be sequenced in the installUIsequence, probably before CostInitialize. But this will remove the old version before the user has seen any UI and won't be able to stop uninstallation. In Windows Installer it would be more common sense to perform the

[WiX-users] Determine the Directory of an IIS Web Site

I need to install some files to the root of an existing IIS website. What would be the best way to handle this? Does the WebSite element create any sort of reference to its root? I've searched for how to do this for a while to no avail. Hopefully, this is just something simple that I'm

[WiX-users] XmlConfig to write raw xml

Is it possible to use XmlConfig to write raw xml as an element inner xml? For instance, in sample data value=1 / /sample Can I write data value=1 /? How will util:XmlConfig look like? -- Let Crystal Reports handle the

[WiX-users] How to work with ALLUSERS

I need a sample wxs file which can install files to different location based on the value of ALLUSERS. Example:- allusers=1, some selected files will be installed to commonappdata folder(C:\Documents and Settings\All Users\Application Data). allusers={}, the above files will be installed

Re: [WiX-users] Problem about installing windows services, need help!

Is you service dependent on any components in the GAC? If it is, then Windows Installer cannot start it because it tries to start the service before it has registered the components in the GAC. The only way round this I know is to use a custom action to start the service (or don't use the GAC).

Re: [WiX-users] How to work with ALLUSERS

The most reliable way would be to duplicate the components installing the files and condition them (one set uses ALLUSERS and the other set uses NOT ALLUSERS). You may be able to use the preprocessor's foreach to avoid duplicating the source code (note, I have not tested this): DirectoryRef

[WiX-users] IPersistFile::Save return 0x8007007b in custom action.

Hi, I have a custom action which creates a link (shortcut). The calling process between layers is: a) The function of creating link is implemented in a C++ DLL. It uses IPersistFile::Save to save the link. b) The function is wrapped in C# code using P/invoke. c) My C# custom

Re: [WiX-users] IPersistFile::Save return 0x8007007b in custom action.

Not sure, but why aren't you using MSI's Shortcut table instead of rolling your own? -Original Message- From: Lian Jiang [mailto:lji...@microsoft.com] Sent: Thursday, August 20, 2009 10:40 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users]

Re: [WiX-users] IPersistFile::Save return 0x8007007b in custom action.

That error code is The filename, directory name, or volume label syntax is incorrect. Not sure which of the two paths it doesn't like. -Original Message- From: Blair [mailto:os...@live.com] Sent: Thursday, August 20, 2009 11:49 AM To: 'General discussion for Windows Installer XML

[WiX-users] showing a message with an ok button

Hi: What is the best way with wix of showing a message with just an ok button. Regards Sean. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design,

Re: [WiX-users] Passing Preprocessor variables when using msbuild

Those variables are MSBuild variables. To reach candle, they need to be added to one of the DefineConstants property. You could try adding this to your $(ROOT)\INSTALLERS\Test.wixproj file (note, this is untested): PropertyGroup

Re: [WiX-users] showing a message with an ok button

Hi Sean, take a look at this tutorial: http://www.tramontana.co.hu/wix/lesson8.php#8.3 Unfortunately we're unable to customize interfaces already created, apart from text messages and disable/hide controls via conditions. So usually we just copy some existing UI and tailor it for our needs. If

Re: [WiX-users] showing a message with an ok button

Some context? Not quite sure what you are trying to accomplish. -Original Message- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: Thursday, August 20, 2009 12:22 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] showing a message with an ok

Re: [WiX-users] IPersistFile::Save return 0x8007007b in custom action.

Thanks Blair. I am trying to create a shortcut under $(env.SYSTEMDRIVE)\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start menu\Programs\Startup, but I did not find any Folder property to do this declaratively. That's why I create my own custom action. I once made below scenario

Re: [WiX-users] showing a message with an ok button

Basically, if a product already exists, I want to tell the user and then run the existing uninstaller. Chers Sean. -Original Message- From: Blair [mailto:os...@live.com] Sent: 20 August 2009 20:30 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users]

Re: [WiX-users] IPersistFile::Save return 0x8007007b in custom action.

I figured out that how to do below thing using shortcut table: create a shortcut under $(env.SYSTEMDRIVE)\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start menu\Programs\Startup Thanks for reminder. Cheers Lian -Original Message- From: Lian Jiang Sent: Thursday,

Re: [WiX-users] Prevent file deletion duting upgrade

Hi, Just to provide an alternative, I personally use a CA which modifies the existing (1.0.0 in this case) MSI before REP happens. Sounds absolutely horrible (I almost pitched a fit when my boss suggested it) but, hey, it works. My CA is a VBS / WSF which uses the MSI COM API to load the

Re: [WiX-users] How to work with ALLUSERS

Need some help to debug this:- Question :Do I have to put the foreach block into some directoryRef? If so how do I do it(since directory ref could be CommonAppDir1 or PersonalDir1). Also, this foreach section is not added into Feature/Feature block. I got the following errors when compiled.

Re: [WiX-users] Passing Preprocessor variables when using msbuild

Hi Blair, Thanks for replying. I have declared them the way you have mentioned. But it still doesn't get those values passed. Don't know why? Thanks. On Thu, Aug 20, 2009 at 3:20 PM, Blair os...@live.com wrote: Those variables are MSBuild variables. To reach candle, they need to be added to

Re: [WiX-users] How to work with ALLUSERS

No, with the Directory attribute set you don't need the Components inside a DirectoryRef. You do need to make the Ids and guids unique, however. I suggest the guids are '*' and the ids incorporate $(var.directory) (or anything else you are willing to define that you will vary). ?foreach

Re: [WiX-users] Passing Preprocessor variables when using msbuild

Set your msbuild log verosity to diagnostic and look at: 1) What your properties' values are, and 2) What your candle commandline is. -Original Message- From: Sam K [mailto:sam.re...@gmail.com] Sent: Thursday, August 20, 2009 2:07 PM To: General discussion for Windows Installer XML

[WiX-users] How to strip the leading '#' from a numerical value retrieved from a reg key using RegistrySearch

I retrieve the IISPORT from the registry as follows: Property Id=IISPORT RegistrySearch Id=IISPortSearch Type=raw Root=HKLM Key=SYSTEM\CurrentControlSet\Control\ServiceProvider\ServiceTypes\w3svc Name=TcpPort / /Property And build the url to our web page like this:

Re: [WiX-users] Prevent file deletion duting upgrade

It's too late if you've already shipped that product, but for future reference if you have an uninstall custom action that you do NOT want to run during an upgrade add the condition NOT UPGRADINGPRODUCTCODE. That property is set in the old product being uninstalled during an upgrade. Phil

Re: [WiX-users] How to work with ALLUSERS

I am still getting the following errors:- G:\WiX3\ACT Network Sync\ACT Network Sync\Product.wxs(157,0): error LGHT0091: Duplicate symbol 'File:Act.Data.dll3' found. G:\WiX3\ACT Network Sync\ACT Network Sync\Product.wxs(157,0): error LGHT0092: Location of symbol related to previous error.

Re: [WiX-users] How to work with ALLUSERS

Dictionary, directory, both are in my email client's spell-check. Sorry. And yes, you should modify the File/@Id values the same way as the Component/@Id values. If you don't change the directory paths (or if you do, it is because you really are changing directories) and you don't alter the file

Re: [WiX-users] How to strip the leading '#' from a numerical value retrieved from a reg key using RegistrySearch

DWORD registry values will always have a prefixed '#' character. It is possible for it to get a '+' or a '-' character following the '#' and preceding the actual number (in decimal aka base-10). You'll need a custom action to parse/strip it. The Windows Installer's formatted syntax doesn't have