Changes between Version 12 and Version 13 of Development/GettingStarted


Ignore:
Timestamp:
07/14/09 20:35:34 (10 years ago)
Author:
ibboard
Comment:

Split out subversion clients to shorten page

Legend:

Unmodified
Added
Removed
Modified

  • Development/GettingStarted

    v12 v13  
    2020=== SVN Client ===
    2121
    22 The easiest way to work with SVN is when source control is integrated in to your development environment. Unfortunately, Subversion plugins for Visual Studio normally come with a price tag and aren't compatible with Visual Studio Express (which leaves you with an even bigger price tag on Visual Studio).
    23 
    24 ==== SVN in MonoDevelop ====
    25 
    26 If you are using MonoDevelop then integrated subversion is already built-in through the supplied plugins. If the plugin is disabled then check that the Subversion client executable is installed on your computer. MonoDevelop will write a warning to the console if the plugin is enabled but it can't find the subversion executable, but not warn you through the GUI. Once MonoDevelop can see the subversion executable you should have a "Checkout" menu item under the "File" menu.
    27 Note:  Under versions of Ubuntu, you will also need to install the monodevelop-versioncontrol package before you will even
    28 have the option to "Checkout" under the MonoDevelop "File" menu.
    29 
    30 ==== SVN in Visual Studio ====
    31 
    32 There are several SVN plugins for Visual Studio, but all of the ones I've seen have a price tag and aren't compatible with Visual Studio Express editions. This is part of Microsoft's general tactic of getting people used to core functionality and then get the money when they want advanced functionality. The easiest solution (if you don't already have a full copy of Visual Studio) is to use an external SVN client.
    33 
    34 ==== External SVN clients ====
    35 
    36 If your development environment doesn't include SVN integration then the easiest alternative is an external client. There are [http://en.wikipedia.org/wiki/Comparison_of_Subversion_clients#See_also lots of clients] for all OSes. The most popular client for Windows seems to be TortoiseSVN, while most Linux developers tend to have development environments that include source control as a core feature.
    37 
    38 ==== SVN from the command-line ====
    39 
    40 The brave can always use SVN from the command-line. While it does have its uses, it's not generally advised for long-term use. Command-line arguments and usage instructions can be found in the [http://svnbook.red-bean.com/ SVN book at Red-bean.com].
     22The easiest way to work with SVN is when source control is integrated in to your development environment. Unfortunately, Subversion plugins for Visual Studio normally come with a price tag and aren't compatible with Visual Studio Express (which leaves you with an even bigger price tag on Visual Studio). If you don't know how to use Subversion in your chosen IDE or on your chosen desktop then the [./SubversionClients Subversion clients] page has more information.
    4123
    4224== Getting the source code ==