That's certainly fair. :)
I have actually had good results using both the tweaked version of
TortoiseSVN and a set of tweaked Windows console binaries written by
Jonathan Malek and available at his web site. He hasn't built new Windows
binaries for version 1.4 yet. I was going to, but he said he would probably
get to it by next week. For my own use, I just renamed his modified binaries
to the original names and put the originals in a backup directory.
Some folks might find this link useful for working with both _svn and .svn
forms of a working copy pretty painlessly
I have seen some comments in the archives about how rough it would be to
support the _svn format rather than .svn for various reasons. I may have
missed something, but it just didn't seem that rough to me. When I found
Windows Scripting Host) that just iterates through a svn working copy and
changes it between formats. In my informal testing it works just fine. You
don't have to get a new working copy or anything unpleasant like that. Since
the working copy it is just a local representation this doesn't affect the
repository on the server, or other developers. Although using a regular
Visual Studio web project would certainly affect other developers since they
would have to use the tweaked SVN or TortoiseSVN binaries.
Somebody else came along and polished the script up to take command line
args and more, from the looks of it. I haven't had a chance to look closely
at the mods, but I'm sure the tweaked script is a lot more user-friendly
than the original.
Everything should be as simple as possible, but not simpler.
-- Albert Einstein
From: Johnson, Rick [mailto:JohnsonR@gc.adventist.org]
Sent: Thursday, April 14, 2005 9:51 AM
Subject: RE: [TSVN] TortoiseSVN-1.1.5 for ASP.NET
This is a fair clarification of my statement. When I said "web server
structure", I was thinking "virtual directory setup". Even with this
clarification though, you still have the issues of .svn directories in Web
Projects. I haven't heard or seen any other way to get rid of that issue.
Since using class projects in Visual Studio solves both the problems of .svn
directories and not being able to open the project until the virtual
directories are created, I encourage everyone who shares ASP.Net projects
via Subversion to try this solution.
Of course you want the same directory structure from the project root on
down on each development machine. Actually, I shouldn't say "Of course"
since someone, somewhere has probably done a project that differs, but for
me the statement is true.
> -----Original Message-----
> From: Craig Tullis
> Sent: Thursday, April 14, 2005 10:49 AM
> To: Johnson, Rick; 'Lars Kaufmann'; email@example.com
> Subject: RE: [TSVN] TortoiseSVN-1.1.5 for ASP.NET
> I think it's fair to point out that using web projects does NOT
> require that every developer have exactly the same web server
> structure. I never set up a web project with the source code in the
> c:\inetpub\wwwroot directory tree, for example, and any developer
> working on the project could put their source tree anywhere it suits
> them. I've worked those projects where everything had to be in exactly
> the same structure, with drive letters embedded in the build scripts
> and so on. It's a major pain in the neck. All you have to do to avoid
> that is create a virtual directory in IIS that points at wherever you
> have the source for your web project.
> It's easy. You do, of course, obviously want the same directory
> structure on every developer machine downstream from the root web
> directory, right?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Apr 16 02:52:23 2005