using extensions in 4.0 is not automatically handled for you

[wixbot]

Using wix 4.0.2220.0 i'm finding that use of oob extensions is not automatically handled for me like it was in 3.9 and earlier releases. My expectation is that this would be the case.

Note that i tried adding these entries to | properties | tools settings | compiler and linker fields so that I can make use of <iis:* />, <sql:* /> and <utils:* /> syntax found in these namespaces . . .

-ext "C:\Program Files (x86)\WiX Toolset v4.0\bin\WixIisExtension.dll" -ext "C:\Program Files (x86)\WiX Toolset v4.0\bin\WixSqlExtension.dll" -ext "C:\Program Files (x86)\WiX Toolset v4.0\bin\WixUtilExtension.dll"

but when I compile this leads to a bunch of compiler [ / candle.exe ] errors having the following signature.

• Error 102 The extension 'WixToolset.Extensions.IIsExtensionData' contains a definition for table '' that collides with a previously loaded table definition. Please remove one of the conflicting extensions or rename one of the tables to avoid the collision. candle.exe 0 1 Setup (Setup\Setup)
• Error 102 The extension 'WixToolset.Extensions.SqlExtensionData' contains a definition for table '' that collides with a previously loaded table definition. Please remove one of the conflicting extensions or rename one of the tables to avoid the collision. candle.exe 0 1 Setup (Setup\Setup)
• Error 102 The extension 'WixToolset.Extensions.UtilExtensionData' contains a definition for table '' that collides with a previously loaded table definition. Please remove one of the conflicting extensions or rename one of the tables to avoid the collision. candle.exe 0 1 Setup (Setup\Setup)

Originally opened by robertob

[wixbot]

The namespaces for the extensions have changed as well. Run WixCop.exe against your source code ot update it to WiX v4.0

Originally posted by robmen
Resolution set to expected
Status changed from Untriaged to Resolved