[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Seeking best practices and words of wisdom in using Subversion in an MS-Windows Visual Studio.Net environment...

From: si <sshnug.si_at_gmail.com>
Date: 2006-01-20 02:59:15 CET

Hi Dominic,

> I'm seeking best practices and words of wisdom in using Subversion in
> an MS-Windows Visual Studio.Net environment both from an administration and
> svn client perspective.

We're in the process of shifting from Delphi to Visual Studio (2005),
administration wise, not much has changed, although with the Subversion
1.3.0 release (we use ra_svn) i'm considering just having one repository
for all of our projects and using the new authorisation features to restrict
access to the various parts of the repository. Either that, or implement
authz-db like we do for password-db, i.e. have all of our repositories
pointing to the same authz-db file (using relative pathing in svnserve.conf).

I gather you know about http://ankhsvn.tigris.org? use the most recent
release (0.6.0.2305), although it's not as mature, i've found it easier when
refactoring and restructuring than SVN client or TortoiseSVN (which is great,
but like Subclipse for Eclipse, horses for courses).

Along with code, we're putting all of our tools (and their configuration) under
version control, in fact, almost everything is versioned (except for debug and
temp builds), and so far it seems to be working well. Projects reference our
tools (and other projects' libraries) using relative pathing (inside
repos/working
copy), so one update trickles through to all projects. Initially I tried using
svn:externals to reference tools, but found it overkill, relative
pathing is fine.

Lastly, for backups (hotcopy+verify and dump+zip), post-commit emails,
ensuring log messages are entered, etc, we're using my own NAnt-based
system to control the lot, it's specially designed for the lazy code monkey
turned into Subversion administrator ;-)

http://svn.berlios.de/viewcvs/subnant/trunk/README.txt?view=markup

The post-commit emails are implemented using Subversion properties:

http://svn.berlios.de/viewcvs/*checkout*/subnant/trunk/doc/commit-email.html

We use it against our 46 repositories. If you want to give it a bash, after
installation and editing the config, run the test target first (takes
about 15-20
minutes to run through all BDB and FSFS tests), and this will ensure
it's happy with your configuration, mail server and Subversion setup.

peace
si

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 20 03:00:21 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.