SVN for Delphi Developers -

I have posted a question before, in which I asked about the best VCS control for Delphi developers which Were using Most developers use TortoiseSVN with STV. I tried this for a few days and I think that is the best way to go with it.

However, I still have some illusions on which svn works. Here are some questions that I want to answer:

1. Do I have an old lock way (Checkout-modified-checkin) which uses VSS?

2. There are two files in the Delphi form (MyForm.pas, MyForm.dfm). When I add any control over the form, both the files will be modified, so I want to do "myform.pas" and am also committed to "myform.dfm". Am I missing anything here?

3. This applies to the Delphi project file as well. Because this link with other files, when I change the project file, then all of them must be committed.

4. Your files in TSVN have been ignored, so TSVN will not (such as .dcu, .exe, ...) Search for files, and can I export it from one PC to another?

Now the way I am thinking in VSS style is to change, and it needs to be changed to the SVN style, but with VSS, all the things IDE Managed within, which was fantastic; -).

5. If I do Delphi Form (.pas and DFM) and have already updated a version already, how do you solve the conflict if there are some new controls and events Has been added to that form and unit (it requires Delphi developer with the SLN).

1. Yes, you can still lock the files, but it is not recommended is. You have to set svn: needs-lock property on all those files you want to lock, when you check out, they only get a read flag set. But again, this is not recommended workflow for text files just try the modified-merge workflow!
2. Since you are using Tauroise SVN: Right-click on your root folder, select "CAMT". In the Commit Dialog, you will see all the files which are required just check myform.dfm file for myform.pas and committed.
3. See 2. - But to be familiar with the concept, first of all you should read. All files will be committed together, no need (and definitely not recommended!) To separate each file!
4. See 2. - You should always have all the files related to a logical change. For example, if you add new controls to your form and apply the code while handling it, then you can only modify the form files, but many files may be more. Since a committed unit is a committed entity, so always submit all those files together.
5. You do not need to ignore the 'export' setting just add svn: ignored property is very easy to do with TortoiseSVN as explained.