Hey,
The info is available in BootstrapperApplicationData.xml. I don't know if
there's an easier way, but if all else fails :)
//Caisa
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Getting-at-the-DisplayName-of-a-package-in-a-custom-bootstr
/[170C:1710][2012-09-10T13:43:58]: Detected related
package:{02BA91DA-3C08-45ED-854E-343B5BBDCE40}, scope: PerMachine, version:
2.1.0.0, language: 0 operation: MajorUpgrade
[170C:1710][2012-09-10T13:43:58]: Detected related
package:{02BA91DA-3C08-45ED-854E-343B5BBDCE40}, scope: PerMachine, version:
I'm bumping this thread since I really need help with this problem.
In a nutshell, the question is this:
*During an upgrade, what can cause that one of the /unchanged/ msi's won't
get the new bundle id registered as a dependency in the registry, which
makes Burn wanting to uninstall it?*
This is
Ok, thanks. I'll keep an eye on your thread.
//Caisa
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Really-weird-upgrade-problem-tp7580416p7580441.html
Sent from the wix-users mailing list archive at Nabble.com.
---
Hi all!
I have a really strange upgrade problem that I could use some help with.
Please. :)
I've implemented my own bootstrapper application, but when I started this
project I made a simple BA (that was based on WixBA) just for testing. When
I use my test BA, I can upgrade without any problems at
Hello,
Is there any way to check which files that Burn needs to download before the
installation starts? E.g. a DVD installation where some of the files are
present on the DVD and some files will have to be downloaded.
As far as I can see the only information I can get today is files per
package
Alright, done. Thank you!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Number-of-files-in-download-tp7579138p7579170.html
Sent from the wix-users mailing list archive at Nabble.com.
---
Hi,
I need to display in my GUI the exact number of files that are being
downloaded. I can't seem to get the number of files, just the number of
packages so when an exe or msi has one or more payload file(s) I get the
incorrect number of files.
Is there any way to access number of files after pla
Hi,
1) I tried that clean/rebuild before posting, and it didn't make a
difference.
2) The only info I get is what I wrote in my first message:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7578853/screen.png
I really would like to know which value can't be null.
There
Hi,
I had a few problems with the new Wix Toolset RC, so I decided to reinstall
it, but it keeps failing. I tried to copy paste the links into my browser
and got Network error. Does anyone know when it's gonna get fixed
//Caisa
[06CC:0150][2012-06-13T08:04:36]: Apply begin
[0B00:0780][2012
Hi Matt!
You mean like this?
This is the way I have it today, and both files are copied to the same
package cache folder, but since the installation process of the exe isn't
started from that folder it's not going to find the text file. The process
is started from the path w
If I do that, then .Net 4.0 won't get installed before the BA GUI starts. Or
am I missing something? I tried to put both 3.5 and 4 in the Package group
that's connected to WixMbaPrereqPackageId, but it just crashed.
But thanks anyway!
//Caisa
--
View this message in context:
http://windows-inst
That would work if I had any sort of control over the exe, but I don't.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Exe-package-can-t-find-payload-file-that-s-not-a-dll-tp7578750p7578783.html
Sent from the wix-users mailing list archive at
Hi,
I upgraded to Wix Toolset RC today, and suddenly some MsiPackage elements in
my bundle generated an error: "Value cannot be null" (Light.exe) There are
absolutely nothing special about the packages, and there were no problems
building the BA before the upgrade.
Does anyone know what causes t
I don't have an answer for you, but I got a similar error (the registration
errors) during uninstall and that caused the uninstall to fail. It would be
nice to know what's causing this.
//Caisa
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Fa
Hi,
Is there any way to have both .Net 3.5 and .Net 4.0 as prerequisites (by
using WixMbaPrereqPackageId in some way)?
Some of the packages we're installing need .Net 3.5 and only .Net 4.0 isn't
working. The problem is that our UI needs .Net 4.0 and we've had some
trouble when installing .Net 4.
Hi,
I really need some creative ideas here, some out of the box thinking.
I have a situation where an exe package has a payload file (a text file),
and for this to work under normal circumstances (without Burn, just double
click on the exe) the payload file needs to be placed in the same folder
Never mind, I figured it out. LaunchAction.Layout rules.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-How-change-path-to-Payload-in-ExePackage-element-during-runtime-tp7557033p7578689.html
Sent from the wix-users mailing list archive at Nabb
Hi again,
I think (!) that I've figured out the problem. If I leave the text file in
the same folder as the Bootstrapper-application and only download the exe,
it works. That scenario won't be possible in this application unfortunately,
all files will have to be downloaded.
Is there any way to t
I'm bumping this because it has become quite urgent.
Can anyone help?
Kind regards,
Caisa
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-How-change-path-to-Payload-in-ExePackage-element-during-runtime-tp7557033p7578673.html
Sent from the w
Hi,
Ok, I didn't get a ResolveSource for the text file, only the exe, but
according to the log it found the file anyway. Perhaps Burn uses the exe
packages new path by default for the "internal" payloads?
Unfortunately the exe didn't use the text file during execution and failed
to write to regi
Hello!
I'm developing my own bootstrapper app and I have an exe that needs a txt
file in the same folder to be able to run. I have defined it in my bundle
like this:
And this works if local source path doesn't change after build, but if
setversion.exe and version.txt are place
Hello,
My Bootstrapper application needs to have parallel download and
installation, which Burn doesn't support as far as I know.
I've implemented my own downloader that alerts Burn when the file is
downloaded. I put a Retry in ResolveSource, and it calls that until it gets
a flag telling it to
Yeah well, apparently a simple /s sufficed. I tried that before of course,
but probably in combination with something else, which made the silent
install fail.
Thank you all for your input, I learn more and more about Burn everyday. :)
--
View this message in context:
http://windows-installer-
Alright, I tried a different install command according to an example I found
in the forum:
It didn't work for me unfortunately.
I'm very sorry if I seem a bit slow here, but I don't understand exactly
what input InstallCommand needs. I also tried to input the complete "msiexec
/qn /i" command
Alright, I tried that (/msiexec /qn /i exePath/) and it worked. That can't be
good...
Can you (or anyone else) see any obvious errors with my ExePackage
definition?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Burn-Help-with-silent-install-E
The exe is a patch and is supposed to support silent install, but maybe it
doesn't.
Do you happen to know any "official" exe's that supports silent install,
that I can download and test with? This has bugging me for days, and it
would be nice to find out if I'm doing something wrong or if the file
Hello,
I'm trying to get Burn to silently install an exe, but I can't get it to
work. Can anyone see what I'm doing wrong?
I've also tried /s, /qn and /silent, but no luck.
The installation starts, but so does the the GUI unfortunately.
Any help is appreciated.
//Caisa
--
View this messag
Ah, it works! Thank you so much, you saved my weekend. :)
//Caisa
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Bootstrapper-App-select-msi-s-during-runtime-tp7438959p7439566.html
Sent from the wix-users mailing list archive at Nabble.com.
-
Hi all,
I'm developing a Bootstrapper Application (with my own UX) and I have this
scenario that I really could use some help with:
1) Bundle.wsx defines all available msi's for a specific product.
2) All users download the same bootstrapper.exe from a server somewhere.
*So far so good, but he
30 matches
Mail list logo
