Alexander Stock wrote:
> So this weird issue is only happening because we're breaking component
> rules?
>
I can't know for sure without more details, but it's certainly possible.
Successful patching relies on strictly following the component rules,
because patching itself relies on proper
> 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
Alexander Stock wrote:
> Version 8.0.1200 (and therefore the first update) adds some new files to an
> existing component.
>
That violates component rules; you need to add new resources (e.g.,
files) to new components.
--
sig://boB
http://joyofsetup.com/
--
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.
-
4 matches
Mail list logo