[AccessD] Source Code Control

OK, I did check the Source Control options for VS.NET 2005 - there are at
least two proposed by MS:

1. "Good" old VSS - it's improved, has remote Web access and it's called
VSS2005 now - relatively inexpensive option.
2. TeamSystem SS based on MS SQL - usd5000 per seat license cost(!?).

http://msdn.microsoft.com/vstudio/previous/ssafe/default.aspx?pull=/library/en-us/dnvsent/html/vssmap.asp

http://dotnetjunkies.com/WebLog/kenbrubaker/archive/2004/06/18/vss2005.aspx

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=150514&SiteID=1

Shamil

----- Original Message ----- 
From: "Jim Lawrence" <accessd at shaw.ca>
To: "'Access Developers discussion and problem solving'"
<accessd at databaseadvisors.com>
Sent: Thursday, January 19, 2006 8:43 PM
Subject: Re: [AccessD] Source Code Control


> Hi Shamil:
>
> I do not know. I went to an intro session on the product and after an hour
> of listening to the apps features and capabilities I realized it was far
> beyond anything I or small (medium?) company would ever need so did not
> investigate it further. (I have a full unlimited legal copy of TeamServer
> but would have to re-build my server to get it installed, so there it
sits.)
>
> Jim
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil
> Salakhetdinov
> Sent: January 19, 2006 5:18 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Source Code Control
>
> Hi Jim,
>
> And TeamServer uses VSS Server - Yes/No?
>
> Shamil
>
> ----- Original Message ----- 
> From: "Jim Lawrence" <accessd at shaw.ca>
> To: "'Access Developers discussion and problem solving'"
> <accessd at databaseadvisors.com>
> Sent: Thursday, January 19, 2006 3:11 PM
> Subject: Re: [AccessD] Source Code Control
>
>
> > Hi Shamil:
> >
> > MS uses TeamServer for all their projects.
> >
> > Jim
> >
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil
> > Salakhetdinov
> > Sent: January 18, 2006 11:57 PM
> > To: Access Developers discussion and problem solving
> > Subject: Re: [AccessD] Source Code Control
> >
> > > I mean, honestly, it works for a little side project
> > Josh,
> >
> > I guess MS uses VSS by themselves ...
> >
> > I did use VSS in a huge MSVC++ project of my colleague with thouzands of
> > source files and a half of a hundred projects - it worked well, no
> problems
> > at all...
> >
> > I think most of the "horror stories" about VSS are in the past now.
> >
> > Yes, I liked SubVersion for the features you describe and because it's
> open
> > source...
> >
> > If there is no need in these SubVersion features then VSS looks good
> enough
> > and stable.
> >
> > Shamil
> >
> > ----- Original Message ----- 
> > From: "Josh McFarlane" <darsant at gmail.com>
> > To: "Access Developers discussion and problem solving"
> > <accessd at databaseadvisors.com>
> > Sent: Thursday, January 19, 2006 7:22 AM
> > Subject: Re: [AccessD] Source Code Control
> >
> >
> > > On 1/17/06, Josh McFarlane <darsant at gmail.com> wrote:
> > > > I haven't used SourceSafe in Access personally, only C++ projects. I
> > > > find it interesting that they've worked out code to diff Access DBs,
> > > > but cannot make it compatible with Word for diffing.
> > > >
> > > > Granted, everything can be corrupt, but source-safe has a very very
> > > > bad track record with corruption, even on simple things. I can't
find
> > > > the link now, but once I hit my work computer I'll post it.
> > > >
> > > > When it's all said and done, I still prefer a stability and safety
> > > > over easy integration with Office / Visual Studio.
> > >
> > > OK, looked a little more into this, and supposedly if you run their
> > > analyze.exe tool at least weekly, it will drastically reduce the
> > > "fail" corruption rate (as it fixes the small corruptions before they
> > > propigate).
> > >
> > > Some other interesting things that I hadn't heard before:
> > >
> > > Large binary files often had to have their version history cleared
with
> > 3.1
> > >
> > > File locks were frequently left behind and had to be manually removed.
> > >
> > > Then there's the dreaded \data\a\aaaaaaaa.a error message that
> > > everyone seems to end up dealing with (For some reason, I swear there
> > > was a KB article dealing with all the possible ways this could pop up,
> > > but I can't find it)
> > >
> > > Also, if you delete a file, and then later recreate a file with the
> > > same name, the previous file history is gone forever (You can't check
> > > out previous complete builds anymore)
> > >
> > > I mean, honestly, it works for a little side project, but for anything
> > > a business is depending on, I don't trust my weight on it when there's
> > > free open-source products out there that do much much better in terms
> > > of both reliability and interface.
> > >
> > > --
> > > Josh McFarlane
> > >
> > > "Peace cannot be kept by force. It can only be achieved by
> understanding."
> > > -Albert Einstein
> > > -- 
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com