Issues with source control:
- don't use version 6 (5 only)
- don't rename anything after it is added to source control ( that really can mess stuff up) Be sure of the name before you add it. If necessary copy the object rename and add it to source control then delete the old one.
- Be very careful with logging in to multiple machines. If I have items checked out on one development machine and log into another... source control thinks the ones on the new machine where the ones I was working on... even though they may be older versions.
- Add projects to source control using the ND Studio... if you start playing with the source control admin etc you can really mess things up.
If you want to use it make sure not to include the class files / and ser files when added the project. - ND studio does all this for you.
- Try to update your project using - project update - at least once a day if you have multiple developers. It is a good habit to be working on a current version of the project. It saves you some integration trouble in the end.
- lastly - or at least the last I can think of... this is very important - many of my developers got in the HABIT of doing it, and it really caused problems.
Make sure you have items checked out before modifying them. If you modify some files then try to save and it is not checked out, you obviously can't. It becomes a problems because some ppl simply check out the file leaving THEIR VERSION of the java file open in the studio. Then they simply save and check it back in. This causes big problems if the file in source control was different then the one they had on their local machine. - I know it obviously SOUNDS like a stupid thing to do when I write it out like this... but some ppl don't know better and it is best to inform them straight up so you can avoid the problem of lost code later.
Cheers
Troy McKinnon
Technical Team Leader
Integrated Quality Management System
Software Solutions Group
Nortel Networks - (Dept. 1P64)
(613) 765-7685 or ESN (395) 7685
-----Original Message-----
From: Lidia Marchioni [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, December 15, 1999 7:08 PM
To: Mckinnon, Troy [SKY:1P64:EXCH]
Subject: Re: [ND] Source control system for ND4/5
If you don't mind listing the "issues" I would post them as a technote...
thanks
lidia
�
Troy Mckinnon wrote:
�
Aby,
we use Visual SourceSafe 5 from microsoft and it has worked out great for us.
We of course are developing on NT machines...
There are some problems you can run into using VSS (i.e. 6 doesn't work correctly).
As well as some other minor problems that can be EASILY avoided.
We have been happy with VSS 5 which can be integrated with ND.
Cheers
p.s. if you are interested I can outline some of the 'issues' you can avoid.
�
Troy McKinnon
Technical Team Leader
Integrated Quality Management System
Software Solutions Group
Nortel Networks - (Dept. 1P64)
(613) 765-7685� or� ESN (395) 7685
-----Original Message-----
From:�� Curt Springer [SMTP:[EMAIL PROTECTED]]
Sent:�� Wednesday, December 15, 1999 10:15 AM
To:���� Aby Mathew
Cc:���� '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
Subject:������� Re: [ND] Source control system for ND4/5
We used open-source cvs, but not integrated with the ND studio.
�From glancing at comments on the list, it does not appear that studio
integration of source code control is smooth, no matter which product you use.
There are 2 related things that make life difficult:
1.� The fileset for an ND application object is objectname.* plus
links/<significantnumber>_<less significantnumber>.sid
thus some sort of mapping needs to be done between the .sid file and the
rest of the files.� With cvs, this was accomplished via a yellow pad.
2.� If you change one app object, ND will often or at least sometimes
regenerate the .sid files for app objects you did not change, in a way that
does not affect how ND processes the file, but which is detected as a
change by version control systems.� I think it reorders the contents of the
file.� If 2 people are working on different objects and doing an "update
all" to the repository, conflicts will be detected if by chance, both local
ND studios happen to regenerate the same .sid file for an object that
neither person is intentionally changing in the studio.
-- Curt, Team ND
At 07:09 PM 12/14/99 -0800, Aby Mathew wrote:
>Hi,
>
>Anybody has a recommendation for a neat Version Control system for ND4, one
>that integrates well with the ND Studio?
>
>My client is thinking about PVCS, VSS etc, but why re-invent the wheel when
>there are people out there with experiences of the good, bad and the ugly?
>
>Thanks for all your feedback.
>
>Aby
>
>
>
>
>_________________________________________________________________________
>
>For help in using, subscribing, and unsubscribing to the discussion
>forums, please go to: <http://www.netdynamics.com/support/visitdevfor.html>
>
>For dire need help, email: [EMAIL PROTECTED]
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: <http://www.netdynamics.com/support/visitdevfor.html>
For dire need help, email: [EMAIL PROTECTED]
�
