[WiX-users] Dark - NullReferenceException due to rows in the AppSearch table

[Frank Eden]

I run dark against my MSI, and I get an exception. Ive tracked it down a
bit, and I find that if I delete particular ros in the AppSearch table, I
can get dark to work. Please find an attached MSI that demonstrates the
problem. Its 4Mg - Sorry its so big!!
Heres the output from dark

C:\junk>dark junk.msi junk.wxs
Microsoft (R) Windows Installer Xml Decompiler Version 3.0.3621.0
Copyright (C) Microsoft Corporation 2003. All rights reserved.


junk.msi
C:\junk\junk.msi : warning DARK1060 : The _InstallValidate table is being
decomp
ble.
C:\junk\junk.msi : warning DARK1060 : The _Required table is being
decompiled as
C:\junk\junk.msi : warning DARK1060 : The _Sequence table is being
decompiled as
dark.exe : warning DARK1065 : The AdvtUISequence table is not supported by
the W
it has been deprecated by the Windows Installer team. Any information in
this t
ut of the decompiled output.
C:\junk\junk.msi : warning DARK1060 : The Cabs table is being decompiled as
a cu
C:\junk\junk.msi : warning DARK1066 : The PatchPackage table is not directly
sup
oolset because it belongs in a patch (msp) file. This table can be
indirectly c
patch creation (pcp) file using WiX, then using PatchWiz to create a patch
(msp)
tion in this table will be left out of the decompiled output.
dark.exe : error DARK0001 : Object reference not set to an instance of an
object

Exception Type: System.NullReferenceException

Stack Trace:
at
Microsoft.Tools.WindowsInstallerXml.Decompiler.FinalizeSearchTables(TableC
at
Microsoft.Tools.WindowsInstallerXml.Decompiler.FinalizeDecompile(TableColl
at Microsoft.Tools.WindowsInstallerXml.Decompiler.Decompile(Output
output)
at Microsoft.Tools.WindowsInstallerXml.Tools.Dark.Run(String[] args)

Unhandled Exception: System.NullReferenceException: Object reference not set
to
bject.
at
Microsoft.Tools.WindowsInstallerXml.Decompiler.FinalizeSearchTables(TableC
at
Microsoft.Tools.WindowsInstallerXml.Decompiler.FinalizeDecompile(TableColl
at Microsoft.Tools.WindowsInstallerXml.Decompiler.Decompile(Output
output)
at Microsoft.Tools.WindowsInstallerXml.Tools.Dark.Run(String[] args)
at Microsoft.Tools.WindowsInstallerXml.Tools.Dark.Main(String[] args)


If I open the MSI with Orca, then delete a row from the AppSearch table
LABELINKINSTALLDIR AppFile5
then all is well.

I suspect that the problem might be somehow related to the fact that
AppFile5 refers to a second row in the DrLocator table:

AppFile5 AppFile5SigFile 2
AppFile5SigFile [ProgramFilesFolder] 2
http://www.nabble.com/file/p14554976/junk.msi junk.msi

[Bob Arnson]

Post by Frank Eden
I run dark against my MSI, and I get an exception. Ive tracked it down a
bit, and I find that if I delete particular ros in the AppSearch table, I
can get dark to work. Please find an attached MSI that demonstrates the
problem. Its 4Mg - Sorry its so big!!

Your attachment didn't come through. Please enter a bug and try
attaching the MSI. (I'm not sure what the size limits on attachments are
in the SF bug system, though; it might be too big.)

[Frank Eden]

Ive uploaded the MSI that causes the problem to
http://www.netspeed.com.au/frankeden/junk.zip

I havent added a new bug because this one: - "[1576981 ] Dark cannot
decompile Votive.msi"
looks similar, but the date that bug was submitted was over a year ago, so
does this mean that development on dark is not active at the moment?

That would be a shame, because being able to decompile our existing MSIs is
very important to me.

[Bob Arnson]

Post by Frank Eden
I havent added a new bug because this one: - "[1576981 ] Dark cannot
decompile Votive.msi"
looks similar, but the date that bug was submitted was over a year ago, so
does this mean that development on dark is not active at the moment?

There are one or two people looking at Dark bugs which is why we need
examples.

[Frank Eden]

No worries, Ive created this bug number:

1864685 NullReferenceException due to rows in the AppSearch table