The origin calculation is not accurate. Such as an installation of 100M, the
actual space taken would be 100.4M. So, I want to tell the user, if he just
have merely enough space to pass DiskSpaceCheck step, that he would fail.
The simplest way to do this, seems to be use ReserveCost table to add extra
1% space in the accumulated sum. But, I don't know the actually space, until
in runtime, since we might change the source file before we build final
installer, and the size of the generated MSI file, and temporary space taken
in system drive are not known until we actually have the MSI file, and
install it.
On Tue, Jun 30, 2009 at 11:12 AM, Bob Arnson <
[hidden email]> wrote:
> kezhong zhou wrote:
> > ReserveCost table in a custom action. But I tried a lot of times, found
> that
> > I can only 'SELECT' the ReserveCost table at install time, but can not
> > "INSERT" or "UPDATE" the table. :(
> >
>
> You can't permanently update tables in custom actions. You can make
> temporary changes.
>
> However, why do you need to do it at runtime?
>
> --
> sig://boB
>
http://joyofsetup.com/>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> WiX-users mailing list
>
[hidden email]
>
https://lists.sourceforge.net/lists/listinfo/wix-users>
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
