Tortoise SVN For VS.NET

If you haven't heard, there is a special version of Tortiose SVN now for people using VS.NET. It gets rid of the .svn folder problem that messed up VS.NET web projects.

8 Comments

  • Do you now of an idiots guide to getting Subversion working with VS.NET- like the whole thing step by step from installing Subversion right though?

  • Scott: the documentation shipped with subversion is pretty good, and very easy to read and understand. So setting it up would be a breeze. TortoiseSVN is also a tool which is very simple to use. You just have to read the docs with subversion to understand how it works, but it is explained in a professional way, in fact it is an ebook :)



    You can then use the vs.net plugin if you want to, however it's not required.

  • Jesse,

    What's your setup look like?

    CVS/Subversion/nant/CruiseControl/FogBugz?



    I'm Curious. I've been evaluating Vault. but no CCNET integration. I'd write it myself but have precious little time. Looking for a continuous intergation environment tied to defect tracking.



    Christian

  • Scott,



    Installation is pretty easy, it is just an MSI. After that, you need to launch svnserve as a scheduled task so that the server starts every time the computer runs and create a database for your code. As far as using with VS.NET, it isn't really integrated at that level (unless you get the VS.NET plugin, which is still pretty buggy). It is a file system level version control system, so you check in multiple files/directories at a time. TortoiseSVN is probably the best client out there, and I definately prefer it to VS integration for a lot of reasons (I have a post a while back on this).



    Christian,



    We are using subversion as our source control system. Our setup is just about what you listed. The only differences are that for all our internal projects we use a custom defect tracking system and we haven't added cruise control to the mix yet.

  • Ta...I had a play a few weeks ago but I never got very far. Plan to spend a bit of time looking at this sort of thing this weekend to get our build environment under a bit more control, could be interesting!

  • Hi Jesse,

    By the way, I could NOT find the "special version of Tortiose SVN now for people using VS.NET". Are you talking about AnkhSVN?

  • The Asp.net version of tortoise svn works great. So much better than SourceSafe.

    The only question I have is: what are your ignore patterns?

    Mine is as follows: *.dll *.pdb *.suo *.fxcop *.build

    This way, when you recompile your solution or .vbproj locally, it doesn't compare the dll's and the project is still up-to-date.

    However, when you checkout a project (let's say for the first time), those files are also excluded, and so you have to overwrite them with the full-source code anyway.

    Is there anyway to ignore a file on the commit only?


Comments have been disabled for this content.