Visual C++ 2010에서 라이브러리 배포 정책 DarkKaiser, 2010년 5월 25일2023년 9월 6일 Central Deployment(중앙배포) Central deployment means that your Visual C++ DLLs are installed in the System32 directory. To centrally deploy your application, you can use one of the following: •The VCRedist_architecture.exe command-line tool. •Merge modules. VCRedist_architecture.exe installs all libraries for the specific hardware platform. Merge modules, or .msm files, are simplified Windows Installer installation packages. The main advantage of central deployment is emergency serviceability. If a critical security vulnerability is discovered, Microsoft automatically updates library files that are centrally-deployed. Local Deployment(지역배포) Local deployment means that your application’s library files are installed in the application folder. To deploy your application locally, simply copy the executable file and its associated library files into a folder. Different library versions can exist side-by-side because the filenames contain the version number (for example, version 10 of the CRT DLL is msvcr100.dll). Unlike centrally-deployed libraries, local libraries are not updated automatically by Microsoft. If you decide to use local deployment, you should also implement your own method of updating libraries. Static Linking(정적링킹) You can statically link your application to any library (such as CRT, MFC, or ATL) to produce an executable that has no dependencies on DLLs. The advantage of static linking is that deploying your application can be copied from one computer to another without also having to copy library files. If you use static linking and Microsoft updates the library that you linked to, your application cannot use the updated library. 기존의 WinSxS 방식을 사용하지 않고 이 방법으로 사용함. 참고: http://msdn.microsoft.com/en-us/library/dd293574(VS.100).aspx C/C++/VC++ 배포