Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Just one bit: Don't believe such crap as you have heard! The server is a server and *nobody* should do any work on that. All operations can and should be made from client workstations, including adding new modules to the server repository. There are at least two ways to do this: 1. The standard way (cvs import) This you do from WinCvs Create/Import module... It will grab all files in the selected directory plus recurse into all subdirectories and add these files too. 2. The cvs add way To use this you need to be in a valid sandbox. To create a top level module you must check out the module . (that is a period) and set the flag for no recursion. This creates a sandbox on the top level. Then move your source directory tree to this sandbox and use cvs add on the folders and then on the files inside. Rather tedious work but you have full control. You can also use Oliver's recursive add macro to ease the work. /Bo On Thu, 26 Sep 2002 17:21:09 -0400, RLMuller <RLMuller at comcast.net> wrote: >Hi All, > >I want to add a Visual Studio project to CVSNT installed on a Win2000 Advance Server OS. Then I like to able to checkout/in component from using WinCVS on a Win2000Pro workstation. > >Right now, I've got the source tree on the workstation. I read something in passing that I should always add new projects from the server rather than from a workstation to avoid problems with CRLF translation to and from Newline. Is that true? > >If you can direct me to the best write-up on getting started, I'd be most appreciative. I just bought the O'Reilly CVS Pocket Reference and ordered Open Source Development with CVS. I'm hopeful that will help. > >TIA, >Richard /Bo (Bo Berglund, developer in Sweden)