Re: [WiX-users] Component condition not works properly

Hi Bob, I think you did not understand my question. I will try explain it again: I have 2 features and 2 components. Where Comp1 belong to feaute F1 and Comp2 belong to F2. My system can be installed in 3 variants: 1) only F1 selected - I am expecting that only Comp1 will be installed 2)

[WiX-users] SQLExtension create database and access denied error

Hello, I'm trying to define a new SQL database using Wix, that has its files (MDF and LDF) in a specific folder (ideally in the user's documents and settings, but this is another story) The thing is when I use the snippet : Directory Id=TARGETDIR Name=SourceDir Directory

[WiX-users] ConditionBased Installation

Hi We have requirement where i need to copy one file say File1 to folder say Folder1 if the system is 64bit Machine else copy File2 to that folder during installation. Please let me know how to write this condition. Thanks in Advance.

[WiX-users] WWWROOT path

Hi There, Can you please help me out to find out the WWWROOT path in wix ? Thanks Jaspreet ***The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any

[WiX-users] Preprocessor and Component Guids

Hey all, I hope I'm missing something obvious. Is there a way for the preprocessor to generate a guid value for a variable? (without making my own custom extension). Something like ?define guid = $(Guid.NewGuid) ? I'm trying to create multiple conditional components like: ?define

Re: [WiX-users] Preprocessor and Component Guids

No, there is no built-in functionality to accomplish that. But the bigger question is why you want to create such components. Ideally, you would have file KeyPaths. Random component guids are usually bad for servicing scenarios. What are you doing with these components? Giving us more details

Re: [WiX-users] Preprocessor and Component Guids

Here's the real use case. I need to create what I'll call an 'Infrastructure Package', specifically for a web service application in a corporate server environment. I need a single unattended MSI that can create an IIS 6.0 web site and application pool based on an environment setting on the

Re: [WiX-users] Preprocessor and Component Guids

No keypath in your component? You are likely to have a hard time with upgrades and servicing if you don't come up with a way to make your generated guids consistent from build-to-build for the same inputs. I would recommend you make a series of RegistryValues (one for each component) and use them

Re: [WiX-users] ConditionBased Installation

Something like this? FolderRef Id=Folder1 Component Id=File.Is64 Transient=yes... ConditionVersionNT64/Condition File Id=File1 KeyPath=yes.../ /Component Component Id=File.Is32 Transient=yes... ConditionNOT VersionNT64/Condition File Id=File2 KeyPath=yes.../ /Component

Re: [WiX-users] Preprocessor and Component Guids

If you can uninstall (and the uninstall of your component actually does something) you have a servicing issue and you need to make your guids consistent from build-to-build for the same flavor component dealing with the same resource set. -Original Message- From: Maillet, Ed

[WiX-users] How to use the FeatureId in a CustomAction condition

I swear I knew this, but for the life of me I can't figure it out: How do I use the Feature Id in a custom action condition ? I used something like this during Install and Uninstall but this doesn't seem to work. Is there a reference on how the ampersand () evaluates when applied to Feature ID

[WiX-users] Installing Device Metadata on Windows 7

I'd like to install Windows Device Metadata for our device via our installer. The process is quite simple and described in http://msdn.microsoft.com/en-us/library/dd835040.aspx. The basic steps are: 1. Query the path of the device meta store by calling SHGetKnownFolderPath with a KNOWNFOLDERID of

Re: [WiX-users] Component condition not works properly

Something like this? ?define F2s-Condition=...? ... Feature Id=F1 ... Condition.../Condition /Feature Feature Id=F2 ... Condition$(var.F2s-Condition)/Condition /Feature Component Id=Comp1 Feature=F1 .../ Component Id=Comp2 Feature=F1 Transitive=yes

Re: [WiX-users] How to use the FeatureId in a CustomAction condition

See Conditional Statement Syntax - http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx Ampersand means action to be applied to the feature. Alex -Original Message- From: Arvind Aiyar [mailto:arvind.ai...@microsoft.com] Sent: Monday, August 31, 2009 11:22 AM To: General

Re: [WiX-users] DTF context, can't access file using absolute path with immediate custom action

Thx Blair. I found the solution, I made a mistake, it was my fault. I was setting a property for my customaction that had the value : [#SearchWeb.config]. Since it was working okay for a deferred customaction, I thought that there would be no problem for an immediate custom action since they

Re: [WiX-users] DTF context, can't access file using absolute path with immediate custom action

MsiFormatRecord() could have been used to expand your value as well. Note also that with [#File.Id] values, on maintenance transactions (such as some minor upgrades and/or removals) it is possible for it to be blank. -Original Message- From: Nicolas Lambert [mailto:nlamb...@coveo.com]

[WiX-users] Custom action from a dialog

I'm trying to use a custom action in a dialog to validate a PID entered by the user. The dialog has a maskededit control that is used to get the string. I have the following sequence defined on the Next button to use to validate the entered data: CustomActionRef Id=ValidatePIDAction/

Re: [WiX-users] SQLExtension create database and access denied error

Hi, When SQL Server creates the database files in the O/S it does so using the identity of the SQL Server Service, the Service identity does not have access to your program files area. I suspect you will have big issues trying to create the database in My Documents for this reason. If you

Re: [WiX-users] Custom action from a dialog

1) When you invoke a CA through a dialog control event, the messages you attempt to write to the log don't end up in the log. You can work around this for debugging by using MessageBox or OutputDebugString to write out logging information. 2) When you invoke a CA through a dialog control event,

Re: [WiX-users] How to add a dialog box when uninstall

Hi Aris, Thanks! I added this in code, then the Remove button is gone in ARP: Property Id =ARPNOREMOVE Value=1 / But the uninstallation is still the simple progress bar. Could you please tell me how to enable maintenance mode? Thanks. From: Aris J. Green

Re: [WiX-users] How to add a dialog box when uninstall

I kept searching for the answer about this issue. But I couldn't find any example to make it work. Can you Wix experts point me out? What else I need to do to show UI in uninstallation, namely, enable maintenance mode? And further how to add a radio button etc. to enable remove user data option

[WiX-users] Installing a new project type

Does anyone know of a good tutorial or a place to get examples that show how to properly register a VSX package? I created a C# subproject along w/ some project templates. I tried using an example that was auto-generated by the VSSDK Assist program, but it looks old (even though I downloaded

Re: [WiX-users] How to add a dialog box when uninstall

By the way, I added this: Property Id =ARPNOREMOVE Value=1 / Then I run the msi again, and I saw the Change and Remove buttons were grey out. There was only the Repair button available. Is this correct? Also, if I run uninstallation from [start]-[All Programs], I didn't even see this UI. I only

[WiX-users] Wix 3.5x x64 version integration with VS2010 works, however 32bit version does not.

Does anyone know of a workaround to get the 32bit version working? Besides applying a couple workarounds to the wxs files, the x64 version is working quite well; however, we are now faced with only some developers can move because the 32 bit version does not install completely. Basically, we

Re: [WiX-users] CustomAction Exectuion by Feature

Dear Blair, Thank you for your advice and concern. Yes, I will use FeatureName=3 style syntax for CustomAction by feature. I don't know what you mean by selected by command internally but if you need help with that please elaborate more. I haven't decided yet how I implement the source

Re: [WiX-users] packa...@installerversion

The Package element populates the MSI's Summary Information Stream. The InstallerVersion attribute populates the Page Count Summary Property (http://msdn.microsoft.com/en-us/library/aa370570(VS.85).aspx) (aka, the Minimum Installer Version) of MSI files. According to

Re: [WiX-users] How to add a dialog box when uninstall

If Change is grayed out you will not get the installer UI you are looking for. Is ARPNOMODIFY set perchance? After you install, what do you see if you double-click the MSI again? You should get the Change experience, which is your starting point to show a modal dialog during your uninstall

[WiX-users] packa...@installerversion

The WiX documentation for the packa...@installerversion attribute is a little vague. I've been searching for a better definition but have come up blank. Where can I find a list of known values for the packa...@installerversion attribute?