Reprint Dll.refresh files and PDB files in. Net

Reprint Original Address: http://blog.csdn.net/lihuang319/article/details/6433727

Dll.refresh file

Open the Refresh file and you can see that it's just a path.

It is well known that. NET programs generate. dll files in the bin directory, and. Dll.refresh where does this file come from? The boring Google that day, this stuff is automatically generated when you reference a third-party assembly (directly) in your project, the. Refresh file stores the original file path for that third-party file, and if the DLL under that path is updated, vs in the cost of living project, The Assembly will be updated based on this address. Without this file, VS will not be able to update the referenced assemblies according to the latest state, which can cause problems with the assembly version being incorrect. A small detail will lead to big problems, everyone! In particular, when the project team came to the new members, to popularize education ....

Summarize the previous experience with assembly references:

1. Build a folder called "Dependency Library" at the root of the project, put the referenced third-party assembly in (so that the project development will not go around to reference, put in the bin will cause the source code management conflict problem, so can not be placed under the bin, to a separate folder)

2. Note the. refresh file, not when the temporary file is deleted, it identifies the file path of the original reference DLL.

PDB file

The PDB contains location information that points to the source code, so we can only find the source code when we debug it. Knowing this principle is also useful in team development in the future. When publishing, select release and be sure to delete the PDB file.

Reprint Dll.refresh files and PDB files in. Net