Re: [WiX-users] Managed Bootstrapper: Engine.EvaluateCondition() requires separate thread?

for all conditions in our Bundle.wxs code, evaluate them and display the related message in our Custom Bootstrapper UI. Farrukhw wrote Hi, In my Managed Bootstrapper, I tried to call Engine.EvaluateCondition(MY_PROG_FOUND); in Run() method. But it never evaluates and said something like

Re: [WiX-users] How to get the WixBundleLog value of LogPathVariable attribute ?

Using Engine.StringVariables[WixBundleVariable] e.g. in your case: Engine.StringVariables[WixBundleLog]; -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-get-the-WixBundleLog-value-of-LogPathVariable-attribute-tp7598738p7600833.html Sent

[WiX-users] Managed Bootstrapper: Engine.EvaluateCondition() requires separate thread?

Hi, In my Managed Bootstrapper, I tried to call Engine.EvaluateCondition(MY_PROG_FOUND); in Run() method. But it never evaluates and said something like: This requires a running thread. and it never evaluates. I'm trying to evaluate Bundle conditions in my managed bootstrapper but still no luck.

[WiX-users] How to set Burn.exe FileVersion and ProductVersion differently?

Hi Our finally generated Burn.exe file got same versions for FileVersion and ProductVersion. However, version scheme followed in our team suggests ProductVersion as 2015.0. As FileVersion is coming from Version attribute of Bundle element, Is there any way to set ProductVersion property of

Re: [WiX-users] How to set Burn.exe FileVersion and ProductVersion differently?

ahh. So it might be me who has to write a utility to modify PE...  On Feb 13, 2015 9:45 PM, Rob Mensching-7 [via Windows Installer XML (WiX) toolset] ml-node+s687559n7599207...@n2.nabble.com wrote: Not today. -- View this message in context:

Re: [WiX-users] How to set Burn.exe FileVersion and ProductVersion differently?

ahh. So it might be me who has to write a utility to modify PE... -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-set-Burn-exe-FileVersion-and-ProductVersion-differently-tp7599204p7599225.html Sent from the wix-users mailing list archive

[WiX-users] Managed Bootstrapper initializing progress indicator ...

Hi fellows, Our Bootstrapper consuming Burn is of 70MB, containing Net Framework 4, VC Runtimes and two more pre-requisites + Product.msi itself. Whenever we execute it from a network location, it took much longer time to execute (last time it was almost 40 seconds . We suspect that such delay is

Re: [WiX-users] Managed Bootstrapper initializing progress indicator ...

there: http://www.firegiant.com/ -Original Message- From: Farrukhw [mailto:[hidden email] http://user/SendEmail.jtp?type=nodenode=7598089i=0] Sent: Wednesday, November 19, 2014 4:12 AM To: [hidden email] http://user/SendEmail.jtp?type=nodenode=7598089i=1 Subject: [WiX-users] Managed

[WiX-users] wixstdba: Using Win-Forms or MFC based UI instead of Theme UI (xml based)

Hi While reading source code for WiX Extended Bootstrapper Application, I'm wondering if I want to replace this Theme manipulation (xml based) with Win-Forms or MFC based UI, do I have to modify/rewrite all that or I can simply use references of some library, just as in case of Managed

Re: [WiX-users] Fwd: Updating a msi installed by bootstrapper .

As mentioned by Jeremiahf, you need to managed your Upgrade scenarios using Upgrade element in your Wix for your msi. In your case, you may need to do a major upgrade. Also, please check if you are not changing Product GUID in your next upgraded wix. -- View this message in context:

[WiX-users] Guidelines/Tutorial for Bootstrapper in native (C++)

Hi, There are some good guidelines available for developing Bootstrapper in managed code. And I've developed one and working very much fine. I'm wondering is someone could guide me towards developing a Bootstrapper in native code (C++), i.e. a jump start... Is there any precise guide/tutorial

Re: [WiX-users] Guidelines/Tutorial for Bootstrapper in native (C++)

Actually, that's what I'm looking too... :) but looking for some tutorial/guide with good explanation, always give a boost and speed... On Mon, Nov 3, 2014 at 8:21 PM, Phill Hogland [via Windows Installer XML (WiX) toolset] ml-node+s687559n7597677...@n2.nabble.com wrote: -- View this

[WiX-users] Repost: Wix Burn and KeyPath file hot repair/restore by Windows Installer.

Hi, Reposting with a hope that someone may be able to give some guidance, as last time it was left abandoned: I've developed a Managed Bootstrapper and now near to release the product. Normally, if a KeyPath file is removed/modified, Windows Installer would try to restore/repair that. But in

Re: [WiX-users] TFS: Wix can't see its source files if using TfvcTemplate.12.xaml.

So, finally I was able to solve this after a whole day struggle. Like Digg a mountain and got a mice :). Actually TfvcTemplate.12.xaml seems to be executing MsBuild with parallel processing enabled (/m), while in my VS Solution, Wix project was added independently i.e. in Build Order it was the

Re: [WiX-users] TFS: Wix can't see its source files if using TfvcTemplate.12.xaml.

Jup.. And as usual, a developer like me found that by hit and trial researching.. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/TFS-Wix-can-t-see-its-source-files-if-using-TfvcTemplate-12-xaml-tp7597267p7597326.html Sent from the wix-users

[WiX-users] TFS: Wix can't see its source files if using TfvcTemplate.12.xaml.

I need to use TfvcTemplate.12.xaml because of its Pre and Post build script execution support and I need to run a Powershell script as PreBuild event. On TFS 2013, Building a Wix project using old DefaultTemplate.xaml works fine. While trying to build using new default template

Re: [WiX-users] TFS: Wix can't see its source files if using TfvcTemplate.12.xaml.

Well, I got it with 2013 actually and I'm trying to run a script for versioning, just according to this msdn article http://msdn.microsoft.com/en-us/library/dn376353.aspx and it is working just as guided and expected. But Wix's behavior is not as expected. However, I do have a Wix project on

Re: [WiX-users] TFS: Wix can't see its source files if using TfvcTemplate.12.xaml.

I've set to Unrestricted for the sake for making things run. But it is even failing when no script is specified, i.e. simply building Solution just as we were doing in older DefaultTemplate... -- View this message in context:

Re: [WiX-users] TFS: Wix can't see its source files if using TfvcTemplate.12.xaml.

I've posted the code and log as well. I tested this with a small C# application with no dependency to build or import/copy/install i.e. just a simple application. And tested with TfvcTemplate as well as old DefaultTemplate, and facing same issue i.e. building on older DefaultTemplate while only

Re: [WiX-users] HeatDirectory failure on TFS

Just updated my query on StackOverflow http://stackoverflow.com/questions/26018253/heatdirectory-failure-on-tfs-with-msbuild-error-msb4166-child-node-3-exited-p/26032349#26032349 -- View this message in context:

[WiX-users] HeatDirectory failure on TFS

Hi experts, I'm using HeatDirectory task in my *.wixproj file, which is working very fine on my machine, being built locally. However, on TFS, it is failing with following error: C:\Program Files (x86)\WiX Toolset v3.8\bin\Heat.exe dir D:\Builds\32\48\bin\Debug\InstallSrc\WebApp\ -cg

Re: [WiX-users] HeatDirectory failure on TFS

Hi John, Thanks for reply. Presently, MSBuild PlatForm is Auto. However, I'm just wondering how the command line generated in MsBuild log working on command line? In addition, same MsBuild project is working just fine if we build it in Visual Studio or using MsBuild command line. -- View

Re: [WiX-users] HeatDirectory failure on TFS

I will try that in morning.. but we are also building 64 bit projects in our solution. Would these be affected? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/HeatDirectory-failure-on-TFS-tp7596956p7596974.html Sent from the wix-users mailing

Re: [WiX-users] HeatDirectory failure on TFS

Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |[hidden email] http://user/SendEmail.jtp?type=nodenode=7596975i=0 -Original Message- From: Farrukhw [mailto:[hidden email] http://user/SendEmail.jtp?type=nodenode=7596975i=1] Sent: Wednesday, September 24, 2014 1:38 PM

[WiX-users] HarvestDirectory target for multiple directories

I'm trying to harvest different folders in my *.wixproj file. But HeatDirectory task is only harvesting last HarvestDirectory target. What I'm missing here? Here is my code segment: ItemGroup Compile Include=Components.wxs LinkComponents.wxs/Link /Compile

Re: [WiX-users] Using '*' in Component Guids and Patches

That's not a differential patch. Its a minor upgrade using the msi... -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Patches-and-using-instead-of-Component-Guids-tp7594909p7594962.html Sent from the wix-users mailing list archive at

Re: [WiX-users] Using '*' in Component Guids and Patches

... ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Farrukhw [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=7594938i=1] Sent: Sunday, May 25, 2014 10:13 PM

[WiX-users] Using '*' in Component Guids and Patches

Hi While searching for best practices, I came across this thread http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Best-Practices-Using-quot-quot-for-GUID-automation-td5234716.html , which is discussing the use of '*' instead of GUIDs in components. As far I know, while generating

Re: [WiX-users] Managed bootstrapper on a PC without .NET framework 4.0

Sky, I faced same problem. At the end, we discovered that on Win 7 with no SP, we are getting this error. When we installed Net Framework 4 (dotNetFx40_Full_x86_x64.exe) on same windows, it started working fine. So finally we got to know that on Windows 7 + Service Pack 1, it may work fine.

Re: [WiX-users] Managed bootstrapper on a PC without .NET framework 4.0

Ok, just solved this. On Windows 7 without SP1, there is Net FW 3.5. In my BootstrapperCore.Config file, it was: startup useLegacyV2RuntimeActivationPolicy=true supportedRuntime version=v4.0 / supportedFramework version=v4\Client / *supportedRuntime version=v2.0.50727 /*

[WiX-users] Wix Bootstrapper maximum number of packages and file size limit

Sorry, if this is a re-post. We have lots of third party components (msi, exe installer) to be delivered on user's machine. Although, there is a main script, used to install these in a required sequence on user's machine, but for delivery purposes, we are creating one self extracting archive

[WiX-users] Is this a Bug in Wix Bootstrapper command line?

I already posted a related problem here: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-BA-command-line-not-effective-td7592884.html and http://stackoverflow.com/questions/21989084/wix-managed-ba-command-line-not-effective, which is about command line passed during upgrade.

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

Any good response? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Managed-Boostrapper-upgrade-but-Installs-side-by-side-with-older-version-tp7592745p7592881.html Sent from the wix-users mailing list archive at Nabble.com.

[WiX-users] WixBA shows No .Net Framework installed

Experimentally, I simply copied WixBA project from Wix 3.7 source. Replaced the reference from core.csproj to BootstrapperCore and tried to use it with my own Bundle which is working fine with my own Manged Bootstrapper. It built fine. But strangely, when I tried to run it, it showed me the dialog

[WiX-users] Managed BA command line not effective

While playing with TestBA Bootstrapper from Bryan http://bryanpjohnston.com/2012/09/28/custom-wix-managed-bootstrapper-application/ , first I installed 1.0.0.0. Then I incremented version to 1.0.0.1 and logged the process. Here is the part where -uninstall -quite command line was passed during

[WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

I'm struggling with my Custom Boostrapper Upgrade issue. By following this stackoverflow thread http://stackoverflow.com/questions/17676657/wix-burn-bootstrapper-majorupgrade , I'm using LaunchAction.Install. This does Upgrade the Product as well as Boostrapper, but older Bootstrapper remains

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

Hi Rob :) I should have attached the log file before.. Adding the log file from version 1.0.1.0 while updating 1.0.0.0. MyProdSoftwareInstaller.log http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7592760/MyProdSoftwareInstaller.log Btw, to me, this doesn't show any

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

Yes, that may be because before Apply Complete, it is not finished and -uninstall is failing. from last lines: 26D4:2C38][2014-02-19T08:42:31]i301: Applying execute package: {c0489d1d-654e-4caa-9f95-0fe034d74cc6}, action: Uninstall, path: C:\Users\Farrukh\AppData\Local\Package

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

Sean, There was Environment.Exist(this.FinalResult) in ApplyComplete(). Now replaced with: this.FinalResult = e.Status; //Storing the final status code. bootstrapperApplication.Engine.Quit(e.Status); Please find latest log attached with this reply. However, I've figured out that

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

So when if found (Engine.Detect) that 1.0.0.0 is there, the Command got Uninstall automatically. But we are invoking our UI dialogs here like: if(MyViewModel.PState==PackageState.Absent) Application.Run(BootStrapDlgs.Welcome_Dlg); //Let's start with Welcome Dlg else

[WiX-users] Custom Managed Boostrapper and Maintenance dialog

Hi everyone, Presently, I'm working with a Managed Bootstrapper with its own UI written in WinForms (.Net 2.0 based). It is able to install my msi using DisplayInternalUI=yes and no very well. BootstrapperApplicationRef Id=ManagedBootstrapperApplicationHost Payload

Re: [WiX-users] Custom Managed Boostrapper and Maintenance dialog

So I have to add my own Form for that... ... -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Custom-Managed-Boostrapper-and-Maintenance-dialog-tp7592225p7592228.html Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] customizing burn prerequisite boostrapper image in theme

Thanks a lot for the useful reply and solution. I was in search of this... Be happy forever.. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/customizing-burn-prerequisite-boostrapper-image-in-theme-tp7205852p7592105.html Sent from the wix-users

[WiX-users] Burn: Launch using -passive option as default

I'm using Wix 3.8 Burn and looking for an event like OnExecuteApp. We can launch bootstrapper.exe using -passive option so that it would auto start its installation process. (Note: Type BootStrapper.exe /? to see other options.) *Question:* How can we set bootstrapper.exe to launch with -passive

Re: [WiX-users] Burn: Launch using -passive option as default

Yes, using following, it is wixstdba: BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense Is there any other method like proving Bootstrapper.exe.config or Bootstrapper.ini kind of thing in which we can specify its parameters, so that whenever user invoke it, it

[WiX-users] WIX Patches: Windows restores patched files and can't uninstall patch

Hi Experts, br/ I'm generating a patch using following code: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; PatchCreation Id=$(var.PatchGUID) CleanWorkingFolder=yes OutputPath=PDW_x64_Patch.pcp

[WiX-users] Patching Components with different GUIDs?

Hi Guys, Is that possible to Patch a Component whose GUID was changed in Updated build? Pyro gives an error: I know if I change the GUID in my updated msi back to the one which was in Original msi. But I have a case in which a great number of GUIDs (might be in thousands) have to be updated

Re: [WiX-users] Patching Components with different GUIDs?

Hi Peter, Thanks for your reply.. I've given msi builds which were not designed by me and after Pyro's complaint, I investigated that in every build, same named components got new Component ID (GUID). Although, I've informed the owners and asked them if they are changing the Component IDs for

[WiX-users] Patch can't update installed product and shows Change/Repair dialog..

Hi Guys, I'm building a patch using PCP, according to this tutorial: http://wix.sourceforge.net/manual-wix3/patch_building.htm http://wix.sourceforge.net/manual-wix3/patch_building.htm I'v two MSI (extracted as Admin installs) 1. 8.11.9.225 (This is my target to update) 2. 8.11.9.353 (The

Re: [WiX-users] Patch to update version of installed product?

Thanks all for your replies. I've just posted my resultant patch script here: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-can-t-update-installed-product-and-shows-Change-Repair-dialog-td7579479.html but with some issues and I need help in these. Thanks -- View this

Re: [WiX-users] Patch to update version of installed product?

Hi Moc Thanks for the tips. No, I only changed ProductCode with a new GUID and updated in all other tables e.g. Registry, INIFile etc. -- View this message in context:

Re: [WiX-users] Patch to update version of installed product?

In the WIX of Product, we do not use PackageCode, as far I remember. It was deprecated -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-to-update-version-of-installed-product-tp7579458p7579483.html Sent from the wix-users mailing list archive

[WiX-users] Patch to update version of installed product?

Hi I need to make a patch for an already installed product, to just update its version information i.e. 9.4.5.10 to 9.4.5.11. I read different articles/posts, but not getting any proper way to do this. Any help would be really appreciated. Thanks a bunch Farrukh -- View this message in

Re: [WiX-users] Patch to update version of installed product?

Hi Peter, Thanks for such a quick response... It does make sense to me. But what do you mean by wholly wix patching?? I'm quite a newbie to patches actually. -- View this message in context:

Re: [WiX-users] Patch to update version of installed product?

Thanks again... I was reading this article about patch restrictions: http://wix.sourceforge.net/manual-wix3/patch_restrictions.htm and it mentions following: Small updates: do not change the ProductVersion property of a target product and typically represent a small subset of files to be updated.

Re: [WiX-users] Patch to update version of installed product?

Thanks Neil, But that's a full product upgrade. My task is to generate a patch which would update the Version info of installed product. I just tried this: ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Patch AllowRemoval=yes

Re: [WiX-users] Patch to update version of installed product?

Thanks anyway Neil for giving time -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-to-update-version-of-installed-product-tp7579458p7579470.html Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Trouble with ScheduleReboot

Make sure if NEEDSREBOOT=1 getting true. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Trouble-with-ScheduleReboot-tp689116p7385293.html Sent from the wix-users mailing list archive at Nabble.com.

[WiX-users] Wix: Installing a Component while Repair Or Reinstall

*Problem:* I have a User Requirement in which a file would not be installed if a Prerequisite application is absent on users machine. But after installing my product, when user would install that Prerequisite application, he would run my installer and choose repair to install that missing file and

Re: [WiX-users] Wix: Installing a Component while Repair Or Reinstall

Hi jhennessey Thanks for the reply. Yes, there is a condition on the component which is defined by a vbscript custom action scheduled in Execute Sequence after CostFinalize, so that is running during reinstall. *But what if the component is not installed at first installation? Would

Re: [WiX-users] Wix: Installing a Component while Repair Or Reinstall

Thanks a bunch I will definitely give it a try. Best regards -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Installing-a-Component-while-Repair-Or-Reinstall-tp7269151p7270180.html Sent from the wix-users mailing list archive at Nabble.com.

[WiX-users] Wix: How to set a Feature State “ This Feature Will Not be available”?

Hi experts, I've assigned a task in which one sub feature among 4 should be displayed to the user in the state as This Feature Will Not be available For instance, I have this feature set: Feature Id=Main AllowAdvertise=no ConfigurableDirectory=MYROOT Description=Required components