From: Gert D. <ger...@te...> - 2009-01-29 17:41:36
|
Beth, No, that should do it. Can you try just executing cabarc from within your build file first? For example: <exec program="cabarc" /> Gert From: Beth Hechanova [mailto:bhe...@im...] Sent: donderdag 29 januari 2009 17:51 To: nan...@li... Subject: Re: [NAnt-users] msi task - 'cabarc' failed to start Hi Gert, Actually I did not have the Cabinet SDK installed, but I do now (c:\tools\cabsdk). I then updated my PATH env variable to include c:\tools\cabsdk\bin. If I open a new command prompt window and just type 'cabarc', the program is found. However this had no effect on my msi task in my nant script. I am still getting the same behavior. I then put an echo statement to print the path (${environment::get-variable('PATH')) in the NAnt script just to be sure the cabsdk was part of that path, and it is. Do I need to configure something else in order to find the Cabinet SDK? Thanks for your help, Beth Re: [NAnt-users] msi task - 'cabarc' failed to start Gert Driesen Wed, 28 Jan 2009 12:07:58 -0800 Beth, Do you have the Cabinet SDK installed? Can you launch cabarc.exe from the command prompt? Gert From: Beth Hechanova [mailto:bhechan...@imsco-us.com] Sent: woensdag 28 januari 2009 19:30 To: nan...@li... Subject: [NAnt-users] msi task - 'cabarc' failed to start Hi, I saw a thread with the same subject approx a year ago in the mail archive, but I did not see any resolution. I am having the same exact problem. At the end of this email is the output from running the msi task from my nant script. I have not done anything with setting a path (either env variable or within the nant script itself). . <snip> This email and any files transmitted with it are confidential & proprietary to Systems and Software Enterprises, Inc. (dba IMS). This information is intended solely for the use of the individual or entity to which it is addressed. Access or transmittal of the information contained in this e-mail, in full or in part, to any other organization or persons is not authorized. No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.15/1921 - Release Date: 1/29/2009 7:13 AM |