This looks like a Votive bug and not a configuration issue. Please log a bug for this on the SourceForge site:
https://sourceforge.net/tracker2/?group_id=105970&atid=642714 Thanks, Justin -----Original Message----- From: David KILLICK [mailto:[EMAIL PROTECTED] Sent: Thursday, November 20, 2008 11:04 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Votive (3.0.4318.0) with VS2005 Is anyone able to help me with this ? Votive is listed in the "Product details" section of the WiX entry of the VS2005's "Help / About MS VS ..." pop-up dialog that lists "Installed products". Here's the snippet I see ... Windows Installer XML Version 3.0 Votive - Windows Installer XML (WiX) Toolset, Version 3.0.4318.0 Copyright (c) Microsoft Corporation. All rights reserved. So is this a Votive bug I'm dealing with rather than a dev env setup problem ? ________________________________ From: David KILLICK Sent: Wednesday, 19 November 2008 13:37 To: 'wix-users@lists.sourceforge.net' Subject: Votive (3.0.4318.0) with VS2005 I am wondering if I have missed any steps to install Votive for use with VS2005 ... ProjectAggregator2.msi was installed first, then Wix-3.0.4318.0.msi. Other than not getting descriptive error messages (just error code numbers - the subject of my earlier posting), things seem to be working until I decided to try to specify the output directory for the generated *.msi file ... Since the WiX project properties only allows the base output file name to be specified (no directory path permitted), I added the following "Post-build Event Command Line": copy /y $(TargetPath) $(SolutionDir) Now when I press the "Build Solution" button in VS2005, the output window reports the following (see the "copy" command line): ------ Build started: Project: IPDS_Installer, Configuration: Debug x86 ------ C:\Program Files\WIXv3\bin\candle.exe -dDebug -d"DevEnvDir=*Undefined if not building from within Visual Studio*" -d"SolutionDir=*Undefined if not building a solution or within Visual Studio*" -d"SolutionExt=*Undefined if not building a solution or within Visual Studio*" -d"SolutionFileName=*Undefined if not building a solution or within Visual Studio*" -d"SolutionName=*Undefined if not building a solution or within Visual Studio*" -d"SolutionPath=*Undefined if not building a solution or within Visual Studio*" -dConfiguration=Debug -dOutDir=bin\Debug\ -dPlatform=x86 -dProjectDir=C:\IPDS\Dev\DI3_Installer\ -dProjectExt=.wixproj -dProjectFileName=IPDS_Installer.wixproj -dProjectName=IPDS_Installer -dProjectPath=C:\IPDS\Dev\DI3_Installer\IPDS_Installer.wixproj -dTargetDir=C:\IPDS\Dev\DI3_Installer\bin\Debug\ -dTargetExt=.msi -dTargetFileName=IPDS_Installer.msi -dTargetName=IPDS_Installer -dTargetPath=C:\IPDS\Dev\DI3_Installer\bin\Debug\IPDS_Installer.msi -out obj\Debug\Product.wixobj -arch x86 -ext "C:\Program Files\WIXv3\bin\WixNetFxExtension.dll" -ext "C:\Program Files\WIXv3\bin\WixUtilExtension.dll" Product.wxs C:\Program Files\WIXv3\bin\Light.exe -ext "C:\Program Files\WIXv3\bin\WixNetFxExtension.dll" -ext "C:\Program Files\WIXv3\bin\WixUtilExtension.dll" -out C:\IPDS\Dev\DI3_Installer\bin\Debug\IPDS_Installer.msi -pdbout C:\IPDS\Dev\DI3_Installer\bin\Debug\IPDS_Installer.wixpdb obj\Debug\Product.wixobj copy /y C:\IPDS\Dev\DI3_Installer\bin\Debug\IPDS_Installer.msi *Undefined if not building a solution or within Visual Studio* The syntax of the command is incorrect. C:\Program Files\MSBuild\Microsoft\WiX\v3.0\Wix.targets(1859,5)Error MSB3073: Done building project "IPDS_Installer.wixproj" -- FAILED. Build FAILED. ========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ========== Why are so many of the macros defined as "*Undefined if not building [a solution or] from within Visual Studio*" when I am building a solution from within the VS2005 IDE ? It seems that Votive is not properly registered with VS2005 ... the VS2005 Tools / Add-In Manager does not report the presence of WiX or Votive (should it?). I can't find any additional information about this in either the wix.chm file or on the WiX/Votive web home pages to continue debugging where things are going awry. Thanks. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
