In case anyone discovers this thread later on - my finding so far is
that there is some problem with Windows Installer 4.5 when running on
Virtual PC/Virtual Server/Hyper-V (in my case with Windows Server 2008
x86 but others may be affected).  I'm still not sure of the correct way
to raise this (on Connect somewhere?).  There seems to be some
difference in the way the system reports disk cost to Windows Installer
when in a VPC (kind of understandable given what it is doing), and this
in turn seems to cause CostingComplete to behave inconsistently.

For non-UI installs this doesn't matter, but the UI is peppered with
SpawnDialogs such as the following if CostingComplete hasn't finished
(is non-zero).

        <Publish Event="SpawnWaitDialog"
Value="WaitForCostingDlg">CostingComplete = 1</Publish>

To work around this, I elected to visit the Wix 3.0.5217 source and make
my own WiXUIExtension wixlib with these SpawnWaitDialog publish events
commented out in each dialog.  By the way, serious kudos to the hard
work on Votive - I able to add my custom WiXUIExtension wixproj to my
existing installer solution and add a project reference to this instead
of the binary reference to WiXUIExtension and it all compiled
successfully.

Thanks, Stuart.

-----Original Message-----
From: Preston, Stuart 
Sent: 01 May 2009 01:50
To: General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] WixUI_Advanced and WixPerMachineFolder setting

> Check out 
>
http://www.symantec.com/connect/forums/costfinalize-does-not-work-window
s-installer-45. 
> It points to a hotfix that they claim fixes the problem...?

Thanks - I tried that today with no joy.  However, I've since discovered
this only seems to occur for me when running inside Virtual PC 2007 SP1.
I found a physical 2008 server, installed Windows Installer 4.5 on it
and didn't get the issue at all...  

Then I rolled back to Windows Installer 4.0 in my Virtual PC and could
install with no issues.  The plot thickens.

All these blog posts talk about the issue but with no explanation.  

http://bloggingabout.net/blogs/harold/archive/2009/01/14/windows-install
er-doesn-t-finish-determining-disk-space-requirements.aspx

http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2009/03/03/vs
ewss-1-3-please-wait-while-the-installer-finishes-determining-your-disk-
space-requirements.aspx

http://blog.fus.net/post/97012275/public-service-announcement-crystal-re
ports-2008

http://blog.walkmind.com/2009/04/windows-installer-doesnt-finish.html

http://www.hyperbina.com/tech/blog/?p=52

http://hometalk.homedesignersoftware.com/showthread.php?t=10513 

http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg25658.htm
l 

So my repro may be null and void unless running in VPC 2007 SP1, Windows
Server 2008 and Windows Installer 4.5.  I'm sure WiX isn't the problem
but I would like to get to the bottom of it as it seems like a
significant issue that shouldn't really exist.

Stuart.

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to