• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            The ATL, MFC, Standard C++, and CRT libraries support the deployment model available on Windows XP, Windows Server 2003, and Windows Vista. The DLLs corresponding to all Visual C++ libraries have been grouped into several shared side-by-side assemblies and are installed into the native assembly cache, also called the WinSxS folder, under the operating system root directory. Similarly, while building a C++ application by using Visual C++, by default the compiler and the linker generate a manifest file that describes runtime dependencies of this application on Visual C++ libraries.

            Visual C++ libraries cannot be used by a C/C++ application without a manifest binding the application to these libraries. If a C/C++ application that depends on a Visual C++ library does not use a manifest, then an attempt to load the Visual C++ library as a dependent DLL from the application-local folder will result in an error message indicating that this is an unsupported way of loading a Visual C++ library.

            NoteNote

            On versions of Windows that do not support deployment of shared side-by-side assemblies, such as Windows 98 and Windows 2000 Server, the Visual C++ libraries are installed in the System32 folder and WinSxS folder under the operating system root directory. This setup enables running Visual C++ applications on these operating system versions because they do not support manifest-based binding of applications to dependent DLLs. On these operating systems, when an application is loaded, the corresponding manifest file is ignored and the operating systems searches for dependent DLLs using paths set in the current running environment. However, on upgrading the operating system to a version that support manifest-based binding, such as Windows XP, Windows Server 2003, or Windows Vista, applications built with manifests start using the DLLs installed in the WinSxS folder.

            This change to the deployment model of Visual C++ libraries prevents the problem of version conflicts between DLLs that occur when you add updates or configurations to a machine, and will allow support of side-by-side installation of two different Visual C++ toolsets. It will also allow you to produce reliable, self-describing applications and components that will not conflict with existing components. For more information on the advantages of new deployment model, please see Concepts of Isolated Applications and Side-by-side Assemblies. To learn about how this may impact deployment of existing native C++ applications, please refer to Redistributing Visual C++ Files.

            Visual C++ libraries have been packaged in several shared side-by-side assemblies with corresponding manifest files.

            Assembly Name

            DLLs included in the assembly

            Visual C++ Library

            Microsoft.VC90.ATL

            atl100.dll

            Active Template Library

            Microsoft.VC90.CRT

            msvcr100.dll

            msvcp100.dll

            msvcm100.dll

            C Runtime Library, release DLLs

            Microsoft.VC90.DebugCRT

            msvcr100d.dll

            msvcp100d.dll

            msvcm100d.dll

            C Runtime Library, debug DLLs

            Microsoft.VC90.MFC

            mfc100.dll

            mfcm100.dll

            mfc100u.dll

            mfcm100u.dll

            Microsoft Foundation Classes, release DLLs

            Microsoft.VC90.DebugMFC

            mfc100d.dll

            mfcm100d.dll

            mfc100ud.dll

            mfcm100ud.dll

            Microsoft Foundation Classes, debug DLLs

            Microsoft.VC90.MFCLOC

            mfc100chs.dll

            mfc100deu.dll

            mfc100esn.dll

            mfc100ita.dll

            mfc100kor.dll

            mfc100cht.dll

            mfc100enu.dll

            mfc100fra.dll

            mfc100jpn.dll

            mfc100rus.dll

            Microsoft Foundation Classes, localized resources

            Microsoft.VC90.OpenMP

            vcomp100.dll

            OpenMP Library, release DLLs

            Microsoft.VC90.DebugOpenMP

            vcomp100d.dll

            OpenMP Library, debug DLLs

            When you build applications with Visual C++ 2008, you may need to redistribute Visual C++ libraries and deploy the corresponding DLLs to customers' desktops. For more information please see Deployment (C++).

            Feedback

            # re: VS編譯動態(tài)庫無法直接運行,所需的其他文件說明(Visual C++ Libraries as Shared Side-by-Side Assemblies)  回復(fù)  更多評論   

            2010-11-24 09:32 by 楊書童
            在VS2005下用C++寫的程序,在一臺未安裝VS2005的系統(tǒng)上,
            用命令行方式運行,提示:
            “系統(tǒng)無法執(zhí)行指定的程序”
            直接雙擊運行,提示:
            “由于應(yīng)用程序的配置不正確,應(yīng)用程序未能啟動,重新安裝應(yīng)用程序可能會糾正這個問題”

            以前用VC6和VS2003的話, 如果缺少庫文件,是會提示缺少“**.dll”,但是用VS2005卻沒有這樣的提示。

            自己實驗了一下,感覺以下幾種解決辦法是可行的:
            方法一:
            在類似C:\Program Files\Microsoft Visual Studio 8\VC\redi
            st\Debug_NonRedist\x86\Microsoft.VC80.DebugCRT 下找到了下列文件:

            msvcm80d.dll
            msvcp80d.dll
            msvcr80d.dll
            Microsoft.VC80.DebugCRT.manifest

            把這幾個文件拷貝到目標機器上,與運行程序同一文件夾或放到system32下,就可以正確運行了。

            其他release版、MFC程序什么的都是拷redist下相應(yīng)文件夾下的文件就可以了,文件夾后都有標識!

            方法二:
            修改編譯選項,將/MD或/MDd 改為 /MT或/MTd,這樣就實現(xiàn)了對VC運行時庫的靜態(tài)鏈接,在運行時就不再需要VC的dll了。

            方法三:

            工程-》屬性-》配置屬性-》常規(guī)-》MFC的使用,選擇“在靜態(tài)庫中使用mfc”
            這樣生成的exe文件應(yīng)該就可以在其他機器上跑了。

            方法四:

            你的vc8安裝盤上找到再分發(fā)包vcredist_xxx.exe和你的程序捆綁安裝
            亚洲国产精品一区二区久久hs| 久久国产成人亚洲精品影院| 日韩av无码久久精品免费| 国产婷婷成人久久Av免费高清| 97精品伊人久久久大香线蕉| 久久国产香蕉一区精品| 久久SE精品一区二区| 99久久www免费人成精品 | www.久久99| 日本精品久久久久久久久免费| 97精品依人久久久大香线蕉97| 狠狠人妻久久久久久综合| 久久夜色精品国产噜噜亚洲AV| 性高湖久久久久久久久AAAAA| 99久久中文字幕| 久久久久久久久无码精品亚洲日韩| 久久黄视频| 97精品伊人久久久大香线蕉 | 97精品国产97久久久久久免费| 精品国产一区二区三区久久| 国产成人精品综合久久久久 | 久久精品国产精品亚洲| 久久99精品综合国产首页| 777午夜精品久久av蜜臀| 亚洲国产成人精品女人久久久| 亚洲国产精品久久66| 久久99精品久久只有精品| 亚洲AV日韩精品久久久久久久| 亚洲va久久久久| 无码国内精品久久综合88| 久久亚洲国产成人影院| 久久久久亚洲AV成人网人人网站 | 日本福利片国产午夜久久| 日本欧美久久久久免费播放网| 亚洲中文字幕无码久久综合网 | 久久妇女高潮几次MBA| 久久无码专区国产精品发布| 色偷偷88欧美精品久久久| 国产精品久久久久免费a∨| 国产精品久久久久久五月尺| 久久精品国产99国产精品导航 |