Publishing my ASP.NET site ruins the Subversion files

Question

I've been trying to use SVN to deploy my asp.net site to production. My workflow is:

Setup: Publish Site to FolderX, Import FolderX to SVN, Update web server production folder with the repository for FolderX.

Everyday: Publish updated site to FolderX, Commit Changes, Update remote server with changes.

That's the theory, but when I publish the site again to FolderX, it destroys the .svn folders that are inside all the site subfolders.

How can prevent that from happening?

Answer 1

Well, a couple of things:

First, why does it matter if the .svn folders within the website are ruined? Surely you're not committing FROM your production environment back into SVN? I suspect the problem you're having is later updates. You can solve that particular problem by deleting the entire site before you update into it.

Second, why are you trying to use SVN for deployment? That's not really what it's for, and all it would take is about 5 lines of batch code to deploy your entire tree to the production location.

Answer 2

If you're using tortoisesvn, then click 'use _svn instead of .svn directories' in the settings.

Then the publish hopefully won't ignore the .svn directories.