Yes, this is a problem with the 0.7.9 release. It
has been fixed. If you try one of the recent builds (nant.sf.net/builds) you
will not be annoyed by this bug anymore.
Sorry for the inconvience, and please keep the
reports coming.
Scott
Not sure what I did, but I typed the following
command:
nant -verbose -buildfile:csdpublish.build
buildpublisher
and received the following error:
INTERNAL ERRORSystem.UriFormatException:
Invalid URI: The format of the URI could not be determined. at
System.Uri.Parse() at System.Ur
[Hello...new to the list]
>> NAnt uses reflection in combination with the TaskAttribute
>> to match your attributes up with your properties and a privately
>> scoped property not only won't show up in reflection,
>> but NAnt wouldn't be able to assign to it even if it did.
You can view and set
That will -definitely- keep it from working. NAnt uses reflection in
combination with the TaskAttribute to match your attributes up with your
properties and a privately scoped property not only won't show up in
reflection, but NAnt wouldn't be able to assign to it even if it did.
Hmmm... Is there
Hi,
Apparently it's currently not necessary to build separate assemblies for
the Windows CE and PocketPC .NET Compact Framework platforms, but I still
think that we should provide different assemblies (or take into account
that this is necessary in the near future) for both platforms, even if
Hi Ian,
Thanks for you answer!
I think that, in the end, it should be possible to both specify a default framework
version on the buildfile level and override that framework version (and type, in case
of .NET Compact Framework) on the task level, certainly for all DotNetTasks. That
would also
