Results 1 to 4 of 4
  1. #1
    Join Date
    Apr 2008
    Along the shores of Lake Michigan

    Source Control - what do you use?

    We use MS-VSS here and it can be a real pain. Sometimes it refreshes, sometimes you have to exit the application and re-enter in order to see new additions/changes, just a lot of little things that make the product a little cumbersome at times. Simply looking to see what other professionals are using and if you think the product is worth the costs involved. Thanks.

  2. #2
    Join Date
    Feb 2004
    One Flump in One Place
    VSS - don't like it much.

    I attended a preview presentation of RedGate's new source control last week. It is not even V1 yet but looked very good. It fits in well with their other products (as you would expect) so if you have the toolbelt that adds value. It appears to sit as an FE to an SVN database (which is free).

    First impressions were it looked promising. It is an SSMS addin and will, for example, highlight all DB objects out of synch with source control when SSMS is launched. I do not know though if it will be once released, nor if it will be expensive. IME RedGate bundles are good value, single licences are very expensive.

  3. #3
    Join Date
    Apr 2008
    Bangalore, India
    Been using SVN and tortoise client for a long time, its been smooth most of the time. Over the years seen a number of version tracker but svn and mercurial are 2 that are responsive and fast.
    code free application environments

  4. #4
    Join Date
    Oct 2002
    Baghdad, Iraq
    Tried VSS once, never again.

    If you use SVN, get Trac. They work really nicely together to handle source control, quick documentation and bug tracking.

    For personal use, I've been using git through a github account. Git is very powerful and very fast, but it is hard to learn. For most stuff, though, you can use gitk or gitx, which are very nice GUIs for it.

    Incidentally, how do you keep your database in sync with your code? On one project, the database was basically embedded so it made sense to build it from scratch as part of the make process. On another, the data was independent of the project (and weighed in at a few terabytes, not that much but more than source control is designed to work with), but certain derived views were generated by the source code.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts