How to get Subversion to work with automatically generated files?

I am using ASP.NET web deployment projects with TortoiseSVN and VisualSVN, but this is a general question about the generated files in Subversion.

A web deployment project automatically generates a parallel “deployment” version of your website with all the code removed and compiled into a single assembly. My file structure:

  • Trunk
  • Trunk / MyProject (root website)
  • Trunk / MyProject_deploy (root of the deployment project)
  • Trunk / MyProject_deploy / Release (root of the deployment website, automatically generated)

Here's the problem: MyProject_deploy / Release is restored during assembly (in release mode). The directory is deleted and recreated, so I lose all the .svn metadata; and when I go to commit, I get the status "Obstructed", which I looked at, and means that the server has an unmanaged local folder with the same name as the managed folder on the server.

(I could just ignore the Release folder, but I want the FTP deployment to be done directly from the Subversion server.)

What is the best way to work with automatically generated files in Subversion?

+3
source share
3 answers

svn: ignore. . , , . , .

, CruiseControl.NET, - , . 2 1 .

+14

Visual Studio, pre post-build .svn( ) Release , ?

+1

Windows.

- , , "Release".

In the case of the installation project, I generated one MSI file, and it worked well - no folders are deleted / created, so there are no SVN errors, and it is clean with only two files in the root of the deployment project folder.

+1
source

Source: https://habr.com/ru/post/1707071/


All Articles