AM
To: Miller, Kevin; [EMAIL PROTECTED]
Subject: Re: [Nant-users] Framework Targeting
Try
asis="true"
instead of frompath="true".
This is based on the fact that csc.exe from a particular CLR is able to
locate the correct system libraries, when you don't specify the pat
We are targeting the 1.1 framework. We changed our build scripts to
include:
However I noticed that 1.0 dlls were still being referenced for
assemblies referenced via frompath="true". The cause was the fact that I
had the builds running from a ".NET command prompt" or a command
environment with
I am trying to invoke a licensed component within an NAnt task I have created. I have
a license resource attached to the Dll in the same fashion I have used it in the Exe I
originally housed the code I am taskifing. Has anyone ran into this problem before. I
know it is not really NAnt's fault. I
Once
you set a property I believe it is scoped to the entire project meaning it is
visible everywhere. You can update it later on in your script, no
problem.
Note,
If you set a property via the commandline inputs those properties are ReadOnly
and cannot be changed. You can try to update R
I wish to generate an .msi installer for a windows service. We use NAnt in our build
process. I noticed that there is an msitask in the NAntContrib project but it seems to
be lacking support services. I know little about .msi (Windows installer) generation.
If anyone has run into a similar prob
