Yes, that does sound like a bug that was fixed post-Beta.
On Wed, Feb 1, 2012 at 9:46 AM, Romeo S. wrote:
> It seems it has been fixed on latest build. I just reproduced it on the
> Beta
> but not in 3.6.2527.0
>
> Cheers,
> Romeo
>
> --
> View this message in context:
> http://windows-installer
It seems it has been fixed on latest build. I just reproduced it on the Beta
but not in 3.6.2527.0
Cheers,
Romeo
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Moving-payload-to-Cache-Directory-tp7237441p7243773.html
Sent from the wix-users ma
I faced the same problem with the .Net 4.0 prerequisite. It seems that the
package is actually downloaded, even though it is not uninstalled.
Here is my package declaration:
http://go.microsoft.com/fwlink/?LinkId=164193";
DetectCondition="Netfx4FullVersion AND (NOT VersionNT64 OR
Netfx4
It seems I can't reproduce it anymore.
Thanks
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Moving-payload-to-Cache-Directory-tp7237441p7241383.html
Sent from the wix-users mailing list archive at Nabble.com.
What is the Detect and Plan state for the ExePackage?
On Mon, Jan 30, 2012 at 10:16 AM, Romeo S. wrote:
> Hi,
>
> I noticed that Burn moves the payload to Cached Directory during uninstall
> even though the ExePackage/@Permanent="yes" is set, tried to search the bug
> list see if there's any rel
Hi,
I noticed that Burn moves the payload to Cached Directory during uninstall
even though the ExePackage/@Permanent="yes" is set, tried to search the bug
list see if there's any related issue about it but no luck. Is this by
design?
The problem is if the Payload is too big like 1000s of files, i
6 matches
Mail list logo
