Hi Steve,
Can you post a test case to the sharpcvslib dev list (cc'd on this email).  The nightly build might be the way to go if you are able to, the <cvs-update/> in the nightly build can be configured to use a different cvs executable (such as cvsnt).  It still uses the sharpcvs library by default but if there are issues with this then you can specify a different cvs binary.
-----Original Message-----
From: steve gupta [mailto:spam@stevengupta.com]
Sent: May 25, 2004 5:54 AM
To: nant-users@lists.sourceforge.net
Subject: [Nant-users] cvs update issues

My issue with the cvs update functions this week is that if I am trying
to do an update on a module and there is an empty non cvs directory
or empty cvs directory the update fails.
Any workarounds or is this fix in a newer build than the one I am using?