note, i am not a dev, nor do i have anything to do with either project (apart from the odd bug report to asvn or questions, answers here), i am just a user and this is just my opinion.
I think it comes down to more of personal preference. ASVN & VSVN are architected completely differently ASVN is implemented on top of Visual Studio as a SCC provider (source code provider). this is the same interface that VS Team System uses to expose Team System in Visual Studio. VSVN is implemented as an Addin. Niether is an more correct or less incorrect implementation, there are advantages and drawbacks to both implementations. VSVN needs to know *intimate details* about a given project type loaded in visual studio, this is why when a new or different project type becomes available vsvn doesnt support it out of the box. Because ASVN is a SCC provider it does. Conversly because ASVN is a SCC provider it is asked by the project type infurstructure to adorn a given object. Often inside ASVN you do not get adornments on Physical nor Virtual folders (References, Properties) - because ASVN is not asked to adorn these folders. It is up to the project type infurstructure to decide how things are adorned. Compare this with the experience you get with VSVN, everything is adorned, I know more immeditely the state of my project because the adornments are more plainly visible. VSVN *wraps* a lot of functionality around TSVN, a stable, well established, and well supported product. Users get a more seemless experience using a tool they are very famililar with. I cant quite remember but I believe their was discussion around the TSVN wrapping being intemedary untill there is more intergration with VS - mabye a dev can confirm. ASVN implements its functionality as tool-windows *inside* visual studio, personally I prefer this intergrated experience but it has its caveats. Some functionality I want isnt there, it has its bugs but its mostly stable. ASVN doesnt have the history that TSVN does, its a younger product that is evolving. It is not my intention to convince you in one direction or the other thats not my place, Both projects have support (ASVN is supported thru Collab Net) I have my preference but having said that both tools have some work to do to get their tool more intergrated into visual studio. anyhow, off to bed On Mon, Jan 12, 2009 at 10:02 AM, <[email protected]> wrote: > > Can someone give me a synopsis of the advantages (and disadvtantages) > of VisualVSN over AnkhSVN (http://AnkhSVN.open.collab.net)? In > particular, we will be using it in a Visual Studio 2008 environment > developing Web ASP.Net and website projects. Thank you. >
