Ian MacLean wrote:
That shouldn't be the case. There might be a property you need to set. Have tried debugging to work out where the null reference exception is coming from ?
I haven't got things setup for debugging - not even sure how to go about doing that (though I can't say I've tried to figure it out yet). But I have looked at the CreateVirtualDirectory code. According to the stack dump, it dies in SetIisProperties. Now, the first thing it does in there is get 'this.XmlNode' ... I'm wondering if that's the problem? Since the task wasn't created from Xml, I wouldn't think I'd have an XmlNode ...
I know that Clayton Harbor has recently been working on refactoring the solution task to defer to csc the same way you are doing. Maybe he can give some insight or you could look at the code hes been working on on the "SolutionPatchesBranch" :
I took a look, and found where the CscTask is being created ... but it hasn't helped. The only extra (non-CscTask-specific) properties/methods he uses are Verbose and InitializeTaskConfiguration. I've tried putting both into my code, and still get the same result.
------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ NAntContrib-Developer mailing list NAntContrib-Developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
