Today, we use igloo to integrate CVs and vs.net. It is very easy to implement the local machine as c/s at the same time (it is better to register the cvsroot environment), but note that it must be selected for all checkin, I don't want VSS to be as simple as checkin all
When the remote computer is used as the CVS server, it is okay to create the project checkin-update from the Local Computer (set up the user), but for localCodeCopy, but not from server checkout (not update), =I am very grateful to anyone who has solved this problem!= If you do not delete a local copy temporarily, open it with vs.net and right-click "get the latest version (recursion )".
As a result, the configuration of continuous integration (dailybuild) based on the. NET environment can be based on CVs, cruisecontrol.net, Nant, etc., without the participation of VSS, which is quite convenient. In the previous articleArticleTo modify the vssget task to a CVS task,
When you add a project of cruisecontrol, you can set a task to monitor CVs!
(Added later than 04/19) provides two reference articles:
Howto: CVs with vs. net
Vs. net use CVS to manage source code
In addition, almost all the igloo plug-ins provided on the website are invalid. I provide a valid address:
Download igloo from Apsara stack technical network [it may be slow. Use flashget...]
ForTortoisecvs, I have not used it yet, but this is definitely a good thing to use.