Influence of DLL. Refresh file When referencing the project class library

Yesterday, the Chinese Medical Society eye science branch of the optical group (www.chinaopt.org) site released a new version, the results found a serious problem, one of which is not automatically updated, but automatically generated an expiration version.

After investigation, it was found that it was related to a DLL. Refresh file in VSS.

The reason is simple:

1. When other external DLL references are added to the website during development, the system automatically generates the refresh file. This file is not generated if the DLL references of other projects under this solution are added.

2. The refresh file specifies the path to automatically update the DLL. If it is referenced by a Class Library, the dubug or release directory is specified. The file with this error specifies the DEBUG directory.

3. The developer mistakenly checked the file into VSSCodeLibrary

4. The problem is that the referenced class library has changed many times since the first release, but the interface has not changed. Therefore, the class library is generated independently, then, update only the corresponding DLL (release version) of all applications. There is no problem. However, when an application is re-released, because the refresh file exists in the bin directory of the project, as a result, the DLL is automatically updated in the specified path of the file, leading to the release of the earlier version DLL (debug version ).

Solution:

Delete the DLL. Refresh file in the application and re-release the application.

Or modify the content in DLL. Refresh. If the dll path is correctly written