Re: [WiX-users] Download newer version of cached MSI if available

Yes. Burn is cool like that. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: Thursday, September 25, 2014 5:06 PM To:

Re: [WiX-users] Download newer version of cached MSI if available

This is great! I looked at the source code for the WiX installer itself, which is making use of the Bundle Update element, and actually does exactly what I would want to do in my case: Check a feed to see if a newer version has been posted, and then continue accordingly. After checking the feed it

[WiX-users] IIS Extension: assigning an existing cert to new website

Is it possible for the wix iis extension to configure a new website to use SSL using a certificate that is already installed on the system? Most of samples I've been able to locate assume I am installing the certificate that I will configure to be used for the newly created website.

Re: [WiX-users] How to Internalize the Installation process.

Use the Binary element. The wix source download has the source for several wixExtensions, and studing the structure and appraoch taken to create those extensions was helpful as I moved my IS projects to WiX. Also there is the WiX contrib project (https://wixcontrib.codeplex.com/) which was helpfu

[WiX-users] How to Internalize the Installation process.

Hi, Currently, We are planning to migrate from IS to WiX. In our product we are using some files which are needed only during installation process(SupportFiles in IS). For eg: we are calling some methods in a dll, say, ProductDLL.dll(and many more editable sensitive files) in the sequence Custo

Re: [WiX-users] Any way to get a bundle to use updated MSI packages without having to rebuild the bundle?

Regarding the general issue of long build cycles, I found that I could decrease the build time by making sure that each MSI project will incrementally build. The use of wixlibs for code common to MSI packages and common to bundles also helped the build process. I make sure that the bundle is buil

Re: [WiX-users] Download newer version of cached MSI if available

Documentation is lagging. // OnDetectUpdateBegin - called when the engine begins detection for bundle update. // // Return: // IDOK instructs the engine to attempt update detection. // // IDCANCEL instructs the engine to stop detection. // // IDNOACTION instruc

Re: [WiX-users] Download newer version of cached MSI if available

Okay, what (built-in) functionality is there for updating the bundle? The only thing I could find was this, but it's more about being able to do an update check from ARP and not while executing the bundle: http://wixtoolset.org/issues/4190/ // Sascha On Wed, Sep 24, 2014 at 8:51 PM, Rob Menschi

Re: [WiX-users] Generating a log file from BootStrapper exe

Hi Rob, Apologies for not noticing the "Burn Log File" section below, at the end. Craziest thing is, I had gone through that link thrice, still didn't notice. :( Thanks for your quick reply Phil, Hogland :) Regards, Sampat -- View this message in context: http://windows-installer-xml-wix-t

Re: [WiX-users] Any way to get a bundle to use updated MSI packages without having to rebuild the bundle?

No. Why? Security. Srlsy. Note: Technically speaking may be able to use signature validation but only very narrowly and signature validation has other real world issues, don't recommend it. _ Short replies here. Complete answe

Re: [WiX-users] Generating a log file from BootStrapper exe

Hi , Thanks a lot for letting me about this, yes it does create with underscore("_") in between words with appending the date-time. Oh my god, i do not know why did not i notice this. :( I have one more question here, Which directory is safe to extract support Files so the no attack can happen.

[WiX-users] Any way to get a bundle to use updated MSI packages without having to rebuild the bundle?

Hi all, The project I am working on is using a custom bootstrapper for our install process. Inside our bundle chain are multiple MsiPackages that are all located on a network, so I'm using DownloadUrl to locate each one of them. Our build process is a bit lengthy (the bundle has to be built a

Re: [WiX-users] Uninstall previous version

By ProductCode, do you mean Product Id? I tried , but it seems like the installer will just install/overwrite and not remove the old application. By PackageCode, do you mean http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Uninstall-previous-version-tp7596982p7596999.html Sent from t

Re: [WiX-users] KeyPath by default?

I don't quite follow. 1. The KeyPath will be set however the non-WiX-based MSI creation tool sets it. That's very much dependent on how the tool works. 2. If someone rewrites their installation package in WiX after using some other tool then they will need to understand how the WiX toolset work

Re: [WiX-users] Generating a log file from BootStrapper exe

If you are using a Burn based bootstraper, it generates log files in the users temp folder (%temp%) using the msi package name, which I believe you could override in an mba, but I have not had the need to do that. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.

Re: [WiX-users] Generating a log file from BootStrapper exe

Burn based bundles automatically create log files. Some details in the "Burn log file" section here: https://support.firegiant.com/entries/24024218-Create-a-log-file- _ Short replies here. Complete answers over there: http://www.firegi

Re: [WiX-users] Patch question (been a while since I did patches, and haven't used WIX for Patches) [P]

Classification: Public Phew glad to know I did it right ☺ Thanks I will take a look at that! Cheers, Steve [Latest TITUS News!] This message has been marked as Public by Steven Ogilvie on September-25-14 1:37:25 PM. The above cla

[WiX-users] Please add me to this group

Hi, I am really interested to learn Wix Installer to author our product installer. We are planning to move from InstallShield to WiX, Regards Sampat -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achiev

Re: [WiX-users] KeyPath by default?

In other words, 1) someone builds an MSI with a non-WiX tool with a component with no KeyPath that uses the MSI default of the containing directory and then 2) builds an upgrade/patch/whatever MSI that similarly contains no KeyPath definition and WiX chooses something else as the KeyPath and 3) the

Re: [WiX-users] Patch question (been a while since I did patches, and haven't used WIX for Patches)

Yes, although I have a project file to automate that, if you'd like. See: http://borgsdemons.com/blog/2014/07/11/yet-more-improve-wix-way-patch-project-with-burn-bootstrapper/ -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack

[WiX-users] Generating a log file from BootStrapper exe

Hi, I have read two ways of generating log files for the wix instller(in general msi's). 1) *enabling registry key* - with this method i /will not get the log file name as our product/ name.(default naming eg: MSIx.log) 2)*using cmd line msiexec.exe tool* --- "msiexec /i MyApplication.msi

[WiX-users] Using external cab for multiple language msi packages.

Using a Burn driven MSIs, without using language transforms, results in MSI packages, of the same name, in a culture named folder tree. I have also been evaluating using external cabs for the common files. From what I have reviewed the cab gets created in the MSI output folder (or subfolder below

[WiX-users] Patch question (been a while since I did patches, and haven't used WIX for Patches)

Here is what I did: created: patch\rtm which holds the admin install of the RTM version of our software (WIX 3.5 MSI 3.0) patch\upp which holds the latest hotfix admin install of our software (WIX 3.5, MSI 3.0) patch\tempholds icons/binaries that are internal to MSI rtm

Re: [WiX-users] KeyPath by default?

Actually, yes. WiX documentation trumps here: http://wixtoolset.org/documentation/manual/v3/xsd/wix/component.html KeyPath YesNoType If this attribute's value is set to 'yes', then the Directory of this Component is used as the KeyPath. To set a Registry value or File as the KeyPath of a com

Re: [WiX-users] KeyPath by default?

The chm for the Component element implies that you are correct, but warns against doing that, as I understand it. "If KeyPath is not set to 'yes' for the Component or for a child Registry value or File, WiX will look at the child elements under the Component in sequential order and try to automati

Re: [WiX-users] Uninstall previous version

Nobody can know if your upgrade will work because it depends on the changes made to a set of properties between old and new MSI files. The UpgradeCode must be the same, ProductCode must have changed, PackageCode too (but WiX does that by default I think) and the ProductVersion must be incremented

Re: [WiX-users] KeyPath by default?

No, according to the docs for KeyPath in the Component table. It uses the folder of the Directory as the KeyPath. http://msdn.microsoft.com/en-us/library/aa368007(v=vs.85).aspx --- Phil Wilson On Thu, Sep 25, 2014 at 8:06 AM, Nicolás Alvarez wrote: > If I write this: > > > > > I

Re: [WiX-users] Uninstall previous version

I have the following: Is that enough and should that be modified? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Uninstall-previous-version-tp7596982p7596985.html Sent from the wix-users mailing lis

[WiX-users] KeyPath by default?

If I write this: Is the File automatically marked as a KeyPath because of being the only file in the component? -- Nicolás -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compli

Re: [WiX-users] Uninstall previous version

2014-09-25 11:49 GMT-03:00 newuser2014 : > Hi, > I have the Product id as follows: > > And I have added the following: > > > > This seems to just overwrite the previous version and not uninstall it. > After installation of the newer version, I went into Add/Remove Programs > and saw that

[WiX-users] Uninstall previous version

Hi, I have the Product id as follows: This seems to just overwrite the previous version and not uninstall it. After installation of the newer version, I went into Add/Remove Programs and saw that the previous version of the application still listed. Any idea on what is wrong or how to do

Re: [WiX-users] HeatDirectory failure on TFS

Just updated my query on StackOverflow -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/HeatDirectory-