We're a small team of 5 devs and just switched from Visual SourceSafe to svn
a few weeks ago. We're currently using Visual Studio .NET 2003 but plan to
upgrade to 2005 within 4-6 weeks. Currently, we use TortoiseSVN as our
primary interface. I also use Ankh (the Visual Studio svn plugin) to see the
status of files directly in Visual Studio. I prefer the maturity of the
Tortoise interface for committing and generating diffs.
We use the ASPNET hack because our main solution is an ASP.NET application
and the .svn directories confused Visual Studio. In this regard, the release
of the 1.3 binaries simplified our build process because it can use the _svn
folders directly.
Our svn server is Windows Server 2003 using the svn protocol (not http)
because it was less effort to setup. We do file-based backups nightly around
1am because no one commits at that time. I've been following the recent
hotcopy thread and will likely change our backup process.
We presently have two active branches (3.9 and 4.0) that we're planning to
begin merging but wanted to do this in svn rather than VSS so we could more
easily track history.
On 1/18/06, Dominic Caffey <zurvahn.domcaf@gmail.com> wrote:
>
> Dear users@subversion.tigris.org,
>
> 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.
>
> Thanks,
>
> Dom
>
>
Received on Thu Jan 19 22:00:29 2006