>> p.s. if you are interested I can outline some of the 'issues' you can
avoid. 

Please, whenever you find time. Also it would be nice if you can brief on
what kinds of problem you had with VSS 6.

Thanks,

Aby

 

-----Original Message-----
From: Troy Mckinnon [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 15, 1999 8:12 AM
To: '[EMAIL PROTECTED]'
Cc: '[EMAIL PROTECTED]'
Subject: Re: [ND] Source control system for ND4/5



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
<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
<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]

Reply via email to