Gert,
I just tried this:
<property name="assembly.path" value="${outdir + '\' + nunit.assembly}" />
<property name="assemblyname.obj"
value="${assemblyname::get-assembly-name(assembly.path)}" />
<echo message=" Assembly = ${assembly::get-name(assemblyname.obj) + ' v'
+
assembly::get-version(assemblyname.obj)}" />
where the assembly.path property had existed before, but the assemblyname.obj property
is new and the expression in the <echo> is new.
I got another "Invalid case from System.String to System.Reflection.Assembly." I
assume that means that the AssemblyName object returned by
assemblyname::get-assembly-name() cannot be stored in a property. Instead, the only
apparent use for assemblyname::get-assembly-name() is as the argument to one of the
other assemblyname::* or assembly::* functions.
If it is true that an AssemblyObject returned by assemblyname::get-assembly-name()
can't be used anywhere except as an argument to another function, then that seems to
argue for changing the allowable arugments to the other functions. A language in
which the return value of a function cannot be saved it weird.
Merrill
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
