Differences between using MFC in a shared DLL and using MFC in a static library

When vs2008 is used, there is one of the following MFC settings in the project properties: 1. use the standard Windows library 2. use MFC in shared DLL 3. use the first type of MFC in a static library as the name suggests. The second type means that the content of some mfc dll files is not included in the EXE files during packaging, so the EXE files are small, but related DLL files are required in the system during running. The third isCodeIn the EXE file, the file is large, but can be run on a machine without the relevant DLL. At the same time, ifProgramThis is the second method. If you send it to a colleague and run it on the machine of the colleague, the following error may occur: "The program cannot be started ......, Failed to start the application because the application configuration is incorrect ."
I think it is better to select 3rd types of programs in the development stage. You don't need to worry about the size and efficiency. You can use other tools such as spy in later packaging, to detect the DLL.