Software<\/h2>\n
We are going to need some additional software.<\/p>\n
1. Server software<\/h3>\n
You need to install SVN server software on some server machine. We recommend to check VisualSVN<\/a>. It is easy to install and configure.<\/p>\n Another option is to use a hosted SVN solution. There are quite a few of them like Unfuddle and CodeSpaces. Besides SVN they provide project management tools, bug tracking and more. In this tutorial we’ll open a free basic account with Unfuddle which is easier than managing your own SVN repository. You can upgrade to a paid plan at any moment.<\/p>\n We recommend TortoiseSVN<\/a> client. It installs as a Windows explorer extension and available via context menu in all explorer windows.<\/p>\n Before we proceed with step by step tutorial lets consider a typical scenario that involves two developers working on the same PHPRunner project.<\/p>\n And here is the picture that tells it all.<\/p>\n Lets get started.<\/p>\n Create an Unfuddle<\/a> account. Create admin user. Proceed to ‘Repositories’ to create a new repository.<\/p>\n Note the URL of your repository (http:\/\/xlinesoft.unfuddle.com\/svn\/xlinesoft_cars\/ in our example).<\/p>\n Create a new PHPRunner project. Open project directory in Windows explorer (i.e. C:\\Users\\Sergey\\Documents\\PHPRunnerProjects\\Cars). Right click anywhere on blank space in Windows Explorer and choose SVN Checkout …<\/strong>.<\/p>\n Enter the URL of your repository. Checkout directory needs to be the same as your project drectory (C:\\Users\\Sergey\\Documents\\PHPRunnerProjects\\Cars). Click Ok. Enter username and password.<\/p>\n If checkout is successful you will see a hidden .svn folder created in your project directory.<\/p>\n Make changes to your PHPRunner project. Add a few tables, make some changes in Visual Editor. Save your project.<\/p>\n In Windows explorer select the all folders except visual<\/strong>, tmp<\/strong> and .svn<\/strong> and project file (.phpr). Right-click on selected files and choose Tortoise SVN->Add. Make sure all files and directories are selected.<\/p>\n Once files are added – right-click in the same folder and choose SVN Commit …<\/strong>. Make sure to add some comment.<\/p>\n Congratulations! Your files are one the server now. You can logon to Unfuddle account and view your files there.<\/p>\n Now second developer comes into the game. We want her to get a copy of the same project on her machine and make a few changes.<\/p>\n Once TortoiseSVN is installed we need to create a folder where this project will be stored. Once created, open this folder in Windows Explorer and right-click anywhere. Choose SVN Checkout …<\/strong>.<\/p>\n Enter repository URL and checkout folder. Enter username and password when prompted.<\/p>\n Note:<\/strong> we recommend to create a different user account for each user. This way you can track changes made by each developer.<\/p>\n Second developer makes a few changes in the Visual Editor and adds a new table to the project. Once project is saved she needs to add new files (if any) to repository.<\/p>\n In Windows Explorer make visual folder and PHPRunner project file selected and choose SVN Commit. Check off new visual files if any. Add a meaningful comment listing changes you have made. Commit.<\/p>\n Note the icons that TortoiseSVN adds to each file. The blue question icon means ‘not under source control’. The red exclamation point icon means ‘this file was modified’. The green check box icon means ‘normal’ status.<\/p>\n If you proceed to your repository at Unfuddle you can see that current revision number is 2. Each commit is associated with a new revision number.<\/p>\n Developer 1 runs SVN Update<\/strong> in the project directory to get new files and updated project file.<\/p>\n Developer 1 opens updated project file to see changes made by Developer 2. Mission accomplished.<\/p>\n There are a few things that may require some extra setup.<\/p>\n We need to make sure that database connection points to the same database on all machines. If you use a file-based database like MS Access the best approach is to put database file to the server and specify file to the database as \\\\server\\share\\database1.mdb<\/strong>.<\/p>\n In case of SQL Server, MySQL, Postgre or Oracle having a centralized development database makes even more sense.<\/p>\n The same story – you want output directory to point to the same directory on all machines. Something like C:\\Projects\\ProjectX<\/strong> will work just fine for this purpose.<\/p>\n Yes, we strongly recommend to use SVN or any other source control system even if you are a one person shop. It gives you both backups and ability to rollback any change made to the project. What else do you need?<\/p>\n Checkout<\/strong> – first step to get project files on a new machine. In most cases you only need to do this once.<\/p>\n Update<\/strong> – perform an Update every time before starting your work. You can run Update as many times as you want<\/p>\n Commit<\/strong> – commit changes you made. Commit at the end of the day or once you completed a large chunk of work. Run Update after Commit to incorporate changes made by other developers.<\/p>\n This is all you need to know in order to start using SVN with PHPRunner or ASPRunnerPro.<\/p>\n","protected":false},"excerpt":{"rendered":" Many developers have the need to work collaboratively on the same ASPRunnerPro or PHPRunner project. In this tutorial I’ll show how to make this happen with almost no effort. We are going to utilize the power of version control system (VCS). Version or revision control systems track and provide control over the changes to the source code. The most popular VCS systems nowadays are Subversion, Git, Mercurial and Bazaar. We plan to use Subversion (SVN) which is easy to get started with. I’ll cover the…<\/span>Continue Reading “Best practices: multiple developers working on the same project”<\/span> 2. Client software<\/h3>\n
Workflow<\/h2>\n
\n
![\"SVN](\"http:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2011\/06\/svn_workflow.png\" "\\"svn_workflow\\"")
<\/p>\nStep by step tutorial<\/h2>\n
1. Create a repository<\/h3>\n
![\"Creare](\"http:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2011\/06\/create_repo-300x251.png\" "\\"create_repo\\"")
<\/a><\/p>\n2. First checkout<\/h3>\n
![\"SVN](\"http:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2011\/06\/svn_checkout.png\" "\\"svn_checkout\\"")
<\/p>\n![\"After](\"http:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2011\/06\/after_checkout.png\" "\\"after_checkout\\"")
<\/p>\n3. Developer 1: Adding PHPRunner project to SVN<\/h3>\n
![\"\"](\"http:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2011\/06\/svn_add1.png\" "\\"svn_add\\"")
<\/p>\n4. Commit<\/h3>\n
![\"SVN](\"http:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2011\/06\/svn_commit.png\" "\\"svn_commit\\"")
<\/p>\n![\"Revision](\"http:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2011\/06\/repo_rev1-300x206.png\" "\\"repo_rev1\\"")
<\/a><\/p>\n5. Developer 2: Checkout<\/h3>\n
6. Developer 2: Committing changes<\/h3>\n
![\"Commit](\"http:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2011\/06\/svn_commit_second_machine.png\" "\\"svn_commit_second_machine\\"")
<\/p>\n7. Developer 1: Update<\/h3>\n
![\"SVN](\"http:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2011\/06\/svn_update.png\" "\\"svn_update\\"")
<\/p>\n8. Profit<\/h3>\n
![\"Profit!\"](\"http:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2011\/06\/profit.png\" "\\"profit\\"")
<\/p>\nAdditional notes and questions<\/h2>\n
Database connection<\/h3>\n
Output directory<\/h3>\n
I’m the only developer, should I still use SVN?<\/h3>\n
What’s the difference between Checkout, Commit and Update?<\/h3>\n