Kevin,
Are you running a nightly build ? If so could you post a small repro of
this issue. The script task should load the reference ok but there have
been some issues in this area.
Ian
Burton, Kevin wrote:
I am getting the following error in a
Gary Feldman wrote:
From: "Andy Harris" <[EMAIL PROTECTED]>
Sent: Thursday, August 26, 2004 12:59 PM
I will have target name collision if I do that. There exist a common set
...
concept of dependencies across build files. My original plan was to
have
n build files, but a bui
Edwin,
Are you running a recent nightly build ? A bug with component locking was fixed
recently.
Ian
Castro, Edwin Gabriel (Firing Systems Engr.) wrote:
Please let me know if this is not the correct place to post this.
I'm using to unregister a number of components.
I noticed that when you try to
Is there a way to stop/unenlist send ports or setting the pipelines used by
the send ports to passthrough using NAnt? I can't remove the send ports
since they've got a reference to the pipeline assembly, and I can't remove
the pipeline assembly when the send ports are using the pipelines... What
I am getting the following error in a
Gert,
Sorry to bother you too much!!!.
I tried to develop a sample application with real long file path names
and lot of subfolders to mimic my actual project. but the test project
got built successfully with NAnt. so even i dont know how to reproduce
this error (vbc Command line error BC2001).
I just upgraded to the latest nightly, after using one from back at the
beginning of July, and discovered that the logging behavior of has
changed.
It used to print out the program file that was being executed, but doesn't
do that any more. The comment in the log for ExecTask.cs says that this
r
>From: "Andy Harris" <[EMAIL PROTECTED]>
>Sent: Thursday, August 26, 2004 12:59 PM
>I will have target name collision if I do that. There exist a common set
...
> concept of dependencies across build files. My original plan was to
have
> n build files, but a build target in one is dependant on bui
Please let me know if this is not the correct place to post this.
I'm using to unregister a number of components.
I noticed that when you try to unregister a component that has been
previously unregistered the unregistration process fails. I don't
think there is an easy way to tell whether a comp
I will have target name collision if I do that. There exist a common set
of targets in all my build files such as build, clean, test, etc. I
could rename the targets in every file to be more like projectA.clean,
projectA.build, projectA.test, etc. However, this makes it a little less
intuitive for
Hello,
I am looking at converting my build files from .84 to .85
when the new version releases. I was experimenting with a recent version of the
nightly code and noticed that properties can no longer have descriptions.
This worked on .84 and I was wondering if this can be added
bac
David,
You cannot use camma separated entries in the name attribute.
Use this instead :
Hope this helps,
Gert
- Original Message -
From: "David Thielen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 26, 2004 3:55 PM
Subject: [Nant-us
Hi;
I have the following:
And it does nothing. It even says 0 assemblies signed. This
is with the latest release
version.
Any ideas?
Thanks - dave
Title: How to detect Mac OS?
Hello!
One of my library design requirements is cross platform build script which cen be run on Win/*nix/Mac OS. Detecting two first with nant is strightforward but how can I setect Mac OS?
Any ideas?
Cheers
Jacek
14 matches
Mail list logo
