Using MergeModules can create invalid .wixpdbs #5270

robmen opened this Issue Apr 20, 2016 · 0 comments


None yet
2 participants

robmen commented Apr 20, 2016


If this issue is a bug:

  • Which version of WiX are you building with?


  • Which version of .NET are you building with?

NET FX v4.6.1

  • If the problem occurs when installing your packages built with WiX, what is the version of Windows the package is running on?

Win 8.1

  • Describe the problem and the steps to reproduce it.

When using a Merge element an internal WixMerge table is created. It is possible (even likely) for the FileCompression and ConfigurationData to get set to null by the compiler. However, null is not allowed by the schema in tables.xml.

  • Describe the behavior you expected and how it differed from the actual behavior.

Either the columns should never be allowed to be null or the table schema needs to be updated to allow nulls.

@barnson barnson added this to the v3.11 milestone May 4, 2016

@barnson barnson added bug linker labels May 4, 2016

rseanhall added a commit to rseanhall/wix4 that referenced this issue Feb 19, 2017

Properly set WixMerge columns nullable
FileCompression and ConfigurationData should both be nullable.

Fixes wixtoolset/issues#5270
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment