This association requires that all Microsoft Windows machines that are part of a JD Edwards EnterpriseOne solution and that perform business function builds share a Microsoft Visual C++ 2005 compiler with identical service pack releases. Each DLL-specific manifest identifies a specific runtime library release and version. With the Visual C++ 2005 or higher compiler, manifests associated with our DLLs must now be created. For instance, when the Microsoft Visual C++ 2005 Compiler and SPn, (where n represents a service pack) are installed on a machine, the Windows\WinSxS (side-by-side) folder is updated to include the associated compiler runtime libraries with the release level of Visual Studio 2005 SPn. Unlike past compilers, the runtime libraries must not only be release-specific but also version-specific. This DLL-specific manifest identifies the runtime library version used to compile and link the objects that were built. When JD Edwards EnterpriseOne objects are compiled using Microsoft Visual C++ 2005 and linked into a dynamic link library (DLL), a manifest file is created for each DLL.
Microsoft Visual C++ compiler release 2005 (v.8) or higher runtime libraries are not backward and forward compatible. Our installer process placed the runtime libraries in a location found within the server's path, (for example, %SYSTEMROOT%\system32), to make them accessible. For past Visual C++ compiler releases (before Visual C++ 2005), the redistribution of the compiler specific runtime libraries has been quite simple. Historically, the Microsoft Visual C++ compiler runtime libraries have been redistributed as part of our JDEdwards OneWorld Xe and EnterpriseOne products. A.1.1 Microsoft Visual C++ Runtime Libraries Background
0 kommentar(er)
