C # development mode-multi-level dll reference,

C # development mode-multi-level dll reference,

C # The solution provides two reference methods: project reference and dll physical file reference.

I. Strict reference of project references. The project file must be included in the solution. The advantage is that it is easy to debug and can directly access the code. The disadvantage is that the coupling degree is too high (it must be fully compiled before it can be run). If the project is too large, compilation is troublesome, which is not conducive to deployment upgrade and testing. Because it is strictly referenced, replacing the dll alone does not work. It is quite troublesome to re-compile, package, uninstall, and install each update.
2. The dll physical file reference is loose and refers to the dll physical file. It doesn't matter if the dll project package is not included in the solution (generally included ), the advantage is that you do not need to re-compile all the files, but the premise is that the dll file must be placed in the referenced path. Otherwise, the compilation will not be updated. The disadvantage is that it is not conducive to debugging, because it is unclear about the program architecture for people with insufficient experience or new people who have just taken over, and the debugging of this method will not automatically enter the code segment, and process debugging must be attached, go to the dll code in advance to open a breakpoint. This method is applicable to large programs with local compilation, which facilitates upgrades, testing, and deployment (you do not need to package, or you can create a package yourself, because you only need to copy physical files ). No matter which type of reference, the referenced dll will be generated under the referenced path. The difference is that the project reference will be updated synchronously, while the dll physical reference will not update the dll under the referenced path, unless your own generated path is the path of the quoter (or clear or regenerate the quoter, but this is not recommended. Generally, the generated path is specified to the quoter path ).