> I don't think it's too late. I would suggest that this issue > be documented and *IF* it's an MS bug, a link or reference to > a PSS Hotfix be made available. That way those who hit the > issue can resolve it on the end where it's being caused. > > The friendly error/exception message is still a must though > and could even reference the known issue.
First off all thanks to everyone who responded so quickly. Nice to know that a lot of eyes are watching Nant :^) I'll contact MS this week to see if it's a known issue and see what their answer is. Anyway, I do think that if it won't be solved from that side, the least we could do is update the documentation. I'll post more info if I get some more information. BTW, is there an official bugtracking system for Nant and if so, where to find it? Kind regards, Wilbert van Dolleweerd ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
