We observed a rarely occuring patch issue resulting in not working
updates on windows xp. It was possible to reproduce the issue in a
little sample project with only one file included.
According to our observations, the file contents are crucial to
reproduce the issue. A simple rebuild of the file
> That violates component rules; you need to add new resources (e.g.,
> files) to new components.
So this weird issue is only happening because we're breaking component
rules?
Whats the best (and easiest) way to manage patch-/setup creation of a
product that changes it (data-)file subset from
Hello,
we've three minor updates (all are changing the ProductVersion property).
1.) Update from RTM (8.0.1000) to 8.0.1200
2.) Update from 8.0.1200 to 8.0.1210
3.) Update from 8.0.1210 to 8.0.2000
Version 8.0.1200 (and therefore the first update) adds some new files to an
existing component.
-
Hi all,
we're using WiX (using PCP-Files, pyro isn't possible because the resulting
.msp-files are significant smaller and applying them never worked) to create
patches for our application.
When applying a patch, we're encountering sporadic patch problems with
ErrorCode 1321 (No permission
4 matches
Mail list logo