Re: [WiX-users] Patching msi

Thanks! That part I got though. I think you misunderstood my question a bit. The question was on how to generate patch 1.0.2. Should I generate that so that it contains the difference between: 1.0.0 ->1.0.1 or 1.0.0 -> 1.0.2 -- View this message in context: http://windows-installer-xml-wix-t

Re: [WiX-users] How to suppress the StdBA Bootstrapper UI

Ahh!! Thanks for the :) . Later i realized it and now the way is clear for me. :) For UIs, which among the following i have to choose 1. ThemeFiles(.xml) or 2. WPF ? Thanks for the BAFunctions. I tried adding reference to BAFunctions alone to use the Delay() Function, but got error while adding

Re: [WiX-users] Hide ICE91 warning

I didn't see that section and of course it worked! Thank you! Paul -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Tuesday, November 04, 2014 1:48 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hide ICE91 warning Yes. Go to the Prop

Re: [WiX-users] Hide ICE91 warning

For a Screenshot, See: http://stackoverflow.com/questions/7055476/how-do-i-suppress-ice-errors-from-merge-modules Quoting John Cooper : > Yes. Go to the Property settings for your Wix project, go to the > "Tool Settings" tab and in the text box labeled "Suppress specific > ICE validation:

Re: [WiX-users] Is there a WiX 4.0 replacement for candle.exe -trace?

And now you've lived why we removed that switch and several others. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: cknoll [mailto:caleb.kn...@ni.com] Sent: Tuesday, Nove

Re: [WiX-users] Hide ICE91 warning

Yes. Go to the Property settings for your Wix project, go to the "Tool Settings" tab and in the text box labeled "Suppress specific ICE validation: " put ICE91 in the box. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henr

Re: [WiX-users] Is there a WiX 4.0 replacement for candle.exe -trace?

We enabled -trace by default a long while ago, but it looks like no one ever realized that it was just duplicated information. I'll remove this from our build tools. without -trace: > C:\source\driver.wxs(3) : fatal error CNDL0023: Undefined variable: > $(var.Manufacturer). with -trace: > C:\s

[WiX-users] Hide ICE91 warning

Hello, I have a true perUser MSI package. I also know that I can ignore the ICE91 warnings as my MSI works well and uninstalls perfectly even from the registry. With that said, is there a way to suppress only the ICE91 warning so it doesn't take up over 100 warning lines? Thanks! Paul ---

Re: [WiX-users] Is there a WiX 4.0 replacement for candle.exe -trace?

Can you provide any more detail why you chose to turn it on? How it was useful? The prevailing attitude now is that if there is useful data we should not be hiding it behind a switch. _ Short replies here. Complete answers over there:

Re: [WiX-users] Is there a WiX 4.0 replacement for candle.exe -trace?

Yes, we used this switched in our build system since WiX 3.0 to provide additional debugging information. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Is-there-a-WiX-4-0-replacement-for-candle-exe-trace-tp7597729p7597738.html Sent from the wix-u

Re: [WiX-users] How to suppress the StdBA Bootstrapper UI

I agree with Jacob's recommendation that writing a mba to display your UX and hide or don't implement the UX in each msi (or exe prereq like VC) is much prefered. This approach works great and is much better than fighting the intended design of burn. The wix source includes a good example (though

Re: [WiX-users] Is there a WiX 4.0 replacement for candle.exe -trace?

We are removing unnecessary switches and updating the default behavior. Did you use this switch? If so, why? _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: cknoll [mailto:

Re: [WiX-users] Incorrect syntax near 'DATABASE' while Uninstalling from AddRemoveProgram

Is the database name passed in as a property? If this is the case, the property won't be automatically persisted without something like the "remember pattern" which would give you the missing database> http://robmensching.com/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern/ --

Re: [WiX-users] Incorrect syntax near 'DATABASE' while Uninstalling from AddRemoveProgram

Thanks for your suggestion I will try and update you. Thanks Bala Sent from Samsung Mobile. Original message From: John Cooper Date:05/11/2014 1:16 AM (GMT+05:30) To: "General discussion about the WiX toolset." Cc: Subject: Re: [WiX-users] Incorrect syntax near 'DATABASE'

Re: [WiX-users] Incorrect syntax near 'DATABASE' while Uninstalling from AddRemoveProgram

Where does the database name come from? If it was derived from a property at install time then it will not have been preserved unless you preserved it and arranged to retrieve it for the uninstall. Or you can use the WiX "remember property" pattern to preserve property values between install and un

Re: [WiX-users] Is there a WiX 4.0 replacement for candle.exe -trace?

I dug around in the lists and and changes and just couldn't find any mention of why it was removed. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Is-there-a-WiX-4-0-replacement-for-candle-exe-trace-tp7597729p7597732.html Sent from the wix-users m

Re: [WiX-users] Is there a WiX 4.0 replacement for candle.exe -trace?

None planned. Why? _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: cknoll [mailto:caleb.kn...@ni.com] Sent: Tuesday, November 4, 2014 10:55 AM To: wix-users@lists.sourcefor

Re: [WiX-users] Incorrect syntax near 'DATABASE' while Uninstalling from AddRemoveProgram

Hi, There is no syntax error in sql. but the database name not included in the script. that is the reason it throws like incorrect syntax. The actual sql script comes like "Drop database " Thanks Bala Sent from Samsung Mobile. Original message From: Phil Wilson Date:05/11

[WiX-users] Is there a WiX 4.0 replacement for candle.exe -trace?

The -trace command line switch was removed in WiX 4.0 and deprecated in WiX 3.9 . Is there a replacement for this functionality going forward? This added the message to the end of an error: Source trace: at C:\source\driver.wxs: line 54 -- View this messa

Re: [WiX-users] How to suppress the StdBA Bootstrapper UI

Writing your own MBA would be easier than writing a native one. The intent is to collect all the required information from within your BA, and then pass it to the needed packages via a MsiProperty element. Windows Installer UI is quite limited, but a BA can do anything you can do in code. For a

Re: [WiX-users] Incorrect syntax near 'DATABASE' while Uninstalling from AddRemoveProgram

The error is reported as a syntax error according to those messages, so why not investigate that possibility? That your SQL is incorrect? If you really did this: " If manually deleted the Registry entry for add/remove program and delete the installer files after that Installed again and uninstal

Re: [WiX-users] How to suppress the StdBA Bootstrapper UI

Ohh!! Sounds great!!Nice to know about this. So, i will quickly add a custom action which will have a sleep() for some amount of time. @Rob: Thanks for the confirmation. Could you please share the approaches for dealing with the changes have to be done to build a older version .wixproj(created us

Re: [WiX-users] Incorrect syntax near 'DATABASE' while Uninstalling from AddRemoveProgram

Yes, Created the database with the installer while installing. I want to delete the database while uninstalling. Thanks Bala. -Original Message- From: Jeremiahf [mailto:jeremi...@gmail.com] Sent: 04 November 2014 22:15 To: General discussion about the WiX toolset. Subject: Re: [WiX-user

Re: [WiX-users] How to suppress the StdBA Bootstrapper UI

Yes. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: ssmsam [mailto:ssmcs...@gmail.com] Sent: Tuesday, November 4, 2014 9:35 AM To: wix-users@lists.sourceforge.net Subject:

Re: [WiX-users] How to suppress the StdBA Bootstrapper UI

HI, Can we add something that skips the cpu cycles and that adds some delay before the Detect is Completed. So that this gives an impression like the splash stays for some amount of time?(Just a vague idea). Any thoughts? Regards, Sampat. -- View this message in context: http://windows-inst

Re: [WiX-users] How to suppress the StdBA Bootstrapper UI

Hi Hoover, Jacob, Thank you very much for your suggestions. We have 5 components of our product. 2 are the main components and 3 are the client tools for interaction. The 2 main comps should take 2 users-details as input (domain, usrname n pwd) (which ll later ,during installation, be qualified fo

Re: [WiX-users] Incorrect syntax near 'DATABASE' while Uninstalling from AddRemoveProgram

Are you creating the database with the installer? On Tue, Nov 4, 2014 at 7:21 AM, Bala wrote: > HI All, > > > > The exact error in log file > > > > Error 26202. Error -2147217900: failed to drop SQL database: , error > detail: > Incorrect syntax near 'DATABASE'.. > > > > If manually deleted the

Re: [WiX-users] Force a MajorUpgrade to do complete uninstall BEFORE new install

This is all good information, but I want to get back to the original question at hand for future onlookers seeking a solution (or understanding of their problem). The logical containers are as follows: A bundle consisting of several .msi packages. Each package has upgrade rules that in this case

Re: [WiX-users] How to suppress the StdBA Bootstrapper UI

Or write your own, Burn is designed to allow you to build your own UI. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sen

[WiX-users] Display optional text in Exit Dialog upon ininstall

I understand that the built-in Exit Dialog will display after the installer completes successfully (whether it is an install/modify/repair or remove). I want to be able to customize the message displayed in the Exit Dialog for uninstallation. I figured I could use the built-in textbox (WIXUI_EXITDI

Re: [WiX-users] Force a MajorUpgrade to do complete uninstall BEFORE new install

Unlikely as it seems, if there is a WiX bug then open your MSI file with Orca and look at the InstallExecuteSequence and see where RemoveExistingProducts is sequenced relative to InstallValidate or InstallInitialize. As John says, you may not have correctly specified enough to make it an actual ma

Re: [WiX-users] Advertised shortcuts and the new world of bundles

Advertised shortcuts don't cause repair to be unavailable, just the part that is associated with advertised shortcuts repairing the containing feature if a component is missing. In that sense it's not a product repair, just a feature repair. There's always manual repair if something does get remove

Re: [WiX-users] How To Detect Visual C++ 2012 X64 RunTime In Wix Bootstrapper Project

http://blogs.msdn.com/b/astebner/archive/2010/05/05/10008146.aspx Scroll down and read through the comments for the 2012/x64 product codes, not certain if there is a reg check you can do that is update "safe". -Original Message- From: Hippias Lesser [mailto:lesser.hipp...@gmail.com] Sen

Re: [WiX-users] How to suppress the StdBA Bootstrapper UI

1) Not what it was designed to do. Instead of trying to fight burn, why not try to embrace it. Create a single unified user experience in the BA, and then property drive your MSI's silently. 2) I believe the splash is hidden after detect completes. Instead of trying to embed valuable informati

Re: [WiX-users] Force a MajorUpgrade to do complete uninstall BEFORE new install

I've been using Burn since it came out in Wix 3.6 with 20 product installers. MajorUpgrade has been an important requirement for all of them. I have had no major upgrade issues with any of these installers. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications

Re: [WiX-users] Force a MajorUpgrade to do complete uninstall BEFORE new install

It seems to me like the roll of burn and msiexec as it is related to the MajorUpgrade element is confused in this and related threads. AFAIK candle compiles the MajorUpgrade element and the MajorUpgrade/@Schedule into the msi package which is parsed by msiexec at installed time without any involve

Re: [WiX-users] Force a MajorUpgrade to do complete uninstall BEFORE new install

Burn does not control the scheduling of a major upgrade. The element (if used) or manual scheduling of RemoveExistingProducts does. Phil is entirely correct. Note that the versioning rules for the target and upgrade MSI's must be followed for major upgrade to work. -- John Merryweather Coope

Re: [WiX-users] Force a MajorUpgrade to do complete uninstall BEFORE new install

I have posted the same question a few days ago and I have received the same answer, I think it's a bug of WiX Burn.I this way I can't execute upgrade of the Burn package as it creates many problems to my application that will not work fine.I need even to add a custom action to clear some folders

Re: [WiX-users] Incorrect syntax near 'DATABASE' while Uninstalling from AddRemoveProgram

HI All, The exact error in log file Error 26202. Error -2147217900: failed to drop SQL database: , error detail: Incorrect syntax near 'DATABASE'.. If manually deleted the Registry entry for add/remove program and delete the installer files after that Installed again and uninstalled it

[WiX-users] Incorrect syntax near 'DATABASE' while Uninstalling from AddRemoveProgram

HI, While uninstalling a WIX installation from Add/Remove program it throws error like "Error 26202. Error -2147217900: failed to drop SQL database: , error detail: Incorrect syntax near 'DATABASE'. Analyzed further through SQL profiles and found that the DATABASE name comes as empty. Plea

[WiX-users] How To Detect Visual C++ 2012 X64 RunTime In Wix Bootstrapper Project

want to detect If Visual C++ 2012 X64 RunTime is installed or not. There is samples and Registery keys sample for Visual C++ 2010 But I can not figure out for C++ 2012 X64 RunTime registery search key . So How To Detect Visual C++ 2012 X64 RunTime In Wix Bootstrapper Project? ---

[WiX-users] Patching msi

Hi I have a MyProduct_1.0.0.msi that I'm going to release and I am planning for the patchwork that will come. When doing patch 1.0.1 I'll create a patch comparing the two versions. So far so good... But the patch 1.0.2. Should that be made comparing againts 1.0.0 or 1.0.1? Thanks? -- View thi