Check dependency (a tool used to check the integrity of. Net file deployment)

Because. NET is very convenient to reference assembly, there are usually dozens of hundreds of DLL files in a large project release file. If there is a problem with the dependencies between these DLL files, the following similar situations will occur during the runtime:

In the face of such problems, we usually feel innocent, because it is notCodeProblems caused by logical errors. However, this is a serious mistake for customers. Therefore, we need to find a way to avoid this error.

To solve this problem, I wrote the check dependency tool.

TheProgramYou can analyze the files that are dependent on each assembly that do not exist in the current directory or that do not match the version number.

It should be mentioned that the system will. net Assembly output. I have not processed this because in some cases.. Net assembly is packaged and deployed together, so the output results must be screened. For example, in the above example, we found that the dependency of fxlib is incorrect.

However, it should be noted that when you solve a dependency problem in the output results, you 'd better run the program again to check. For example, if the problem of dependency on fxlib is solved, check again to see if other assebmly dependencies on fxlib are correct, this process is until you finally confirm that there is no dependency error in the output result.

Click here to download.

 

The software has been updated. Go

Check dependency 2 (a tool used to check the integrity and consistency of. Net deployment files)

 

Comments are welcome. Thank you!