In article <[EMAIL PROTECTED]>,
"Jason J. W. Williams" <[EMAIL PROTECTED]> writes:
> I really appreciate your help. It ended up being a stupid typo in the
> variable name I was comparing. Don't know how many times I looked at
> it and it looked right... I'm sorry for the wild goose chase. Thank
> you very much for helping me though.
I've done things like use naming conventions for identifiers in order
to identify typos like this in an ICE. Unfortunately with properties
there isn't a good way to use the Property table to say "this row
represents a valid property whose value is empty". However, you could
create your own custom table that just lists the names of your
variables. You could them parse all condition columns to see that
they only use valid expressions consisting of predefined property
values, constants, valid operators, and your own variables listed in
the custom table.
This is all a bit much just to check for the occasional typo, but it
might be worth it in a particularly large install with lots of custom
properties. I'd only build this infrastructure if I'd been bitten by
typos in variable names three times or more.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
