Hello all,
I am facing a strange problem where an assembly is not upgraded in the GAC
after a major upgrade.
V1.0 of the msi package contains v1.0.19.0 of the assembly
V1.1 of the msi package contains v1.0.21.0 of the assembly.
This assembly is sourced using a merge module.
When i execute v1.1
I have posted the logs
https://gist.github.com/johnstile/aed128a3dd268b008f4a
On Tue, 2014-07-22 at 03:21 +, Hoover, Jacob wrote:
> Posting links to logs of the downgrade (both the uninstall and the install
> logs) would help deduce the actual problem. The bundle logs detect and
> planning
I have not been able to collect any more information on the scenario where
the feed download by the bundle indicated a higher version number, but the
bundle reported 'up to date'. I have not duplicated that scenario on
several systems since this morning, so I am going to let this issue cool its
he
I have been trying to get the logging.
On my test PC I can only get setups created with the Release build of wix
3.9.720 to run, so when using the test box I tried to add log messages to
each of the three handlers, but in this situation it seems that DetectUpdate
is never fired. (As indicated b
Need logging around the DetectUpdateBegin/DetectUpdate/DetectUpdateComplete
events in your MBA. Are you seeing detect being triggered twice?
If you don't return Result.Ok, then the engine won't download and parse the
feed. If you return Result.Ok (which seems to be the case since you say in
fi
I transitioned my mba code to model the WixBA UpdateViewModel code in wix
3.9.720. Initially it detected the latest new update and appeared to work
as expected. However the more I play with it I seem to run into a problem
multiple times. I am still a little unsure of how I get to this problem,
b
6 matches
Mail list logo
