Before we start coding with VB6 I need to put in place a source control policy as the traditional methods dont suit. Does anyone have some rules and / or tools on how they control their source libraries, both test and production. Any advice on this would be most helpful. Thank you.
Regards,
Hans
UniObjects Source Control Policy
We use Microsoft Visual SourceSafe for all of our source code control. It has good integration with VB, and can be used in development teams quite happily.
It also seems to be quite robust and does the job well.
You can setup SourceSafe so that it either supports multiple simultaneous check-outs of the same file or just one check-out per file at one time.
With this tool you can also view changes between versions, merge changes done by more than one person, and SourceSafe also has an object library which you can use from within VB/C++ etc to programatically perform various functions on SourceSafe. Such functions may include reporting, or automating checking in and out files.
We have been using this tool for 3+ years and have had no problems what so ever, and recommend it to anyone.
Good Luck
Jason
-----Original Message-----
From: Morawa, Hans [mailto:Hans.Morawa@boral.com.au]
Sent: Friday, October 19, 2001 02:50 PM
To: u2-users@oliver.com
Subject: UniObjects Source Control Policy
Before we start coding with VB6 I need to put in place a source control policy as the traditional methods dont suit. Does anyone have some rules and / or tools on how they control their source libraries, both test and production. Any advice on this would be most helpful. Thank you.
Regards,
Hans
It also seems to be quite robust and does the job well.
You can setup SourceSafe so that it either supports multiple simultaneous check-outs of the same file or just one check-out per file at one time.
With this tool you can also view changes between versions, merge changes done by more than one person, and SourceSafe also has an object library which you can use from within VB/C++ etc to programatically perform various functions on SourceSafe. Such functions may include reporting, or automating checking in and out files.
We have been using this tool for 3+ years and have had no problems what so ever, and recommend it to anyone.
Good Luck
Jason
-----Original Message-----
From: Morawa, Hans [mailto:Hans.Morawa@boral.com.au]
Sent: Friday, October 19, 2001 02:50 PM
To: u2-users@oliver.com
Subject: UniObjects Source Control Policy
Before we start coding with VB6 I need to put in place a source control policy as the traditional methods dont suit. Does anyone have some rules and / or tools on how they control their source libraries, both test and production. Any advice on this would be most helpful. Thank you.
Regards,
Hans
Try MICROSOFT Visual Source Safe.
>Reply-To:
> "Morawa, Hans" "u2-users@oliver.com"
> UniObjects Source Control PolicyDate: Fri, 19 Oct
>2001 16:20:03 +0930
>
>Before we start coding with VB6 I need to put in place a source control
>policy as the traditional methods dont suit. Does anyone have some
>rules and / or tools on how they control their source libraries, both
>test and production. Any advice on this would be most helpful. Thank
>you.
>
>Regards,
>Hans
>This email and any files transmitted with it are confidential to the
>intended recipient and may be privileged. If you have received this
>email inadvertently or you are not the intended recipient, you may not
>disseminate, distribute, copy or in any way rely on it. Further, you
>should notify the sender immediately and delete the email from your
>computer. Whilst we have taken precautions to alert us to the presence
>of computer viruses, we cannot guarantee that this email and any files
>transmitted with it are free from such viruses.
------------------------------------------------------------
--== Sent via Deja.com ==--
http://www.deja.com/
>Reply-To:
> "Morawa, Hans" "u2-users@oliver.com"
> UniObjects Source Control PolicyDate: Fri, 19 Oct
>2001 16:20:03 +0930
>
>Before we start coding with VB6 I need to put in place a source control
>policy as the traditional methods dont suit. Does anyone have some
>rules and / or tools on how they control their source libraries, both
>test and production. Any advice on this would be most helpful. Thank
>you.
>
>Regards,
>Hans
>This email and any files transmitted with it are confidential to the
>intended recipient and may be privileged. If you have received this
>email inadvertently or you are not the intended recipient, you may not
>disseminate, distribute, copy or in any way rely on it. Further, you
>should notify the sender immediately and delete the email from your
>computer. Whilst we have taken precautions to alert us to the presence
>of computer viruses, we cannot guarantee that this email and any files
>transmitted with it are free from such viruses.
------------------------------------------------------------
--== Sent via Deja.com ==--
http://www.deja.com/
Hi there I have used both Microsoft Visual SourceSafe and CVS, they are pretty much identical in easy of use and functionality, however CVS is open source and free whereas Microsoft Visual SourceSafe is not.
Have a nice day
Moe Badawi
----- Original Message -----
From: "Morawa, Hans"
To:
Sent: Friday, October 19, 2001 2:50 AM
Subject: UniObjects Source Control Policy
> Before we start coding with VB6 I need to put in place a source
> control policy as the traditional methods dont suit. Does anyone have
> some rules and / or tools on how they control their source libraries,
> both test and production. Any advice on this would be most helpful.
> Thank you.
>
> Regards,
> Hans
>
Have a nice day
Moe Badawi
----- Original Message -----
From: "Morawa, Hans"
To:
Sent: Friday, October 19, 2001 2:50 AM
Subject: UniObjects Source Control Policy
> Before we start coding with VB6 I need to put in place a source
> control policy as the traditional methods dont suit. Does anyone have
> some rules and / or tools on how they control their source libraries,
> both test and production. Any advice on this would be most helpful.
> Thank you.
>
> Regards,
> Hans
>
> From: Jason McCulloch [mailto:jason.mcculloch@itvision.com.au]
>
> We use Microsoft Visual SourceSafe for all of our source code control.
> It has good integration with VB, and can be used in development teams
> quite happily.
We also use SourceSafe. We are reasonably happy with it. We had lots of problems with it at first; apparently it was not installed correctly (which Ive heard is easy to do). But since weve cleaned that up, its been pretty good. An occassional glitch but it works well enough for us.
- John M. Horn
HealthLink, Inc.
>
> We use Microsoft Visual SourceSafe for all of our source code control.
> It has good integration with VB, and can be used in development teams
> quite happily.
We also use SourceSafe. We are reasonably happy with it. We had lots of problems with it at first; apparently it was not installed correctly (which Ive heard is easy to do). But since weve cleaned that up, its been pretty good. An occassional glitch but it works well enough for us.
- John M. Horn
HealthLink, Inc.