[WiX-users] WiX burn: how to change 'WixBundleName' in bootstrapper application?

In my bundle element I have an attribute Name, I would like to edit this during an install after a user has selected which application they would like to install. How can I accomplish this task? I tried the following below, but no luck. Bundle Name=!(loc.WixBundleName)) Version=1.0.0.0

Re: [WiX-users] WiX burn: how to change 'WixBundleName' in bootstrapper application?

Bumdle != Bundle ? On Thu, Aug 14, 2014 at 2:32 PM, linos lino...@hotmail.com wrote: In my bundle element I have an attribute Name, I would like to edit this during an install after a user has selected which application they would like to install. How can I accomplish this task? I tried

Re: [WiX-users] WiX burn: how to change 'WixBundleName' in bootstrapper application?

neslekkim That was it! Thank You. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-burn-how-to-change-WixBundleName-in-bootstrapper-application-tp7596357p7596359.html Sent from the wix-users mailing list archive at Nabble.com.

[WiX-users] [SPAM] Re: PayloadGroupRef to import fragments - Bundle fails

While reading through the engine.cpp (and related) code, I modified my implementation to provide a text file in the payload group, so that there was nothing ambiguous (as there may have been by using the empty PayloadGroup). (I also discovered the usefulness of reviewing the bundle-manifest.xml

Re: [WiX-users] [SPAM] Re: PayloadGroupRef to import fragments - Bundle fails

I filed a bug with the same root cause last week: http://wixtoolset.org/issues/4491/. I guess we'll see in the wix-devs meeting today whether they take my fix into v3.9. On Thu, Aug 14, 2014 at 8:23 AM, Phill Hogland phogl...@rimage.com wrote: While reading through the engine.cpp (and

Re: [WiX-users] [SPAM] Re: [SPAM] Re: Build order problems Votive vs MSBuild

Cool! Sounds a lot like this: http://robmensching.com/blog/posts/2008/10/10/what-are-.wixlibs-and-why-would-you-use-them/ ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original

[WiX-users] [Light] light.exe error LGHT0001: Cannot create a file when that file already exists.

We are randomly get having out WiX builds fail with the following: [Light] light.exe error LGHT0001: Cannot create a file when that file already exists. The log does not indicate what file it is complaining about and I have not seen any other reports of this error in the groups. Has anyone seen

[WiX-users] [SPAM] Re: [SPAM] Re: PayloadGroupRef to import fragments - Bundle fails

Interesting. Thanks for all your efforts! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/PayloadGroupRef-to-import-fragments-Bundle-fails-tp7596356p7596364.html Sent from the wix-users mailing list archive at Nabble.com.

[WiX-users] [SPAM] Re: [Light] light.exe error LGHT0001: Cannot create a file when that file already exists.

I get this error when the output file (bundle.exe, msipackage.msi, or library.wixlib, depending on the type of project) is open in another process, like Orca. So for me it is not random. Is your build process trying to do something with the prior version of the output file, as the project is

Re: [WiX-users] [Light] light.exe error LGHT0001: Cannot create a file when that file already exists.

Thanks Phill, I do not think someone would have been on the TeamCity build machine opening up files at the times of the failures, so that should rule out that case. We have a build step that will generate a new Product Code for the product and replace the one in the WiX projects, but that

Re: [WiX-users] [Light] light.exe error LGHT0001: Cannot create a file when that file already exists.

IIRC, 0001 errors are internal errors and provide a stack trace to help track down where better error message should be added. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original

[WiX-users] V C++ 2013 redist detection

Hello everyone, Has anyone had experience in detecting for V C++ 2013 dependency in their installer? It's doesn't appear to be as easy as it used to be... Thank you in Advance, J -- They may forget what you said but they will never forget how you made them feel. -- Anonymous

[WiX-users] [SPAM] Re: V C++ 2013 redist detection

I have been using: util:ProductSearch ProductCode={13A4EE12-23EA-3371-91EE-EFB36DDFFF3E} Variable=vc2013_x86_SP1 Result=state / Install when the variable is less than 5. -- View this message in context:

[WiX-users] [SPAM] Re: V C++ 2013 redist detection

I have been using: util:ProductSearch ProductCode={13A4EE12-23EA-3371-91EE-EFB36DDFFF3E} Variable=vc2013_x86_SP1 Result=state / or util:ProductSearch ProductCode={13A4EE12-23EA-3371-91EE-EFB36DDFFF3E} Variable=vc2013_x64_SP1 Result=state Condition=VersionNT64 / when it is detected as installed

Re: [WiX-users] FileSharePermission - Change?

A very old post, but in case anyone was wondering, to get the Change permission on a file share, use the following properties on FileSharePermission: GenericWrite=yes Traverse=yes Delete=yes GenericRead=yes -- View this message in context:

Re: [WiX-users] [SPAM] Re: V C++ 2013 redist detection

On 14-Aug-14 17:59, Phill Hogland wrote: util:ProductSearch ProductCode={13A4EE12-23EA-3371-91EE-EFB36DDFFF3E} Variable=vc2013_x86_SP1 Result=state / I recommend against using a product code search: If a user has a later version of the runtime installed, it won't be detected. (The VC runtimes