On Tue, Dec 30, 2003 at 10:11:31AM -0500, Jim Sokoloff wrote:
>
> Incidentally, we ARE developing web .Net projects and our
> solution to the .svn problem is to use hard-links to link
> our working copy tree (where the .svn dirs are) to the web
> server tree (which does not have .svn dirs, among other
> differences)
>
Disclaimer:
I'm not sure that this is even possible with WebFolders, much less with
VS.NET thrown into the mix, but:
Have you tried using WebFolders to create a view of the repository for
Visual Studio?
With, for example, a repository layout like:
/trunk/
/branches/
/sandboxes/
anne/
bob/
you could keep a real WC of the trunk (like you are already doing)
and create S: which points at http://svnserver/svn/sandboxes/
(I'm guessing that's how WebFolders work). Use s:\anne as Anne's
Visual Studio project dir. She can make whatever changes she wants,
and save (autocommit) them to the /sandboxes/anne dir in the repository.
When she's done, she can merge those changes into the trunk-WC with the
svn command line utility, and then choose to continue work in the sandbox
or potentially to delete the sandbox dir and re-create it from trunk
(which would eliminate the need for ongoing merge-point tracking).
This model encourages a branch-per-change policy, which is not such a bad
thing, IMO.
If you try this, please let me know how it goes.
--ben
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 30 16:32:56 2003