Title: RE: [Nant-users] Invalid cast error in latest nightly
Hi,
There's probably an obvious answer to this question, but is there any reason why all the static methods in the framework are being wrappered to be used as 'functions' in NAnt?
E.g. assemblyname::get-assembly-
Gert,
Thanks for your prompt help, but I still think this change is as clear as mud. :-)
The function called assemblyname::get-assembly-name() does NOT return an assembly
name, despite the function's name. Instead, it returns and "AssemblyName object,"
which I can't find documented as a typ
code base, ... of a given assembly.
Gert
- Original Message -
From: "Merrill Cornish" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Thursday, October 07, 2004 9:24 PM
Subject: Re: [Nant-users] Invalid cast error in l
Gert,
Actually, I _did_ read the nightly build doc/help before I sent the message. They may
be in there somewhere, but I didn't see any specific changes listed.
Now that I know there is a change, if I compare the documentation for
assembly::get-name() with the previous version, I see that the
8:26 PM
Subject: [Nant-users] Invalid cast error in latest nightly
The first time I ran my build script (which has been working for months)
with NAnt 0.85, 10/6/2004, I got the following error:
Cannot convert argument 1 (assembly) of assembly::get-name() to
'System.Reflection.Assembl
The first time I ran my build script (which has been working for months) with NAnt
0.85, 10/6/2004, I got the following error:
Cannot convert argument 1 (assembly) of assembly::get-name() to
'System.Reflection.Assembly' (actual type was 'string').
Expression: Assembly= ${assembly::get-name(
