颠覆应该忽略哪些Visual Studio文件以最大程度地减少冲突? [英] What Visual Studio files should be ignored by subversion to minimize conflicts?

问题描述

我支持许多使用Subversion进行版本控制的.Net开发人员，但我们遇到了许多问题，这些问题似乎与Visual Studio用于管理项目，进行调试的其他文件有关等等.具体来说，似乎这些文件正在引起冲突，因为它们已经在存储库中.我知道如何解决它们，以及如何处理它们，但是我需要知道什么是它们".

I am supporting a number of .Net developers who are using Subversion to version control their work, but we have been running into a number of issues that seem to revolve around the additional files that Visual Studio uses to manage projects, do debugging, etc. Specifically, it seems that these files are causing conflicts due to the fact that they are already in the repo. I know how to get them out and how to handle them, but I need to know what "they" are first.

那么，Subversion可以忽略的文件/目录是什么，为什么它们可以被忽略?(aka.这些文件做什么?)

So, what are the files/directories that Subversion can ignore, and why can they be ignored?(aka. what do those files do?)

这是一个大型的，没有组织的ASP.Net网站，并且通过部署该网站. svn更新，因此IIS在文件更改时需要动态编译(我认为就是这样)的站点所需的文件需要保留在存储库中.

This is a large, rather un-organized ASP.Net site and deploying the site is done via. svn updates, so files needed by IIS to dynamically compile (I think that's what it is) the site as files change needs to be left in the repo.

推荐答案

• bin和obj目录
• *.user文件(MyProject.csproj.user)
• *.suo文件

此外，如果您使用的是Visual Studio 2015，请使用.vs目录.

Also, if you are using Visual Studio 2015 the .vs directory.

这篇关于颠覆应该忽略哪些Visual Studio文件以最大程度地减少冲突?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！