#1133 Wix 3.0.3829.0 and 3.0.3907.0 problem

[Ivan J]

After installation wix 3.0.3829.0 I was not abble open visual studio project and visual studio was crashing - see attached screenshots. The latest version: 3.0.3907.0 is not crashing visual studio, but doesn't load wix project (the same error: HRESULT E_FAIL..... a call to a COM component), I also added screenshot.
The last 'working' version is: 3.0.3815.0

My configuration:

Vista 64 Ultimate, SP1

Microsoft Visual Studio 2008
Version 9.0.21022.8 RTM
Microsoft .NET Framework
Version 3.5
Installed Edition: Professional

Latest hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB947789) KB947789

ReSharper 3.1 RC Full Edition build 3.1.571.4
Windows Installer XML Version 3.0

/latest working version /
Votive - Windows Installer XML (WiX) Toolset, Version 3.0.3815.0
Copyright © Microsoft Corporation. All rights reserved.

I got the very same behaviour on 2 different workstations:

1. Intel E8400, 4GB RAM
2. Intel X9650, 4GB RAM

Software configuration is the same for the both computers.

[Ivan J]

screenshots

[Dominik Guder]

Logged In: YES
user_id=437335
Originator: NO

Same error here with VS2005.
In 3.0.3829.0 the references seemed to be the problem, so I tried 3.0.3907.0.
References are working now, but sub folders are causing this error now.

• Create New Project
• Save
• Close and Open (working)
• Just add an empty folder
• Save and close
• Open is not working anymore. :(

If I put all my wix file aside of project file then it is working in 3.0.3907.0.

hth
Dominik

[Markus Loibl]

Logged In: YES
user_id=424353
Originator: NO

Hello,

I had also problems opening a project!
I had some subdirectories within my project:
After removing from the wixproj...

<itemgroup>
<folder include="NewFolder1\">
</folder></itemgroup>

... and after CLOSING COMPLETELY DevStudio (yes, just reload doesn't work!!) and reopening the solution, I could open it normally without E_FAIL!

I then just inserted my previously removed resources to the projects' root, and it works for me.

[Anonymous]

Logged In: YES
user_id=2025042
Originator: NO

I’ve been able to further pin down the source and repro steps for generating the "Error HRESULT E_FAIL has been returned from a call to a COM component." issue when reopening a wix3 project using the current builds.

Repro path 1

1. file | new | WixProject | <anyname></anyname>
2. references | addReference | <anywixextension></anywixextension>
3. save solution, close and reopen
4. <project> | add | newFolder | <anyname></anyname></project>
5. save solution, close and reopen at which time bug repro’s

Repro path 2

1. file | new | WixProject | <anyname></anyname>
2. <project> | add | newFolder | <anyname></anyname></project>
3. save solution, close and reopen
4. <project> | references | addReference | <anywixextension></anywixextension></project>
5. save solution, close and reopen at which time bug repro’s

Work around 1
Open project file in notepad and remove all <wixextension…> entries then readd them with ide once project has successfully reopened. Removing <folder include…=""> entries would work as well but requires also removing </folder></wixextension…>

*.wixproj settings that will cause repro
<itemgroup>
<wixextension include="WixIIsExtension">
<hintpath>C:\Program Files (x86)\Windows Installer XML v3\bin\WixIIsExtension.dll</hintpath>
</wixextension>
<compile include="WixProject1.wxs">
<folder include="NewFolder1\">
</folder></compile></itemgroup>

*.wixproj settings that will not cause repro
<itemgroup>
<wixextension include="WixIIsExtension">
<hintpath>C:\Program Files (x86)\Windows Installer XML v3\bin\WixIIsExtension.dll</hintpath>
</wixextension>
<compile include="WixProject1.wxs">
</compile></itemgroup>

*.wixproj settings that will not cause repro
<itemgroup>
<compile include="WixProject1.wxs">
<folder include="NewFolder1\">
</folder></compile></itemgroup>

[Bob Arnson]

Logged In: YES
user_id=26581
Originator: NO

There are some known regressions on VS2005, but can you reproduce this problem on VS2008 with WiX v3.0.4109 or later?

[Jason Ginchereau]

Logged In: YES
user_id=2086430
Originator: NO

I fixed this bug in build 3.0.4014.