[WiX-users] Custom Actions Missing in InstallExecuteSequence

For some reason, when I make an msi build using WiX, sometimes the MSI that comes out is missing custom actions in my InstallExecuteSequence. The custom actions are correctly identified in the CustomActions table in Orca but in the InstallExecuteSequence, they are not there. This doesn't happen to

Re: [WiX-users] Uninstall question

It's fixed after reinstalling. Thank you! -- From: "Leung, John C.H." Sent: Tuesday, May 11, 2010 3:12 PM To: Subject: [WiX-users] Uninstall question > I understand that the uninstall information is store in registry key: > > HKEY_LOCAL_MACHINE\SO

Re: [WiX-users] CA only on initial install

We use it with (we call it runtime.wxi :)) and put that inside a . Follow the CA declarations to see when these properties are being set. It's basically after FindRelatedProducts, AppSearch, etc. where all this stuff becomes available. We typically use them much later in the sequences (eg. for

Re: [WiX-users] CA only on initial install

If you're doing major upgrade, Installed is not sufficient. Check out this post: http://code.dblock.org/ShowPost.aspx?id=101. It tells you how to define FirstInstall: when product is installed for the first time Upgrading: when we run upgrade for the installed product RemovingForUpgrade: when

Re: [WiX-users] CA only on initial install

btw i could only get this to work by changing the block to and putting everything inside a block. The resulting file i named defines.wxs and compiled and linked. Is this how you use it? Also: Do you know how early/late in the installation process these properties can be used, assuming above

Re: [WiX-users] Uninstall question

Try this Run the command MSIEXEC /X Notice the same message. No installer is involved. Message is coming from MSIEXEC.EXE or other Windows components associated with it. Message is not coming from an installer. It's using a slightly different code path depending on where you run it from (Command

[WiX-users] createAndRemoveOnUninstall for registry VALUE?

Using Wix 3.5. It seems "createAndRemoveOnUninstall" works on the key. How would you use that logic only on the value under the specified key? That is, the key should not be removed - only the its sub value "InstalledComponent1". Thanks

[WiX-users] Uninstall question

I understand that the uninstall information is store in registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ And the uninstall string is store in value "UninstallString". If I actually execute that command (which is "MsiExec.exe /X{---MyGUID---}), I would get a

Re: [WiX-users] CA only on initial install

WOW now that's a clean way of doing it! Beautiful. Huge thanks! One little suggestion: consider adding how to include that as a .wxi ;) On 5/11/2010 22:04, dB. wrote: > If you're doing major upgrade, Installed is not sufficient. > > Check out this post: http://code.dblock.org/ShowPost.aspx?id=10

[WiX-users] major upgrade, overwriting non-versioned files...

Hello! So I have this WiX problem doing a major upgrade. I have made some progress since I started, but I'm fairly stumped on exactly what to do now. I was having trouble with the SettingsXml file, but now it does remain intact as I need it to. Then I tried to make the two database components

Re: [WiX-users] Upgrade no longer work when I use WebVirtualDir element

Working great for me. I even nest WebVirtualDir three levels deep in my project and have not hit a problem yet and no reports from customers. We've had 5 major upgrades since our product shipped. You don't mention what it does or doesn't do when you use that element. Does the MSI not launch? Does

[WiX-users] Upgrade no longer work when I use WebVirtualDir element

I'm not sure if this is a bug if a desired behavior. There are plenty of reliable examples on how to implement upgrade with WIX. It worked until I started creating IIS virtual directory. I have been scratching my head for a while trying to resolve the problem, and it turned out that it works i

[WiX-users] FW: Custom Action

What is the Registry Path? -- Carolina Zuqueto Amaral tel: +55 21 2494-5476 cel: +55 21 9524-7186 email: carolina.ama...@conv.com.br -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: terça-feira, 11 de maio de 2010 13:48 To: General discussion for Windows Installer XML

Re: [WiX-users] FW: Reset IIS

Ooops, helps to Paste: http://www.dalun.com/wix/06.10.2005.htm -Original Message- From: Chad Petersen [mailto:chad.peter...@harlandfs.com] Sent: Tuesday, May 11, 2010 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] FW: Reset IIS Found this al

Re: [WiX-users] FW: Reset IIS

Found this also. Haven't tried it, but if I had a need it would look promising. -Original Message- From: Chad Petersen [mailto:chad.peter...@harlandfs.com] Sent: Tuesday, May 11, 2010 11:12 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] FW: Reset IIS

Re: [WiX-users] FW: Reset IIS

Dangerous move since other Web applications might be running (without the customer necessarily knowing) and all will fail once the IIS Reset is done. But, if you really want to do that you could, as one alternative, run IISRESET through a custom action. -Original Message- From: Carolina Z

[WiX-users] FW: Reset IIS

I need to reset the IIS in the end of the installation. How Do I do it? Thanks, Carolina Zuqueto Amaral carolina.ama...@conv.com.br tel +55 21 2494-5476 cel +55 21 9524-7186 Confidencialidade: A informa??o contida nesta mensa

Re: [WiX-users] Custom Action

Looks like this command requires admin privileges. Try changing your CA to be deferred and run it before InstallFinalize. -Original Message- From: Carolina Zuqueto Amaral [mailto:carolina.ama...@conv.com.br] Sent: Tuesday, May 11, 2010 9:06 AM To: 'General discussion for Windows Insta

Re: [WiX-users] Custom Action

Hi, I use XMLConfig for this from wix 3.0 from a 32bit MSI. Try:- IISVERSION="#7" AND VersionNT64 Its working fine so far for me. Dave -Original Message- From: Carolina Zuqueto Amaral [mailto:carolina.ama...@conv.com.br]

[WiX-users] Custom Action

Custom Action: ... NOT Installed The appcmd is run, but the configure of the AppPool not is made. What Do I do? Thanks, Carolina Zuqueto Amaral carolina.ama...@conv.com.br tel +55 21 2494-5476 cel +55 21 9524-7186

Re: [WiX-users] Conditional removal of HKCU-key?

I don't think you understand what KeyPaths are. Every Component has a KeyPath. WiX hides this from you most of the time by picking the first File or RegistryKey/RegistryValue in a Component & making it the KeyPath for that Component unless you explicitly tell it otherwise. See -> http://msdn.mi

Re: [WiX-users] Version independent prog id is removed after uninstalling current version

In our product, we maintain the component violation and we instruct our users in such a scenario to run repair on the remaining version if you uninstall from a side-by-side state. A custom action would also potentially work as you suggest Kim, if the scenario is important enough to warrant the e

Re: [WiX-users] Based on CheckBox value have to show the WIX Dialog.

Actually, I'd probably try without having the checkbox hidden. Something in the back of my mind makes me think hidden controls don't behave exactly like visible controls. But, a verbose log file is how I solve just about every run-time install issue I've ever run across. -Original Message-

Re: [WiX-users] Based on CheckBox value have to show the WIX Dialog.

Verbose log file would be where I'd look next. Best of luck Velu. Have a good day. -Original Message- From: Velu [mailto:velusa...@syncfusion.com] Sent: Tuesday, May 11, 2010 8:19 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Based on CheckBox value have to show the WI

Re: [WiX-users] Based on CheckBox value have to show the WIX Dialog.

Hi Chad, As per your suggestion i have changed the CheckBoxValue="TRUE" like below . Its still not working. Any other idea ? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Based-on-CheckBox-value-have-to-show-the-WIX-Dialog-tp5035041p5036

Re: [WiX-users] Based on CheckBox value have to show the WIX Dialog.

In your case don't you want to say CheckBoxValue="TRUE" I'm not sure what your CheckBoxValue="CheckBox" would do, but it doesn't look correct to me. -Original Message- From: Velu [mailto:velusa...@syncfusion.com] Sent: Tuesday, May 11, 2010 8:02 AM To: wix-users@lists.sourceforge.net S

Re: [WiX-users] Conditional removal of HKCU-key?

Thanks for your answer. Just to clarify... This is what I want: 1) HKCU\MyApp\InstallPath should be the key path for the installed exe (and all other files too). 2) HKCU\MyApp must not be removed if HKCU\MyApp\SpecialValue is set. 3) The installation folder for the installed exe must alway

Re: [WiX-users] Based on CheckBox value have to show the WIX Dialog.

Hi Chad, Please look into the codesnippet. By default i have set the property value as True. INSTALL INSTALL AND CHECKBOX_1_PROP INSTALL INSTALL -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.

Re: [WiX-users] Based on CheckBox value have to show the WIX Dialog.

You might want to look at or post your Control element and attributes you have set. Something subtle like Integer="yes" on that Control element would make it act this way since it is not expecting a string in that case. Personally I prefer to use Integer values for WiX checkboxes as they seem a bit

Re: [WiX-users] CA only on initial install

You might think that would be what you'd want, but the upgrade is "NOT Installed" until you install it. That condition would apply to the upgrade and not to the original version you installed. If you're other logic was working you could probably add OR OLDER_VERSION_BEING_UPGRADED. You might want

[WiX-users] CA only on initial install

I promise I Googled this a TON and none of the solutions people posted have worked for me. My problem is, the CA is running during upgrades when it should only run on the very first installation: NOT Installed ... Setup ALWAYS says: NOT Installed :( Could it have anything t

Re: [WiX-users] WiX and TFS Build

The easiest way I have found to do this is to maintain multiple configurations. Use one configuration for the build server and one for development systems. Then pass in the variable into the preprocessor variables in the Wix Project. -Michael Clark -Original Message- From: pmdarrow [mailt

Re: [WiX-users] Version independent prog id is removed after uninstalling current version

This is an interesting problem. The question is: what behavior would be acceptable? If it didn't remove the unversioned progid this would also be a problem because then you would have a progid that points to a component (dll, ocx, exe, ...) that got deleted. Assume we have 3 versions of a product

[WiX-users] Based on CheckBox value have to show the WIX Dialog.

I have to show the Dialog based on the checkbox value. I have set the checkbox property as true initially like below And now show the dialog based on the check box value selection at the time of installation. If it is true i have to show the "Newdoalog_1" if it is false i have to show the "Setu

Re: [WiX-users] Looking for assistance using WIX to rollbackan install upon failure of a custom action.

set your custom action attributes as below - return = check if your custom action return non-zero value the installation fails and roll backs. Peter Shirtcliffe wrote: > Add this: > > > > > > If you already have an installexecutesequence then just add the > element anywhere inside t

[WiX-users] Resiliency repair dialogs

Hi All, We have a problem in our installer, that sometimes when specific COM object is called, installer starts silence repair. And I see next error messages in event log: Detection of product '{955F9F12-0EF2-483F-A50A-12A8C6C9AD8C}', feature 'MyFeature' failed during request for component '{8

Re: [WiX-users] Looking for assistance using WIX to rollbackan install upon failure of a custom action.

Add this: If you already have an installexecutesequence then just add the element anywhere inside that instead. Make sure your existing element has the Execute attribute set to "deferred". If you need it, add a condition inside the element to prevent the action running during

Re: [WiX-users] Version independent prog id is removed after uninstalling current version

This is likely a classic component violation. The component GUID has been revved but the version independent progID remains the same registry key for the two components, meaning the uninstall of any one of the components will remove the key out from underneath the other product since two separat

[WiX-users] Version independent prog id is removed after uninstalling current version

Hi All We have a version independent prog id in a COM dll. We used heat.exe to generate the COM registry keys. 1) Installed the version 3.5 MSI with the com registry keys generated using heat.exe. 2) Installed the version 4.0 MSI with the com registry keys generated using heat.exe, note that CO