When we develop a project with the VS, the first thing should be clear with the VS IDE generated some files and folders What do you mean, what role, to use in what situations
解决方案下 .sln文件和.suo文件的解释：
When a Web site is created, a solution file (.sln) and a hidden solution user options file (.suo) are created. By default, these files are created in the My Documents/Visual Studio 2005/Projects folder. bcoz they are not required in the deployed website.
SLN ( own’s the following details):
* A list of the projects that are to be loaded into Visual Studio 2005
* A list of project dependencies
* Microsoft Visual SourceSafe information
* A list of add-ins that are available
SUO ( own’s the following files):
* The task list
* Debugger break points and watch window settings
* Visual Studio window locations
Visual Studio uses two types of files (.sln and .suo) to store settings specific solutions, which are collectively referred to as the solution file. Graphical interface provides the information needed to display file management solution Explorer
so that each time the continued development tasks, the development environment will not distracted;
*.sln：(Visual Studio Solution) 通过为环境提供对项目、项目项和解决方案项在磁盘上位置的引用,可将它们组织到解决方案中。比如是生成Debug模式,还是Release模式,是通用CPU还是专用的等.
ps:就是打开文件的索引,正确引导你进入环境,进入工程!
*.suo: (solution user options) 解决方案用户选项记录所有将与解决方案建立关联的选项，
So that every time you open it contains custom settings you have made. For example VS layout, but do not turn off the file was last compiled project (next time you open a)
ps:大概就是保存一些与代码本身无关的一些配置.
*.suo 是一种文件的格式。它是很重要的文件，
*.suo 解决方案用户选项，记录所有将与解决方案建立关联的选项，以便在每次打开时，它都包含用户所做的自定义设置。
它储存了用户界面的自定义配置，包括布局、断点和项目最后编译的而又没有关掉的文件(下次打开时用)等，以便于下一次你打开Visual Studio可以恢复这些设置，因此不要随便删除，所以不要管它们。 其实上面英文中解释已经很清楚了，要申明的是PDB中不带断点信息.
Wherein, VS layout comprising: a variable distribution list, and breakpoint marker switch status, such as the output window error window and suspension, as well as monitor item 1234 unloading state flag.
* .suo file occasionally be destroyed, so that unexpected results occur when building and editing application. If Visual Studio for each solution is unstable, it should be deleted .suo file. The next time you open the solution, Visual Studio will rebuild it.
to sum up:
sln and suo files make up the logs and configuration solutions, VS solution various configurations are present here, specific to every detail not list above can give you a sense of the whole.
But you need to understand the fact that, sln and suo just a record of information solutions, detailed project information in other files, these two files only play the role of an organization, individual information collected in together to form a solution, to facilitate project development. We do not need to carefully study every detail, but this has been recognized on the whole, you know usually use the basic work record VS are stored in this file.
So, do not arbitrarily delete this your seemingly useless files, delete the code will not be lost, but sometimes after you configure the environment, but also more convenient to use, for these two documents, no need to touch it. In order to reduce the size of the project file, and these two files does not matter, but if done incorrectly, can result in solutions open. So the only solution to the reconstruction project, and then import the code files, just waste some time only, but also to re-organize project files.
These two documents are very basic, size is not large, but the solution does for the organization played an important role, not recommended to manually change arbitrarily, after operating in VS will naturally file modification.
