- Open visual studio command prompt.
- Use this command: dumpbin /headers C:\path\name.dll
- At the very beginning, you will find “FILE HEADER VALUES”, the first value will have a “(x86) ” for 32 bit and “(x64)” for 64 bit.
A few days back I developed an ISAPI filter and when I installed it on the IIS server and tried to test it was not running. To troubleshoot I thought how would I know that DLL has been loaded by the IIS server successfully and there is no error? If you used Windows Task Manager it does not tell you which DLL has been loaded. There is a cool command line utility to check this. That is the tasklist. According to its description:
“This tool displays a list of currently running processes on either a local or remote machine.”
To check whether a DLL has been loaded or not use the following command.
> tasklist /m yourdll*
The /m switch lists all tasks currently using the given exe/dll name. It also supports wildcards. If the module name is not specified all loaded modules are displayed.
So, I used this command to check if my DLL has been loaded. It’s a really handy command to check some other stuff as well. Try to use /? to get a complete list of switches and their description.