Re: [WiX-users] Displaying custom error messages if deferred CA fails

Youmight want to look at src\ext\ca\wixca\dll\CloseApps.cpp in the Wix tools source for an example of using WcaProcessMessage. HRESULT hr = S_OK; UINT er = ERROR_SUCCESS; PMSIHANDLE hRecMessage = NULL; DWORD *prgProcessIds = NULL; DWORD cProcessIds = 0; hRecMessage = ::Msi

Re: [WiX-users] Displaying custom error messages if deferred CA fails [P]

Classification: Public I would love to see your code for that :) " Particularly if the user is going to see It, I try to give a message appropriate to the context with a "Details" button that displays the stack trace." -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com]

Re: [WiX-users] Displaying custom error messages if deferred CA fails [P]

In general, this works well for Immediate custom actions (my custom actions follow a similar pattern). However, for deferred actions, you're not going to be able to set (or get) properties. That being said, logging still generally works. The caveat is that custom actions hooked to DoAction in

Re: [WiX-users] Displaying custom error messages if deferred CA fails [P]

Classification: Public 1. Have a MSI property set up that is empty If the custom action has an error populate the MSI property Display the error via a custom error dialog if the property is not empty? 2. Display the custom action error message in the Custom Action itself (as long as the MSI is

Re: [WiX-users] "The specified Feature name ('FilterDriverx64') not found in Feature table."

Think we have found the problem. The 32- and 64-bit driver installation MSIs have the same Product ID. As always... thanks for listening... -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/The-specified-Feature-name-FilterDriverx64-not-found-in-Fe

[WiX-users] Displaying custom error messages if deferred CA fails

Hi all, I've Googled and searched the WiX mailing list, but I haven't been able to figure this one out yet. One of the biggest problems I've always had with MSIs is that they rarely return useful error messages. I'm using a custom bootstrapper and I'd like to display a custom error message if one

Re: [WiX-users] WiX 3.8 Installer and NetFx 4.5.2 on Win7 x64

For this testing it was a manual install of .NET Framework 4.5.2 Offline Installer (http://www.microsoft.com/en-us/download/details.aspx?id=42642). For our products I prepared our own implementation derived from our Wix NetFx 4.51 definition (which was derived from NetFx451.wxs from WiX Toolset). I

Re: [WiX-users] RemoveFolderEx really slow on large folders

@John: I completely understand why the util:RemoveFolderEx action works the way it works, and for many applications that is the right way to go, and that's why I had used it to begin with. Unfortunately for this particular app it was simply unacceptable to be stuck for 45 minutes during uninstall o

Re: [WiX-users] RemoveFolderEx really slow on large folders

How does rollback work with your CA? > From: Sascha Sertel [mailto:sascha.ser...@gmail.com] > > Yes, what it is getting hung up on is enumerating a hundred > thousand files one by one and adding them up to a giant string > that is passed on to the MSI engine. > > I looked at the RemoveFolderEx C

Re: [WiX-users] RemoveFolderEx really slow on large folders

In general, the table-driven approach that RemoveFolderEx follows is superior. First, it handles locked files appropriately. Second, it does the deletes at the same time and sequence as other deletes are being performed by the installer. Third, it is much safer. Yes, if all the files and sub

Re: [WiX-users] RemoveFolderEx really slow on large folders

Yes, what it is getting hung up on is enumerating a hundred thousand files one by one and adding them up to a giant string that is passed on to the MSI engine. I looked at the RemoveFolderEx C++ implementation and it confirmed all my suspicions, so I went ahead and took it out and created my own m

Re: [WiX-users] WiX 3.8 Installer and NetFx 4.5.2 on Win7 x64

How are you installing .NET 4.5.2? The WiX 3.8 NetFxExtension does not contain a wxs for NetFx452, so I'm assuming you manually specify an ExePackage element for 4.5.2? Since .NET 4.5.2 was just released a couple of days ago I'm sure there aren't a lot of people who have tried to deploy it with Wi

[WiX-users] "The specified Feature name ('FilterDriverx64') not found in Feature table."

We have a small bundle with one 32- or 64-bit driver installation followed by our app. We are getting a failed installation on a 32-bit computer. The gross error is that the 64-bit driver installation appears to be running, and failing, on the 32-bit computer with a message box. Here is our Chai

Re: [WiX-users] w120: Detected partially cached package: BaslerPylonGigEx86, invalid payload: BaslerPylonGigEx86, reason: 0x80070570

Should have waited before posting... :/ After reboot installation runs fine. Thanks for listening... :) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/w120-Detected-partially-cached-package-BaslerPylonGigEx86-invalid-payload-BaslerPylonGigEx86

[WiX-users] w120: Detected partially cached package: BaslerPylonGigEx86, invalid payload: BaslerPylonGigEx86, reason: 0x80070570

We have a small bundle with one 32- or 64-bit driver installation followed by our app. We are getting a failed installation on a 64-bit computer. The gross error is that the 32-bit installation appears to be running, and failing, on the 64-bit computer with a message box. Here is our Chain

Re: [WiX-users] torch create transform

Thank you for pointing that link out. From reading the MSDN link I understand why what I tried to do did not work. Thanks. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/torch-create-transform-tp7594463p7594633.html Sent from the wix-users maili

Re: [WiX-users] torch create transform

hmmm sorry just had a brief look in MSDN. msts seem to not to fulfill the needs for file transformation (which are stored in embedded cabs): A transform can modify information that is in any persistent table in the installer database

[WiX-users] WiX 3.8 Installer and NetFx 4.5.2 on Win7 x64

Hi all, Got some weird behavior with WiX 3.8 Installer (+ our own installer with custom BAL) and I'm interested if anybody else saw that issue as well or if this might be an issue related to 2 badly configured VMs. Same for WiX 3.8 and custom BAL: - Installer installed on these VMs with Net FX 4.

Re: [WiX-users] Problem in Getting the path of executable file and scripts in WIX Installer

I don't understand. The $(var.MyProject.TargetMachine) is only used while compiling the installer and not while using the installer. After compiling the solution you should get one MSI file. You only need to deploy the MSI file to the machine where you want to install. -- View this message in co

Re: [WiX-users] torch create transform

>>Torch for generating transform + apply that transform... This is where I had the problem. I created the two msi packages (a and a.modified) and I created the transform (brand.mst). The difference between the two MSI packages was that I used Orca to extract and then import a changed Icon from

[WiX-users] Problem in Getting the path of executable file and scripts in WIX Installer

I want to develop a installer using WIX in which we want to run 3 set up simultaneously: DB Script, Console application and Web service. I have develop the WIX Installer solution using VS2012 and have insluded the console application and webservice solutions too within the same solution. So, when r

Re: [WiX-users] Problems using Wix Toolset 3.8 in Visual Studio 2013

Aparna: Thanks very much for the reply. By watching the You-Tube video produced by DMC, I eventually discovered that the instructions in the "Creating a Simple Setup" tutorial are incorrect, at least for use with VS 2013. As you mentioned, the answer is to add the new Wix project to the exist

Re: [WiX-users] torch create transform

hmmm I'm not thinking right now at all the appoaches what might get wrong when "both" MSI + (MSI + Transform) run on the system. Only apout the approach to modify an MSI by transform. In general it should be possible to transform an MSI into another using a mst file. So I think of 2 approaches: -

Re: [WiX-users] Problems using Wix Toolset 3.8 in Visual Studio 2013

Dit mailadres is niet meer in gebruik. Mail kan je voortaan sturen naar basti...@careercontrol.nl. -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your pro

Re: [WiX-users] Problems using Wix Toolset 3.8 in Visual Studio 2013

Hi Ken, I followed the steps you have written and reached to the point of problem however the solution is very simple. If you follow the link exactly you'll end up creating two separate solutions and in that case you won't be able to add a project reference. You'll get error saying this type of