Thoughts on Visual Studio 2017 dynamic Link Library (DLL / LIB) static Link Library (LIB)

Software engineering can develop rapidly, and I believe source code reuse plays an important role. On the Linux platform, as far as C++ is concerned, there is an obvious difference between dynamic link library files ending in so and static link library files ending in .a. However, under the Window platform, when a project such as DLL is compiled by Visual Studio, the target DLL DLL file is generated, and there is also a LIB file with the same name. The target static link library LIB file is also generated when compiling the static link library project separately. * * dynamic link library * * when you need to reference a dynamic link library in other projects, you need to introduce the LIB file of the dynamic link library into the new project as a resource, so that it can be compiled successfully when the project is generated, and the DLL dynamic link library file is not used in this process. The DLL file is needed at run time only when the compilation is complete, and an exception is thrown if not. ! [] (https://cache.yisu.com/upload/information/20200312/76/258671.jpg?x-oss-process=image/watermark,size_16,text_QDUxQ1RP5Y2a5a6i,color_FFFFFF,t_100,g_se,x_10,y_10,shadow_90,type_ZmFuZ3poZW5naGVpdGk=) [for more information here] (http://www.zyh2690.org/dynamic-link-library-dll-dynamic-import-libraries-lib-static-link-libraries-lib/))