Re: [WiX-users] Burn running sql script/ batch /command script in chain.

2012-05-30 Thread Bob Arnson
On 30-May-12 11:17, Benjamin Bennett wrote: > scripts between the msi and the install of sql server. I was hoping to > use the sql extension in wix but cannot put it in order in the chain. Put it in the .msi or, if necessary, create another .msi to do it. Burn is a chainer, not a replacement for M

Re: [WiX-users] Burn and LUA Patching

2012-05-30 Thread Bob Arnson
On 30-May-12 11:14, Hoover, Jacob wrote: > That is the question, though I suspect that it would still need to in order > to update the bundle's installation information. I don't think the patch bundle touches the per-machine bundle's registration. But it would be registered per-user, so it's more

[WiX-users] Bootstrapper VCredist

2012-05-30 Thread Jelani Jackson
Hello all, I am currently working on an installer in which I would need to bootstrap VCredist. As some may know there are two separate files within the C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages folder: Vcredist_x64 Vcredist_x86 I have tried bootstrapping both

Re: [WiX-users] Message Box at the top of Installer Dialog

2012-05-30 Thread Wilson, Phil
Those DTF managed custom actions tree up to call MsiProcessMessage(), so you're restricted to the functionality of MsiProcessMessage. I assume that if the IntelliSense in the dev environment doesn't offer what you want then you can't do it. Phil W -Original Message- From: Ravi Raj [m

Re: [WiX-users] Question on RemoveFolderEx

2012-05-30 Thread Chad Petersen
What version of WiX are you using? I don't believe that RemoveFolderEx would be available until WiX 3.6. Something to consider, at least. -Original Message- From: Shyam Kannam [mailto:shyam.kan...@gmail.com] Sent: Wednesday, May 30, 2012 10:44 AM To: wix-users@lists.sourceforge.net Subjec

Re: [WiX-users] harvesting COM information using heat.exe results in HEAT5150

2012-05-30 Thread Rob Mensching
It's not just not recommended, it's known to introduce more failures into your install. You are trading work up front to get the right registration into your package for failures on customer machines. I personally never understand that trade off. You own the registration code, just look at what it

[WiX-users] Question on RemoveFolderEx

2012-05-30 Thread Shyam Kannam
Hi, I’m pretty newbie on using WiX. I’m having trouble with using RemoveFolderEx in our installer sources. Hope someone could help me with this. Our software application creates temporary folders in our installation directory. On uninstall these folders as well the root folder is not getting

Re: [WiX-users] Burn running sql script/ batch /command script in chain.

2012-05-30 Thread Richard Mayes
How about using ExePackage to run windows cmd and the command-line you need to run with the /c switch Richard Mayes On 30 May 2012 16:17, Benjamin Bennett wrote: > I am trying to use burn as bootstrapper.I have figured out how to > install sql server express and the third party msi's as part of

Re: [WiX-users] harvesting COM information using heat.exe results in HEAT5150

2012-05-30 Thread Michael Scheepers
Hi again, for all others who struggle extracting com information for x86 components on x64 machines. I solved the problem by using regsvr32 in two custom actions. One during installation for registering the second during remove for unregistering the components. I know it is not the recommended

Re: [WiX-users] MSI Uninstall throw exception

2012-05-30 Thread Wilson, Phil
Most likely your code is crashing, the custom action, if the subject line is the issue. That part of the log would have been more useful. that something about Win64. My guess is that you have an uninstall custom action which assumes that the properties you are using (SERVERNAME, DATABASENAME) ar

[WiX-users] Burn running sql script/ batch /command script in chain.

2012-05-30 Thread Benjamin Bennett
I am trying to use burn as bootstrapper.I have figured out how to install sql server express and the third party msi's as part of the software suite we deliver . I need to be able to run command line scripts between the msi and the install of sql server. I was hoping to use the sql extension in wix

Re: [WiX-users] Burn and LUA Patching

2012-05-30 Thread Hoover, Jacob
That is the question, though I suspect that it would still need to in order to update the bundle's installation information. -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Wednesday, May 30, 2012 6:38 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users]

Re: [WiX-users] WixExitEarlyWithSuccess not working for me

2012-05-30 Thread Luis Tiago C Eterovick
Well, i couldn't make it work the way i wanted. Can anyone help me with this? I want the application to simply end with success as soon as possible with a custom message, if it finds the same or newer version. In my context, this is the best practice, even though it sounds strange. 2012/5/24 Luis

Re: [WiX-users] Perl Script on initialization

2012-05-30 Thread John Cooper
Is perl.exe in your path? You may need an absolute path to it if it isn't. After an install, can you run that perl command line from the INSTALLLOCATION directory? What shows up in the verbose log of the install? -- John Merryweather Cooper Build & Install Engineer - ESA Jack Henry & Associat

Re: [WiX-users] Perl Script on initialization

2012-05-30 Thread Dmuller720
Yes I do, -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Perl-Script-on-initialization-tp7578584p7578603.html Sent from the wix-users mailing list archive at Nabble.com. ---

Re: [WiX-users] Perl Script on initialization

2012-05-30 Thread John Cooper
Do you have an entry in the InstallExecute Sequence? Something like: -- John Merryweather Cooper Build & Install Engineer - ESA Jack Henry & Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message

Re: [WiX-users] Perl Script on initialization

2012-05-30 Thread Dmuller720
I think I have it correct, but it does not seem to be running. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Perl-Script-on-initialization-tp7578584p7578600.html Sent from the wix-users mailing list archive at Nabble.com. ---

Re: [WiX-users] Perl Script on initialization

2012-05-30 Thread Dmuller720
Thanks for the quick response. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Perl-Script-on-initialization-tp7578584p7578599.html Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Burn and LUA Patching

2012-05-30 Thread Bob Arnson
On 29-May-12 14:19, Rob Mensching wrote: > The Burn engine will need to elevate to apply per-machine patches. Would it have to? If MspPackage/@PerMachine="no", would a LUA-compliant per-machine patch Just Work(tm)? -- sig://boB http://joyofsetup.com/ ---

Re: [WiX-users] ExePackage: can my SourceFile be a file that was installed by an earlier step in the chain?

2012-05-30 Thread Bob Arnson
On 29-May-12 18:35, Nate Hekman wrote: > While I think I can get that to work, it would be more convenient and would > end up as a smaller download if I could call the exe that has already been > installed. Is there some way to do that? No, Burn doesn't support that. -- sig://boB http://joyofs

Re: [WiX-users] Issues with Burn (WiX v3.6.2921.0)

2012-05-30 Thread Bob Arnson
On 29-May-12 11:58, Pally Sandher wrote: > Rob M. advised that to do the above with Burn I would have to schedule the > v2.0 MSI for install& Slipstream the 2.2 MSP since Burn assumes a false > InstallConditon means "uninstall" rather than "don't install". Right. You could do this in a custom BA

Re: [WiX-users] Examples of Burn

2012-05-30 Thread Richard Mayes
Go onto the codeplex site and download the source. It's the best example out there. For your comment about doing some of the work inside burn, AFAIK all burn can do is bootstrap other files so what ever you need to do will need to be in a separate application. I'm sure someone will correct me if I