Is there a problem with dark.exe (v 3.0.4805.0) in decompiling MsiAssembly
tables?
Dark is giving warnings like this:
> Migration.msm : warning DARK1059 : The MsiAssembly table contains a
> row with primary key(s)
> 'DataObjects.v0405.dll.5DF28CB2_8D5D_4385_994C_3AB91FB1B53A'
> whose Component_ column contains a value,
> 'DataObjects.v0405.dll.5DF28CB2_8D5D_4385_994C_3AB91FB1B53A', which
> specifies a foreign key relationship with the Component table. However,
> since the expected foreign row specified by this value does not exist,
> this will result in some information being left out of the decompiled
> output.
for the entire MsiAssembly table. The foreign row does actually exist in the
Component table. Dark appears to reject all rows in MsiAssembly, adding none to
the WXS. Fwiw the command line which seems to work best for me is
dark -x temp Migration.msm
I have to convert a whole bunch of merge modules to WXS, so I'm reluctant to
hand-code the MsiAssembly table for each and every one if there's a possible
workaround.
thanks
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
