Hello MSI gurus,
I've faced with an interesting issue, which is now a kind of academic interest
for me.
I had to modify the MSI tables from an immediate custom action using DTF. I was
using View.Modify method with InsertTemporary option, as it is the only way to
"change" the MSI database at runtime. All the tables required were addressed by
this technique, including Property.
However, I mentioned that my custom action behaves incorrectly. I've been
setting a property containing the disk root (e.g. D:\) and then referenced that
property from Directory table. But in the log file that property fell back to a
disk root with the most of free space (as if the TARGETDIR wasn't set).
When I changed the property set operation from View.Modify to
session["PROP_NAME"] = "D:\", everything started working correctly.
So, my question is what's the difference between MsiViewModify and
MsiSetProperty? And are there any recommendations where to use each?
Thank you.
-- Yan
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
