Walker dependency on .NET applications: FlsAlloc

Question

I tried to profile some .NET executables during dependencies and always get something like this:

GetProcAddress (0x7C800000 [KERNEL32.DLL], "FlsAlloc"), called from "MSCOREE.DLL" at 0x79006079 and returned 0xFFBADD11.

I tried to create a new Windows VS2005 project and did nothing but build it. Dependency walker still gives the same error. Does this mean that it is no longer possible to profile .Net applications, or am I missing something?

Answer 1

The dependency handler can only handle unmanaged programs.

Answer 2

Having the same problem, but the FAQ says the following:

Will Walker freeze work with COM, Visual Basic, or .NET modules?

Yes. Dependency Walker will work with any 32-bit or 64-bit Windows module, regardless of the language used to develop it. However, many languages ​​have their own way of defining dependencies between modules. For example, COM modules can have built-in type libraries and registry information, and .NET modules can use .NET assemblies. All of these methods are implemented as layers above the core Windows API. In the end, these layers still need to access the core Windows functions, such as LoadLibrary and GetProcAddress, to do the actual work. It is at this basic level that Dependency Walker understands what is happening. Thus, although Dependency Walker may not understand all the language-specific complexities of your application, it will still be able to monitor all module activity at the basic level of the Windows API.