In most of my programming career mainly I saved my codes in SVN(Subversion). So i have deep relationship with SVN. The main reason this always prefer to walk with SVN might be I think its simplicity, straight forward and fastest bidirectional code update.
I start my coding definitely with SVN, but later I moved to MS source safe(VSS). Since all my development I did with Visual studio, Source safe gave good support for me from the studio. But the poor performance of Source safe every time annoyed and it always brought that sweet thoughts of SVN. The big advantage here I've seen in Source safe was the easy isolation of Version control files and folders from the code files.
If you add your project to the SVN it'll add a "-svn" folder everywhere (inside every folder) in the project. So at the time of deployment everytime you have to go inside each and every folder and have to remove this svn folder(the reason for this svn removal is some time these files may create permission issues in the deployed server while manages with FTP). But in the case of Source safe everything manages with a single source file (project name.vss). So here things can do very easily.
When ever I do this file removal with SVN, I always would think about a simple solution probably hidden under SVN bunk. But truth is I never tried for that. The reason I again can tell most of my recent works I manages with VSS.
But recently, I was involving in big project deployment to a new server, the same concern came to me and I was really worried on how to remove these file from this big sized project which has thousands of folders under. I talked few of the senior people, but everyone has not much idea on SVN. Most of them worked only with VSS and they were well sounded in that(also I understood how much .Net people trust on their fully supported Source safe, even its poor performance ).
Instead of start my work I was sitting my seat, thinking. But the real truth once again got proved for me that "simplification will always happen whenever you approach things as simple". I simply discussed the context with one of my colleague who has comparatively less experienced there. He said he also doesn't have much knowledge in SVN, but in the past he heard some statements from his managers at the deployment time, they used the word "Export".
Yes, that was enough for me.. I jumped into my SVN context menu to know what is "export" or anything is there like that. Of course that was the answer... the perfect answer.. SVN Export will make your code isolated cleanly from the version control files.

Now situation is so calm. I went to cafeteria with my simple friend. :)