Hi everybody...
I imagine I'll take some flak for this, but we still have
installers being cobbled together by Wix 2.0.
Recently I was tasked with upgrading our product builds from VS 2005 to VS 2010
(and moving our production environment from Windows Server 2003 to 2008). I
just got all the product build converted and running under VS 2010 (with a side
nightmare thanks to Sourcegear Vault). My Wix project cranked out .msis
without complaint.
But when I went to install the msi on Windows 2008, it threw an
exception 2765. Not a lot of information on what the problem is. Not sure if
it's some kind of difference between W2003 and 2008, the version of the msi
installer on the os or what. It did say there was one specific merge module at
the time, a .net assembly that was going to be put in the gac.
I'd run Wix under VS 2005 figuring that the bundling of the
build product didn't need to be upgraded, but to start eliminating variables I
upgraded the Wix solution to VS 2010 and tried the msi outcome of that. Same
error.
I went to install Wix 3 (baby steps), but that installer still
only offered VS 2005 integration.
I haven't worked with Windows Server 2008 much and I haven't
seen this installer error before. Is this a Wix compatibility issue or an OS
issue?
Thanks
Mark
------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
