Find out the types of complex files in. Net)

In a project (. csproj. user ),(. csproj ),(. SLN ),(. suo ),(. projdata ),(. SCC) What are the files with the suffix, and what is the purpose? The query results are summarized as follows:

Solution file (. sln and. suo)

Visual Studio. NET uses two file types (. sln and. suo) to store solution-specific settings. These files are collectively referred to as solution files, which provide solution resource manager with the information required to display graphical interfaces for file management, so that each time you continue development tasks, all of them can be fully invested in the project and the ultimate goal, without being distracted by the development environment.

Description of extension name
. Sln Visual Studio. Solution organizes projects, project items, and solution items into a solution by providing reference to the environment on the disk.
. Suo solution user options record all options that will be associated with the solution, so that each time you open it, it contains your custom settings.

 

The following is an article written by a foreigner. The original Article is as follows:

When you browse a project directory, you will always feel that the file type of. NET Framework is a bit confusing. This article will give you a deeper understanding of different files and extensions of. NET and Visual Studio. NET.

When you access a public site and see the familiar file extensions in the URL, you must immediately recognize the tools used by the site for development. Although HTML is the standard of the internet, you will often encounter. asp and wonder why developers use this old technology. If you find. aspx, you must guess the ASP. NET version number used by the programmer during development.

Recently, I was reminded of the differences in many file types between. NET and Visual Studio. NET (vs. net. As a result, the roles of different file types are summarized here, especially the usage details of different file types.

Vs. Net file type

Now let's take a look at the files used by vs. net. vs. NET is currently the most popular ide developed by. net. The following list provides common files for vs. Net (only C # and VB. NET are involved ):

•. Sln: vs. Net solution file, including: Project information contained in the solution, and access global build settings through the Properties window.
•. Suo: vs. Net solution user option file. It is used to store user-specific settings. The source control integration package in vs. net uses this file to store the conversion table of the web project, the offline status of the project, and the settings built by other projects.
•. Csproj: A vs. Net C # project file that includes project details, such as reference content, name, and version.
•. Csproj. User: C # project user options.
•. Vbproj: A vs. Net VB. NET project file.
•. Vbproj. User: user options for the VB. NET project.

Common Development File

When developing a web site, Windows service, or Windows program, you may use the following file types:

•. VB: a file that contains the source code of VB. NET.
•. CS: a file containing C # source code
•. XSD: XML schema file, which is the data definition standard of XML. You can use these files to process datasets and classes.
•. MDF: An empty SQL database with local data.
•. Xml: an XML file and data standards.
•. XSLT: An XSLT file, that is, the standard for converting XML documents.
•. CD: A class chart file.
•. JS: a file containing JavaScript code.
•. Vbs: a file containing VBScript code.
•. WSF: a file that contains scripts that can run in Windows programs.
•. Config: A program configuration file that can be set using the storage program. ASP. NET uses this file to configure Web Settings. It uses a web. config file that you cannot change.
•. Resx: The file used to edit and specify the program source.
•. ICO: an image file used to create a regular image.
•. Rpt: The Crystal Reports file that can be published to web or Windows Forms.
• .Txt: a simple text file.
However, you can use these files without considering the project type. A specific project has a specific file type. For example, you can use the following file types in a web development project.

 

ASP. NET file type

ASP. NET uses a specific file type. The following lists the file types that you will encounter during ASP. NET development.

•. Aspx: A web form that contains a code-behind file.
•. Asax: This file allows you to write code to handle global ASP. NET program events. The file contains an unchangeable global. asax file.
•. Ashx: the page that executes a general handle.
•. Asmx: an ASP. NET web service, including corresponding code separation files.
• .Htm: a standard HTML page.
• .Css: a stacked list used on the site.
•. Sitemap: A web application site map.
•. Skin: Specifies the ASP. Neta theme file.
•. Browser: defines the file in the browser.
•. Disco: an optional file.
•. Ascx: Web user control.
You can also use other files not in the list, depending on how the program is compiled and configured.

 

Other files

If you compile the program, A. EXE file will be generated in the local binfile of the main program. A. PDB file is also generated. This. PDB file contains the compilation and project status information. These files are automatically generated during the compilation process, but you can also control them during the compilation process without generating them. During the compilation process, you will also encounter another file, namely, the. Act file used by Application Center test.

Now you have some knowledge about the file type of. NET Framework. The advantage of familiarity with these specific files is that if the file is lost, you can regenerate the file.

 

The author of this article, Tony Patton, started his career as an application developer and has obtained Java, VB, Lotus, and XML certifications with a wide range of knowledge.
This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/Rommen/archive/2010/05/06/5561808.aspx

======================================

6.2 SolutionFile Format

Visual Studio2008 is actuallySolutionCreate two files with the extension. suo and.SLN(SolutionFile ). The first file is a binary file that is difficult to edit. It contains user-related information. For example,SolutionThe location of the file and breakpoint opened during the last close. This file is marked as hidden, so it is not displayed inSolutionFolder, unless the option to show all files is enabled.

The. suo file is occasionally damaged, resulting in unexpected results when building and editing the application. IfVisual StudioFor eachSolutionIf the file is unstable, delete the. suo file. Next timeSolution,Visual StudioIt will be rebuilt.

.SLNSolutionThe file containsSolutionRelated information, such as the project list, build configuration, and other non-project-related settings. AndVisual Studio2008 other files used are different,SolutionThe file is not an XML document because it stores information in the block, as shown in the following example file:

MicrosoftVisual StudioSolution file, format version 10.00

#Visual Studio2008

Project ("{F184B08F-C81C-45F6-A57F-5ABD9991F28F}") = "firstproject ",

"Firstproject \ firstproject. vbproj ",

"{D4FAF2DD-A26C-444A-9FEE-2788B5F5FDD2 }"

Endproject

Global

Globalsection (solutionconfigurationplatforms) = presolution

Debug | any CPU = debug | any CPU

Endglobalsection

Globalsection (projectconfigurationplatforms) = postsolution

{D4FAF2DD-A26C-444A-9FEE-2788B5F5FDD2}. debug | any CPU. activecfg =

Debug | any CPU

{D4FAF2DD-A26C-444A-9FEE-2788B5F5FDD2}. debug | any CPU. build.0 =

Debug | any CPU

Endglobalsection

Globalsection (solutionproperties) = presolution

Hidesolutionnode = false

Endglobalsection

Endglobal

Example aboveSolutionA firstproject project andSolutionThe global part of the configuration. Hidesolutionnode is set to false, soSolutionVisible in Solution Explorer. If you want to change this value to trueSolutionThe name is not displayed inVisual Studio.