Something strange just started happening to my NAnt executions. (I'm running NAnt
0.85 (Build 0.85.1708.0; net-1.0.win32; nightly; 9/4/2004).) The exception is shown
below. It appears that the exception is thrown AFTER the target has completed all of
its work. If it weren't for the unhandled exception, there would be nothing in STDOUT
or STDERR to indicate a problem.
This exception started after I modified my NAnt script. However, the change was
straightforward, the modified script claims no syntax errors, and it appears to run as
I intended. On the other had, it DID have at least two unflagged XML syntax errors.
While making the modifications, I ran across the following <if> statement:
<if test="${report and file::exists(nunit.xml)}" >
<loadtasks path="${outdir}" verbose="${verbose}" />
<nunitreport out="${report.out}"
xslfile="${report.xslt}" >
failonerror="false"
verbose="${verbose}" >
<fileset basedir="${outdir}" >
<include name="${nunit.xml}" />
</fileset>
</nunitreport>
</if><!-- nunit.xml -->
Notice the extraneous > on the xslfile line.
I removed the > along with making the other changes, and the problems started. I put
the extra > back and the problems continued.
It then occurred to me that MAYBE there was an compensating error someplace else that
hid the extraneous >. Sure enough, I found this: <echo message=" ... "/>"/>
That's an error, but it doesn't look like a compensating error. No only is there a
close tag with no open, there is an extraneous " which should wreak havoc with the
following syntax--but it didn't.
I've now physically looked at all >, and they NOW seem OK. I used Replace All to
count < and to count >, and the counts match. Also, there are an even number of ".
(This is a 700+ line script, so simple code reading isn't easy.)
Any ideas,
Merrill
======================================================
Unhandled Exception: System.Runtime.Remoting.RemotingException: Object
</a0a1b855_93ae_4440_a826_a184373d6f90/u3Q6hY0OVqvGphvFHMIUHg89_2.rem> has been
disconnected or does not exist at the server.
Server stack trace:
at
System.Runtime.Remoting.Channels.ChannelServices.CheckDisconnectedOrCreateWellKnownObject(IMessage
msg)
at System.Runtime.Remoting.Channels.ChannelServices.SyncDispatchMessage(IMessage
msg)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg,
IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData,
Int32 type)
at NAnt.Console.HelperArguments.get_ExitCode() in
C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp125A.tmp\src\NAnt.Console\ConsoleStub.cs:line 276
at NAnt.Console.ConsoleStub.Main(String[] args) in
C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp125A.tmp\src\NAnt.Console\ConsoleStub.cs:line
150
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
