RE: Re: Visual Studio.Net and Subversion?

As a matter of fact I happen to personally do a lot of web development using class libraries instead of web projects as this is the only way I can build binaries into directories above the Web root so I am very cognizant of how "painless" it is.

At the end of the day it's a hack, and I cannot force development teams that are geographically dispersed to fundamentally change the way they are developing, change their wizard files (yes you must change the VS.Net install files if you want the user controls and aspx files to be available from the new item window if you are developing inside a class library), and convert every existing project.

I appreciate everyone's suggestions, but unless you are suggesting a way that I can install Subversion and tSVN (there is enough of a learning curve here already for the users) and it just "WORK" for the users without any scripts that must run when they open it, or converting of their projects and the way they currently dev, then it will never fly here. There is really no argument that can dispute this.

The bottom line is that either SVN / tSVN wants to fully support VS.net users or it does not. I can understand if the dev teams do not want to make this happen as it is their project and their prerogative, but everyone else who is trying to rationalize the current hacks that you must put in place to get around this must have a lot more pull at their organization than I do - or a lot more time on their hands to fight this fight.

I have been in this situation before and to try to force something like this is like laying your wiener on the chopping block. Every problem from then on out with Subversion becomes a more tense situation between the dev teams and the person who forced this decision. I like my wiener too much for this.

:)

We have a shop of 30-40 developers and switching our site
to use class libraries was a complete non-event for us.
In fact, IMO, it makes development make more sense, as it
decouples the build of our site from the running of our
site and with the exception of having to write a quick
macro to "attach to aspnet_wp process", it was completely
painless.

I understand if your (not you Folker, but OP's) shop doesn't
want to switch, but by making that decision, you are deciding
to do one of:

a. Not use subversion
-or-
b. Compile your own version of subversion with your own
or someone else's patches. (Want to know what's in those
mysterious patches? Read them...)
-and possibly-
c. Submit patches to either svn and/or microsoft to
fix one tool or the other in a clean fashion so you
can stop building your own custom versions.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 5 15:58:09 2004