If i have global variable in A.dll, that depends on global variable in B.dll , is it guaranteed that B.dll will be loaded before A.dll? I made two sample dll projects in Visual Studio, and link A.dll with B.dll , and it seems, that B.dll is loaded first.So is this behavior guaranteed ?
相关问题
- How to know full paths to DLL's from .csproj f
- the application was unable to start correctly 0xc0
- how to call a C++ dll from C# windows application
- efficiently calling unmanaged method taking unmana
- Handle button click in another application
相关文章
- vs2017wpf项目引用dll的路径不正确的问题
- Why windows 64 still makes use of user32.dll etc?
- Can WM_NEXTDLGCTL be used with non-dialog windows?
- Determine if an executable (or library) is 32 -or
- Windows EventLog: How fast are operations with it?
- C++: Callback typedefs with __stdcall in MSVC
- Are resource files compiled as UNICODE or ANSI cod
- Is it possible to check whether you are building f
This behavior is guaranteed by the OS, because otherwise it would be impossible to write proper dll-loading code. In particular, if
A.dll
importsB.dll
, then when the dynamic linker attempts to loadA.dll
, it will see that dependency and loadB.dll
into the process first.