Actually, nothing to report with Nant except that the tedious process of building the gnome libraries and all supporting packages on my older suse linux system, did finally get me to the point of running a gui debugger on NAnt. And the result? I stepped into an infinite loop. Same thing with the command line debugger. Same thing with a 5 line hello world type program, though I could step until I accessed a system dll.
So, I am left with the question I posed back awhile. To debug, I have to either wait until the debugger stabilizes, or go to something like log4net where I can assert debug statements (that could be turned off later with a config file change). If I were to go that way, I would prefer that the using log4net statements and the logger setup stay in the code. Ideally, some rationale and best practices for leaving logging assertions in the libraries would be useful too for later debugging purposes. But, there would have to be some agreement on style etc. so it didn't turn into chaos. Any thoughts? ------------------------------------------------------- This SF.net email is sponsored by: Tablet PC. Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
