Subversion

VisualStudio.Subversion History

Hide minor edits - Show changes to output

June 08, 2011, at 11:45 PM by 24.64.76.54 -
Changed line 68 from:
! How to Retrieve an earlier version'''.
to:
! How to Retrieve an earlier version
Changed line 93 from:
!To check out an existing SVN project:
to:
!To check out an existing SVN project from scratch
Changed line 102 from:
! To obtain the latest version of your project:
to:
! To obtain the latest version of your project
Deleted lines 122-176:







Subversion (SVN) is a source code management system similar to CVS, but nicer in many ways. It assists with collaborative development, and can be useful even for single-developer projects where code may be modified on different computers.

!!Basic Use in Visual Studio

To get started using Subversion:
# You will need to E-mail [[mailto:bugzilla@cpsc.ucalgary.ca|bugzilla]] and ask them to grant your CPSC account permission to access the SVN repository for the ILab.
# Download a program to interface with the SVN repository. We recommend [[http://ankhsvn.open.collab.net|AnkhSVN]], which integrates nicely with the Visual Studio 2005/2008 IDE.

For reference, the ILab SVN repository URL is as follows:
https://forge.cpsc.ucalgary.ca/svn/research/iLab/

To create a new Solution and SVN Project:
# When creating your project, check the "Add to Subversion" option.
# (Additional instructions?)


To create a new SVN project from an existing Solution:
# Open the Solution that you would like to put under version control.
# In the Solution Explorer, right click the Solution node and choose "Add Solution to Subversion..."
# The project name will already be filled in for you from the Solution name. Change this if you like.
# Copy and Paste the repository URL into the "Repository Url" dropdown.
# Check the "Add Trunk" option. (The trunk is meant to contain the branch under active development.)
# Click OK. This will refresh the tree view beneath the Repository URL box.
# You may wish to create a folder for yourself off the "svn/research/ilab" root node. If not, just select the root node. Click OK again.
# A dialog will come up where you can type in a log message. Maybe just type something in to the effect that this is your initial check in for the project. Click OK.
# The "Pending Changes" window will appear in the Visual Studio IDE window where you can select which items you wish to commit. You can muck around with this if you feel the need.
# Click the "Commit" button and wait for the process to complete.
# Congrats, your Solution is now under version control!

To check out an existing SVN project:
# Start Visual Studio
# Select File > Subversion > Open from Subversion
# If the URL for your Subversion repository does not appear in the URL dropdown, then click the Add URL button beside it and type in the desired respository URL. You will be prompted for your username and password.
# Browse to find the .SLN file of the desired solution you would like to check out. Select it and press the Open button. The "Open Project from Subversion" window appears.
# In most cases you want the Type to be Latest Version. In the Local Directory group box, you can select where you want the files to go on your local machine. If you don't like the automatic suggestion, you can browse for a different location.
# Click OK and wait for the project to download. The Solution will be opened and ready for you to stark working with it!

To commit changes to your project:
# Use the Commit button in the Pending Changes tool window, or right click on your solution and choose Solution File > Commit...
# Wait for the operation to complete.

To obtain the latest version of your project:
# Use the Update button in the Pending Changes tool window, or right click on your solution and choose Update to Latest Version
# Wait for the operation to complete.

!!Mixing Projects from Different SVN Repositories
You may wish to create your own solution which brings in one or more projects from a separate SVN solution. Furthermore, you may wish to put your own solution under version control. Luckily this works quite nicely because Visual Studio knows which projects belong to which SVN repositories. So if you add your solution to its own SVN repository, it will NOT include the sub-projects that are already under version control from other solutions. Furthermore, if you modify the projects from other repositories, your changes will automatically be committed to those subsequent repositories when you commit your solution.
June 08, 2011, at 11:44 PM by 24.64.76.54 -
Changed lines 68-72 from:
# '''Retrieve an earlier version'''. This can be done many ways. Here is one way.

** From the Solution Explorer, raise the Solutions context menu and select '''Subversion-SwitchSolution'''

** From the dialog box (below), change the Type to '''Revision''' and click the '''...''' browse button \\
to:
! How to Retrieve an earlier version'''.
This can be done many ways. Here is one way.

# From the Solution Explorer, raise the Solutions context menu and select '''Subversion-SwitchSolution'''

# From the dialog box (below), change the Type to '''Revision''' and click the '''...''' browse button \\
Changed line 76 from:
** The Log Viewer displays the various versions in the trunk (you can now see the value of the log messages! I skipped one intentionally, which makes that entry somewhat mysterious). Select Version 1, which shows what actions had been done between that version and the initial version.\\
to:
# The Log Viewer displays the various versions in the trunk (you can now see the value of the log messages! I skipped one intentionally, which makes that entry somewhat mysterious). Select Version 1, which shows what actions had been done between that version and the initial version.\\
Changed lines 93-97 from:

! This is left over from prior versions of this document - delete this?

To check out an existing SVN project:
to:
!To check out an existing SVN project:
Changed line 102 from:
To obtain the latest version of your project:
to:
! To obtain the latest version of your project:
Changed line 106 from:
!!Mixing Projects from Different SVN Repositories
to:
!Mixing Projects from Different SVN Repositories
June 08, 2011, at 11:41 PM by 24.64.76.54 -
Changed line 87 from:
** In the Url, change the path portion that reads 'branches' to '''tag\<SOMENAME>''', for example '''tag\Version2. Add log messages as desired. Note that you will have to rename this for every tag you save in the future - think of these as folders that would be otherwise overwritten. \\
to:
** In the Url, change the path portion that reads '''branches''' to '''tag/<SOMENAME>''', for example '''tag/Version2. Add log messages as desired. Note that you will have to rename this for every tag you save in the future - think of these as folders that would be otherwise overwritten (e.g., tag/Version3, etc). \\
June 08, 2011, at 11:40 PM by 24.64.76.54 -
Changed line 87 from:
** In the Url, change the path portion that reads 'branches' to '''tag'''. Add log messages as desired. \\
to:
** In the Url, change the path portion that reads 'branches' to '''tag\<SOMENAME>''', for example '''tag\Version2. Add log messages as desired. Note that you will have to rename this for every tag you save in the future - think of these as folders that would be otherwise overwritten. \\
Changed lines 94-95 from:
! DONE TO HERE
to:
! This is left over from prior versions of this document - delete this?
Changed lines 104-107 from:
'''To commit changes''' to your project:
# Use the Commit button in the Pending Changes tool window, or right click on your solution and choose Solution File > Commit...
# Wait for the operation to complete.
to:
June 07, 2011, at 09:19 AM by 24.64.76.54 -
Changed line 3 from:
!!Basic concepts
to:
!Basic concepts
Changed lines 9-11 from:
!!Basic Use in Visual Studio

!!
!To get started using Subversion:
to:
!To get started using Subversion:
Changed line 18 from:
!!!To create a new Solution and SVN Project:
to:
!To create a new Solution and SVN Project:
Changed line 46 from:
!! Ways of viewing your repository and its state.
to:
! Ways of viewing your repository and its state.
Changed line 58 from:
!! Using the Trunk
to:
! Using the Trunk to save your ongoing work
Changed lines 80-93 from:
to:
! Creating a Tag to save a snapshot of a specific version
As mentioned above, Tags are a way to save a complete snapshot of a version of your software. A typical use of a Tag is to save a version that is (say) a release or version update that you give to end users. While the trunk stores all your incremental work that is part of your routine development, a Tag is a good way to store a major version for later retrieval. The method used is almost identical to how you would create a Branch.

** '''Modify the Xaml file''' so the label reads Version 2 and commit it as normal to the trunk. We will save this version as well as a tag.

** '''Start the Save as Branch dialog'''. From the Solution Explorer, raise the Solutions context menu and select '''Subversion-BranchSolution...'''.

** In the Url, change the path portion that reads 'branches' to '''tag'''. Add log messages as desired. \\
Attach:SVN-TagDialog.png

** You can now, at any time, retrieve this version without going through the trunk.

June 07, 2011, at 08:50 AM by 24.64.76.54 -
Added lines 46-47:
June 07, 2011, at 08:48 AM by 24.64.76.54 -
Changed lines 68-69 from:
# Retrieve an earlier version. This can be done many ways. Here is one way.
to:
# '''Retrieve an earlier version'''. This can be done many ways. Here is one way.
Added line 71:
Changed line 75 from:
** The Log Viewer displays the various versions in the trunk (you can now see the value of the log messages! I skipped one intentionally, which makes that entry somewhat mysterious). Select Version 1, which shows what actions had been done between that version and the initial version.\\
to:
** The Log Viewer displays the various versions in the trunk (you can now see the value of the log messages! I skipped one intentionally, which makes that entry somewhat mysterious). Select Version 1, which shows what actions had been done between that version and the initial version.\\
Changed line 91 from:
To commit changes to your project:
to:
'''To commit changes''' to your project:
June 07, 2011, at 08:47 AM by 24.64.76.54 -
Changed lines 63-64 from:
! DONE TO HERE
to:
Changed line 73 from:
** The Log Viewer displays the various versions in the trunk (you can now see the value of the log messages! I skipped one intentionally, which makes that entry somewhat mysterious). Select Version 1, which shows what actions had been done between that version and the initial version.
to:
** The Log Viewer displays the various versions in the trunk (you can now see the value of the log messages! I skipped one intentionally, which makes that entry somewhat mysterious). Select Version 1, which shows what actions had been done between that version and the initial version.\\
Changed lines 76-80 from:
** Your solution will now show (via the label text) that you are now displaying original version 1.
to:
** Your solution will now show (via the label text) that you are now displaying the original version 1.


! DONE TO HERE
June 07, 2011, at 08:46 AM by 24.64.76.54 -
Changed line 61 from:
# Change the label in your MainWindow.xaml file to read 'Version 1.0.1'. The fact that this file has changed from the last committed version is shown both in the pending changes view and in the icon view by the red checkmark.\\
to:
# '''Modify your solution.''' Change the label in your MainWindow.xaml file to read 'Version 1.0.1'. The fact that this file has changed from the last committed version is shown both in the pending changes view and in the icon view by the red checkmark.\\
Added lines 65-81:
# '''Commit the Changes''' either by raising the context menu on your Solution and selecting '''Commit Solution Changes''', or by selecting '''File-Subversion-Commit''', or by selection 'Commit' from the Pending Changes window. Depending on the way you did this, you will have the opportunity to log a message as described previously.

# '''Repeat the above''' by changing the label to 1.0.2.

# Retrieve an earlier version. This can be done many ways. Here is one way.
** From the Solution Explorer, raise the Solutions context menu and select '''Subversion-SwitchSolution'''
** From the dialog box (below), change the Type to '''Revision''' and click the '''...''' browse button \\
Attach:SVN-SwitchTo.png

** The Log Viewer displays the various versions in the trunk (you can now see the value of the log messages! I skipped one intentionally, which makes that entry somewhat mysterious). Select Version 1, which shows what actions had been done between that version and the initial version.
Attach:SVN-LogViewer.png

** Your solution will now show (via the label text) that you are now displaying original version 1.


June 07, 2011, at 08:31 AM by 24.64.76.54 -
Added line 45:
# Congrats, your Solution is now under version control!
Changed lines 54-55 from:
# '''View in Pending Changes'''. Also from the VS 2010 View menu, select '''Pending Changes'''. This will raise the Pending Changes window (shown above) that displays all the files that have changed since this version was last committed. The above example lists nothing, simply because everything has been committed at this point.
to:
# '''View in Pending Changes'''. Also from the VS 2010 View menu, select '''Pending Changes'''. This will raise the Pending Changes window (shown above) that displays all the files that have changed since this version was last committed, and gives you the option to select (or unselect) what files you actually want to commit. The above example lists nothing, simply because everything has been committed at this point.
Changed lines 58-59 from:
to:
!! Using the Trunk
As mentioned, the trunk is where you store snapshots (versions) of your solution as you are developing it. Its up to you to decide how often you do this. For this example, we will save two versions of our hello world program, where all we do is change the label in each version

# Change the label in your MainWindow.xaml file to read 'Version 1.0.1'. The fact that this file has changed from the last committed version is shown both in the pending changes view and in the icon view by the red checkmark.\\
Attach:SVN-Version1.0.1.png
Deleted lines 64-81:


To create a new SVN project from an existing Solution:
# Open the Solution that you would like to put under version control.
# In the Solution Explorer, right click the Solution node and choose the "Add Solution to Subversion..." at the right-hand corner.
[[Attach:AddToSubversion.png]]

# Copy and Paste the repository URL into the "Repository Url" dropdown.
# Check the "Add Trunk" option. (The trunk is meant to contain the branch under active development.)


# Click OK. This will refresh the tree view beneath the Repository URL box.
# You may wish to create a folder for yourself off the "svn/research/ilab" root node. If not, just select the root node. Click OK again.
# A dialog will come up where you can type in a log message. Maybe just type something in to the effect that this is your initial check in for the project. Click OK.
# The "Pending Changes" window will appear in the Visual Studio IDE window where you can select which items you wish to commit. You can muck around with this if you feel the need.
# Click the "Commit" button and wait for the process to complete.
# Congrats, your Solution is now under version control!
June 07, 2011, at 08:24 AM by 24.64.76.54 -
Changed lines 5-8 from:
* '''Trunk''' is where all your incremental versions are saved. Whenever you do a change and commit it, it is saved as a version in the Trunk. You can retrieve different versions.
* '''Tag'''
is where you can store a self-contained snapshot of your code. Normally, you would do this to save (say) a version that was released to your end users. Tags are separate from trunks
* '''Branch''' is where you can store a version of your code that may differ from a version developed in the trunk (or another branch). There are options to merge branches, but that won't be discussed
here.
to:
* '''Trunk''' is where all your incremental versions are saved. Whenever you do a change and commit it, it is saved as a version in the Trunk. You can retrieve different versions. The trunk is meant to contain the branch of your code under active development. For example, lets say you already have a version 1 released to users, and you are developing version 2. You would save all the incremental (but perhaps unreleased to users) changes you make as you develop this 2nd version in the trunk.
* '''Tag''' is where you can store a self-contained snapshot of your code. Normally, you would do this to save (say) a version that was released to your end users. Tags are separate from trunks. For example, when Version 2 was done, you would save it as a tag.
* '''Branch''' is where you can store a version of your code that may differ from a version developed in the trunk (or another branch). For example, while developing version 2, you may be working on the main part of it (perhaps in the trunk, while someone else may be working on another part of it (as a branch). Afterwards, you can decide to merge the branch back into the trunk, but we won't discuss how to do that
here.
June 07, 2011, at 08:14 AM by 24.64.76.54 -
Changed lines 43-45 from:
to:
# Alternately, if you already had an existing solution that was not in subversion, you can add it to SVN after the fact: raise the context menu on the '''Solution''' in the Solution Explorer, and select '''Add Solution to Subversion'''. Note that this menu option won't be displayed if the solution has already been added.

!! Ways of viewing your repository and its state.
Before going on to show you how to save and manipulate versions, you should know about the several ways you can view your repository and its state.
# '''View in a web browser'''. There is nothing special about the repository. For example, if you point your browser to it (and enter your login name / password), it will let you navigate the file structure.\\
Attach:SVN-InBrowser.png

# '''View in Repository Explorer'''. From the VS 2010 View menu, select '''Repository Explorer'''. This will raise the repository explorer, where you can navigate and inspect all the folders and files in the repository. The properties window will show the state of each selected file, e.g., its last committed date.\\
Attach:SVN-Views.png

# '''View in Pending Changes'''. Also from the VS 2010 View menu, select '''Pending Changes'''. This will raise the Pending Changes window (shown above) that displays all the files that have changed since this version was last committed. The above example lists nothing, simply because everything has been committed at this point.

# '''Solution Explorer'''. As mentioned, the solution explorer adds icons next to each item managed by SVN, where icons indicate its state (see above, where the checkmarks indicate that all items are currently up to date in the repository). The context menus attached to each item also suggests what actions you can take on it given its current state.
June 07, 2011, at 07:59 AM by 24.64.76.54 -
Changed lines 42-44 from:
# (Additional instructions?)
to:



! DONE TO HERE
June 07, 2011, at 07:56 AM by 24.64.76.54 -
Changed lines 37-40 from:
# To commit all un-added files, raise the context menu on the '''Solution''' in the Solution Explorer, and select '''Commit Solution Changes'''. \\
to:
# To commit all un-added files, raise the context menu on the '''Solution''' in the Solution Explorer, and select '''Commit Solution Changes'''.
** It will raise a dialog box giving you the opportunity to log a message
** It will then display the actions it is taking on each file
** All the icons will then turn into a checkmark, showing what is currently up to date in the repository
\\
June 07, 2011, at 07:52 AM by 24.64.76.54 -
Changed lines 37-38 from:
to:
# To commit all un-added files, raise the context menu on the '''Solution''' in the Solution Explorer, and select '''Commit Solution Changes'''. \\
Attach:SVN-CommitSolutionChanges.png
June 07, 2011, at 07:49 AM by 24.64.76.54 -
Changed line 34 from:
# Your solution explorer will now show the state of each of your files by icons added next to it. The '''+''' means that these files have not yet been added to the subversion, i.e., they still have to be committed.
to:
# Your solution explorer will now show the state of each of your files by icons added next to it. The '''+''' means that these files have not yet been added to the subversion, i.e., they still have to be committed. \\
June 07, 2011, at 07:49 AM by 24.64.76.54 -
Added lines 34-37:
# Your solution explorer will now show the state of each of your files by icons added next to it. The '''+''' means that these files have not yet been added to the subversion, i.e., they still have to be committed.
Attach:SVN-HelloWorldV1.png
June 07, 2011, at 07:08 AM by 24.64.76.54 -
Changed lines 31-32 from:
# It will then raise another dialog box giving you the opportunity to create a log message detailing anything you've done. While you don't have to enter anything in the log, you'll find it handy as a way to add comments about your various versions. This will let you track things in the future.
to:
# It will then raise another dialog box giving you the opportunity to create a log message detailing anything you've done. While you don't have to enter anything in the log, you'll find it handy as a way to add comments about your various versions. This will let you track things in the future. \\
Attach:SVN-LogMessage.png
June 07, 2011, at 07:07 AM by 24.64.76.54 -
Changed lines 31-32 from:
to:
# It will then raise another dialog box giving you the opportunity to create a log message detailing anything you've done. While you don't have to enter anything in the log, you'll find it handy as a way to add comments about your various versions. This will let you track things in the future.
June 07, 2011, at 07:04 AM by 24.64.76.54 -
Added lines 24-31:
# You'll see the following dialog box. Within it,
** enter the iLab SVN repository URL: https://forge.cpsc.ucalgary.ca/svn/research/iLab/, which should display all the subfolders within it
** create a folder for yourself off the "svn/research/ilab" root node, to store this and other projects e.g., for me it was ''saul.greenberg''
** check the '''Add trunk Folder for Project''' at the bottom, which will establish this project in your trunk.
** You should get a message at the bottom saying where your project will be created. While you can change this, its probably best to leave it.\\
Attach:SVN-CreateFolder.png
Changed line 39 from:
# The project name will already be filled in for you from the Solution name. Change this if you like.
to:
Added lines 42-43:
June 07, 2011, at 06:55 AM by 24.64.76.54 -
Changed line 21 from:
# When creating your project, check the "Add to Subversion" option at the bottom right
to:
# When creating your project, check the "Add to Subversion" option at the bottom right \\
June 07, 2011, at 06:53 AM by 24.64.76.54 -
Changed lines 22-23 from:
Attach:AddToSubversion.png
to:
Attach:SVN-Add.png
June 07, 2011, at 06:47 AM by 24.64.76.54 -
Changed lines 22-23 from:
%rfloat% [[Attach:AddToSubversion.png]]
to:
Attach:AddToSubversion.png
June 07, 2011, at 06:46 AM by 24.64.76.54 -
Changed lines 22-23 from:
[[Attach:AddToSubversion.png]].
to:
%rfloat% [[Attach:AddToSubversion.png]]
June 07, 2011, at 06:45 AM by 24.64.76.54 -
Added lines 18-19:
The tutorial below illustrates the various steps using AnkhSVN and a 'Hello World' type of project, where different versions are indicated by the text in the window.
Changed lines 21-22 from:
# When creating your project, check the "Add to Subversion" option.
to:
# When creating your project, check the "Add to Subversion" option at the bottom right
[[Attach:AddToSubversion.png]]
.
Changed lines 28-29 from:
# In the Solution Explorer, right click the Solution node and choose "Add Solution to Subversion..."
to:
# In the Solution Explorer, right click the Solution node and choose the "Add Solution to Subversion..." at the right-hand corner.
[[Attach:AddToSubversion.png]]
June 07, 2011, at 06:39 AM by 24.64.76.54 -
Changed lines 1-2 from:
Subversion (SVN) is a source code management system similar to CVS, but nicer in many ways. It assists with collaborative development, and can be useful even for single-developer projects where code may be modified on different computers.
to:
Subversion (SVN) is a source code management system similar to CVS, but nicer in many ways. It assists with collaborative development, and can be useful even for single-developer projects where code may be modified on different computers.

!!Basic concepts
There are three main words you need to know, as it defines the primary ways that subversion organizes your code
* '''Trunk''' is where all your incremental versions are saved. Whenever you do a change and commit it, it is saved as a version in the Trunk. You can retrieve different versions.
* '''Tag''' is where you can store a self-contained snapshot of your code. Normally, you would do this to save (say) a version that was released to your end users. Tags are separate from trunks
* '''Branch''' is where you can store a version of your code that may differ from a version developed in the trunk (or another branch). There are options to merge branches, but that won't be discussed here.
Changed lines 11-14 from:
To get started using Subversion:
# You will need to E-mail [[mailto:bugzilla@cpsc.ucalgary.ca|bugzilla]] and ask them to grant your CPSC account permission to access the SVN repository for the ILab.
# Download a program to interface with the SVN repository. We recommend [[http://ankhsvn.open.collab.net|AnkhSVN]], which integrates nicely with the Visual Studio 2005/2008 IDE.
to:
!!!To get started using Subversion:
# '''E-mail''' [[mailto:bugzilla@cpsc.ucalgary.ca|'''bugzilla''']] and ask them to grant your CPSC account permission to access the SVN repository for the ILab.
# '''Download a subversion program''' to interface with the SVN repository. We recommend [[http://ankhsvn.open.collab.net|AnkhSVN]], which integrates nicely with the Visual Studio IDE.
Changed line 18 from:
To create a new Solution and SVN Project:
to:
!!!To create a new Solution and SVN Project:
Added lines 54-123:






















Subversion (SVN) is a source code management system similar to CVS, but nicer in many ways. It assists with collaborative development, and can be useful even for single-developer projects where code may be modified on different computers.

!!Basic Use in Visual Studio

To get started using Subversion:
# You will need to E-mail [[mailto:bugzilla@cpsc.ucalgary.ca|bugzilla]] and ask them to grant your CPSC account permission to access the SVN repository for the ILab.
# Download a program to interface with the SVN repository. We recommend [[http://ankhsvn.open.collab.net|AnkhSVN]], which integrates nicely with the Visual Studio 2005/2008 IDE.

For reference, the ILab SVN repository URL is as follows:
https://forge.cpsc.ucalgary.ca/svn/research/iLab/

To create a new Solution and SVN Project:
# When creating your project, check the "Add to Subversion" option.
# (Additional instructions?)


To create a new SVN project from an existing Solution:
# Open the Solution that you would like to put under version control.
# In the Solution Explorer, right click the Solution node and choose "Add Solution to Subversion..."
# The project name will already be filled in for you from the Solution name. Change this if you like.
# Copy and Paste the repository URL into the "Repository Url" dropdown.
# Check the "Add Trunk" option. (The trunk is meant to contain the branch under active development.)
# Click OK. This will refresh the tree view beneath the Repository URL box.
# You may wish to create a folder for yourself off the "svn/research/ilab" root node. If not, just select the root node. Click OK again.
# A dialog will come up where you can type in a log message. Maybe just type something in to the effect that this is your initial check in for the project. Click OK.
# The "Pending Changes" window will appear in the Visual Studio IDE window where you can select which items you wish to commit. You can muck around with this if you feel the need.
# Click the "Commit" button and wait for the process to complete.
# Congrats, your Solution is now under version control!

To check out an existing SVN project:
# Start Visual Studio
# Select File > Subversion > Open from Subversion
# If the URL for your Subversion repository does not appear in the URL dropdown, then click the Add URL button beside it and type in the desired respository URL. You will be prompted for your username and password.
# Browse to find the .SLN file of the desired solution you would like to check out. Select it and press the Open button. The "Open Project from Subversion" window appears.
# In most cases you want the Type to be Latest Version. In the Local Directory group box, you can select where you want the files to go on your local machine. If you don't like the automatic suggestion, you can browse for a different location.
# Click OK and wait for the project to download. The Solution will be opened and ready for you to stark working with it!

To commit changes to your project:
# Use the Commit button in the Pending Changes tool window, or right click on your solution and choose Solution File > Commit...
# Wait for the operation to complete.

To obtain the latest version of your project:
# Use the Update button in the Pending Changes tool window, or right click on your solution and choose Update to Latest Version
# Wait for the operation to complete.

!!Mixing Projects from Different SVN Repositories
You may wish to create your own solution which brings in one or more projects from a separate SVN solution. Furthermore, you may wish to put your own solution under version control. Luckily this works quite nicely because Visual Studio knows which projects belong to which SVN repositories. So if you add your solution to its own SVN repository, it will NOT include the sub-projects that are already under version control from other solutions. Furthermore, if you modify the projects from other repositories, your changes will automatically be committed to those subsequent repositories when you commit your solution.
July 15, 2010, at 06:07 PM by 136.159.7.119 -
Changed line 22 from:
# Check the "Add Trunk" option. (???)
to:
# Check the "Add Trunk" option. (The trunk is meant to contain the branch under active development.)
July 15, 2010, at 05:56 PM by 136.159.7.119 -
Changed line 6 from:
# You will need to E-mail [[bugzilla@cpsc.ucalgary.ca|bugzilla]] and ask them to grant your CPSC account permission to access the SVN repository for the ILab.
to:
# You will need to E-mail [[mailto:bugzilla@cpsc.ucalgary.ca|bugzilla]] and ask them to grant your CPSC account permission to access the SVN repository for the ILab.
July 15, 2010, at 05:56 PM by 136.159.7.119 -
Changed line 6 from:
# You will need to E-mail bugzilla and ask them to grant your CPSC account permission to access the SVN repository for the ILab.
to:
# You will need to E-mail [[bugzilla@cpsc.ucalgary.ca|bugzilla]] and ask them to grant your CPSC account permission to access the SVN repository for the ILab.
March 17, 2009, at 12:44 PM by 136.159.7.243 -
Changed lines 1-2 from:
Subversion (SVN) is a source code management system similar to CVS, but nicer in many ways. It assistes with collaborative development, and can be useful even for single-developer projects where code may be modified on different computers.
to:
Subversion (SVN) is a source code management system similar to CVS, but nicer in many ways. It assists with collaborative development, and can be useful even for single-developer projects where code may be modified on different computers.
March 17, 2009, at 12:36 PM by 136.159.7.243 -
Added lines 1-47:
Subversion (SVN) is a source code management system similar to CVS, but nicer in many ways. It assistes with collaborative development, and can be useful even for single-developer projects where code may be modified on different computers.

!!Basic Use in Visual Studio

To get started using Subversion:
# You will need to E-mail bugzilla and ask them to grant your CPSC account permission to access the SVN repository for the ILab.
# Download a program to interface with the SVN repository. We recommend [[http://ankhsvn.open.collab.net|AnkhSVN]], which integrates nicely with the Visual Studio 2005/2008 IDE.

For reference, the ILab SVN repository URL is as follows:
https://forge.cpsc.ucalgary.ca/svn/research/iLab/

To create a new Solution and SVN Project:
# When creating your project, check the "Add to Subversion" option.
# (Additional instructions?)


To create a new SVN project from an existing Solution:
# Open the Solution that you would like to put under version control.
# In the Solution Explorer, right click the Solution node and choose "Add Solution to Subversion..."
# The project name will already be filled in for you from the Solution name. Change this if you like.
# Copy and Paste the repository URL into the "Repository Url" dropdown.
# Check the "Add Trunk" option. (???)
# Click OK. This will refresh the tree view beneath the Repository URL box.
# You may wish to create a folder for yourself off the "svn/research/ilab" root node. If not, just select the root node. Click OK again.
# A dialog will come up where you can type in a log message. Maybe just type something in to the effect that this is your initial check in for the project. Click OK.
# The "Pending Changes" window will appear in the Visual Studio IDE window where you can select which items you wish to commit. You can muck around with this if you feel the need.
# Click the "Commit" button and wait for the process to complete.
# Congrats, your Solution is now under version control!

To check out an existing SVN project:
# Start Visual Studio
# Select File > Subversion > Open from Subversion
# If the URL for your Subversion repository does not appear in the URL dropdown, then click the Add URL button beside it and type in the desired respository URL. You will be prompted for your username and password.
# Browse to find the .SLN file of the desired solution you would like to check out. Select it and press the Open button. The "Open Project from Subversion" window appears.
# In most cases you want the Type to be Latest Version. In the Local Directory group box, you can select where you want the files to go on your local machine. If you don't like the automatic suggestion, you can browse for a different location.
# Click OK and wait for the project to download. The Solution will be opened and ready for you to stark working with it!

To commit changes to your project:
# Use the Commit button in the Pending Changes tool window, or right click on your solution and choose Solution File > Commit...
# Wait for the operation to complete.

To obtain the latest version of your project:
# Use the Update button in the Pending Changes tool window, or right click on your solution and choose Update to Latest Version
# Wait for the operation to complete.

!!Mixing Projects from Different SVN Repositories
You may wish to create your own solution which brings in one or more projects from a separate SVN solution. Furthermore, you may wish to put your own solution under version control. Luckily this works quite nicely because Visual Studio knows which projects belong to which SVN repositories. So if you add your solution to its own SVN repository, it will NOT include the sub-projects that are already under version control from other solutions. Furthermore, if you modify the projects from other repositories, your changes will automatically be committed to those subsequent repositories when you commit your solution.