[dba-VB] Subversion, TortoiseSVN and VisualSVN

John,

Everything in Subversion can be controlled by using batch files - that is
the best approach (IMO) for the initial setup, bulk checking and working set
checkout: if I do not miss anything then I will post in the following
several e-mails under this topic the set of .bat files I used to create the
test environment last autumn(three projects ProjectA, ProjectB and
ProjectC). Stay tuned (after posting I will be out here until Sunday).

Thanks.

-----Original Message-----
From: dba-vb-bounces at databaseadvisors.com
[mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Friday, April 25, 2008 11:35 PM
To: Discussion concerning Visual Basic and related programming issues.
Subject: Re: [dba-VB] Subversion, TortoiseSVN and VisualSVN

Shamil,

I am also a "one man shop" however I still want a version control 
system.  One thing that it does for me is to allow me to do development 
on any of my machines and not worry about keeping the sources in sync. 
For example, a lot of time I just want to use my laptop, but the files 
are in the c: drive for that.  On Stonehenge they are on the C: drive 
there.  In Azul they are on the C: drive there.  Which version is the 
latest?

I would like to be able to work wherever I want but without a VCS that 
is tough.  I have a server that is x64 with more memory and a quad core, 
but I wrote it all on a different machine.  Trying to get it onto that 
more powerful machine has been fun.  If I can get it to just "check in" 
and "check out" then I can go to that machine and check it out and start 
running.

Shamil Salakhetdinov wrote:
> Hi John,
> 
> I did use Subversion for some time, then I abandoned it because customer
> didn't insist on using any source control tools, and because I'm still
> working mainly as one man shop...
> 
> ...I do plan to restart using Subversion hopefully in the near future - I
> wanted to be 'in' in this discussion and participate or at least lurk it
> because of a lot of work here, and not that much time left for pleasure of
> AccessD discussions...
> 
> ...I did also use TortoiseSVN...
> 
> ...I do agree that MS support is usually useless...
> 
> ...I did also use CruiseControl.NET as well as NUnit as well as MS Build
as
> well as I do plan to add to that "bundle" MS SoundCastle, NCover and some
> other useful tools...
> 
> ...one or another bug/issues/features tracking/managing tools should be
used
> - I do use Axosoft's OnTiome2008 now...
> 
> ...I did manage (last autumn) to make CruiseCOntrol.NET + Subversion + MS
> Build + NUnit working together and making automated builds and (unit) test
> runs - that's the only way to go for teamwork development these days...
> 
> ...all that mentioned above stuff worked well here but I must admit it was
> not that easy to make the parts working in ensemble but when everything
was
> tuned it happened to be relatively easy to handle stuff...
> 
> ...I have had two large ASP.NET applications with probably several (1,2,3
?
> I didn't count) thousands of source files and about 15 projects in two
> solutions to put into Subversion code base, automate compilation/building
> using CruiseCOntrol.NET and MS Build etc...
> 
> ...the only issue I can remember (after everything was set) is that I
didn't
> find how to easily manage the cases to synchronize central code db with
> local code versions when source files are moved from one folder into
another
> within the same project - I could have missed something because of lack of
> time, and experience or that could be a real "bottleneck" of Subversion
with
> everything else being very good I think...
> 
> ...I'd participate in preparing and publishing on AccessD web site
together
> with other interested AccessD members an instruction/manual and set of
> scripts and utilities on how to set up and effectively use together
> Subversion, CruiseCOntrol.NET, MS Build, NUnit etc. - although I can't say
> how much time I will have for this work...
> 
> Thank you.
> 
> --
> Shamil
> 
> P.S. As far as I know Subversion "beats" MS Source Safe for the cases when
> the project development should be fork-ed, and then several branches
merged
> back: the difference between Subversion and MS SourceSafe is conceptual
here
> IOW MS SourceSafe doesn't allow to automate "project forks" in principle.
I
> can be wrong, please correct me then, thank you.
> 

-- 
John W. Colby
www.ColbyConsulting.com
_______________________________________________
dba-VB mailing list
dba-VB at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-vb
http://www.databaseadvisors.com