I recently had the problem that I created a build server that did not have
Visual Studio installed and I needed to compile .NET 3.5 code. I figured out
that NAnt 0.86 beta 1 was looking for registry keys in the
HKLM\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v6.0a\WinSDKNetFxTools hive.
To fix this
Hi Beth,
The problem appears to be that the working directory - which is a temporary
directory created by the task - no longer exists when cabarc is
executed.
I'll look into that, and make a new nightly build available that either
fixes this issue (if I find the cause) or adds more tracing
Gert,
I tried executing cabarc from my build file - that works (at least I get
a .cab file - I'm not sure how the msi file gets generated.)
Executing the msi block gives the same error (pasted again below).
Here's the Distribute target I currently have (with the exec to cabarc
directly):
It is a little painful, but it is possible. The idea is to be able to
address each FileItem node individually. If each Path property is
unique across all of the FileItem nodes, then you can use that property
to "pick-out" each FileItem node:
File:
Beth,
No, that should do it.
Can you try just executing cabarc from within your build file first?
For example:
Gert
From: Beth Hechanova [mailto:bhechan...@imsco-us.com]
Sent: donderdag 29 januari 2009 17:51
To: nant-users@lists.sourceforge.net
Subject: Re: [NAnt-users] msi t
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
Hi,
I've run into a problem building an msi using nAnt. I hope you can give me
some idea of what is wrong.
I am setting up my directory as seen in the build below.
When I set the foldername for USR to something five characters long or less, I
get an entry for it in the Defaultdir field of the
