A “static” solution (in the sense it can capture a stack trace on demand) would be Process Monitor. A more dynamic solution would be ApiMonitor, but it may be too old to be compatible with the applications to monitor. Worth a try though.
Try regasm /u “[full path to your DLL in double quotes]” To re-register use regasm /codebase “[full path to your DLL in double quotes]” ignore the warning.
It’s when Application A installs a Shared DLL v1.0, Application B comes and updates the Shared DLL to v1.1 which should be compatible but there are slightly different behaviors, then App A stops working correctly and reinstalls v1.0 then App B stops working … now imagine this with more than 2 apps let’s say a … Read more
Storm’s answer is not correct. No hard feelings Storm, and apologies to the OP as I’m a bit late to the party here (wish I could have helped sooner, but I didn’t run into the problem until today, or this stack overflow answer until I was figuring out a solution.) The Visual C++ 2003 runtime … Read more
You can only load a 32bit DLL into a 64 bit process when you are loading the dll as a datafile. You can’t execute the code. (http://support.microsoft.com/kb/282423) Microsoft recommends that you use interprocess COM to use 32 bit code with a 64 bit application. Here’s an article explaining the process.
This is an area where PowerShell shines. If you don’t already have it, install it. It’s preinstalled with Windows 7. Running this command line: [System.Reflection.Assembly]::LoadFrom(“C:\full\path\to\YourDllName.dll”).GetName().Version outputs this: Major Minor Build Revision —– —– —– ——– 3 0 8 0 Note that LoadFrom returns an assembly object, so you can do pretty much anything you like. … Read more
It hides it in the GAC. There it may reside indefinitely. Using a more recent version may indeed solve the problem, but there is an outstanding bug in Visual Studio that has to do with choosing the correct version of DLL files. (If DLL Hell wasn’t bad enough, the Visual Studio team is making it … Read more
You can use PowerShell to get the information you want. (Get-Item C:\Path\To\MyFile.dll).VersionInfo By default this will display ProductVersion and FileVersion But the full VERSIONINFO is available. I.e. to return Comments (Get-Item C:\Path\To\MyFile.dll).VersionInfo.Comments
Like the others say, this is a .NET behavior. Assemblies loaded into an AppDomain cannot be unloaded. Only the AppDomain can be unloaded, and powershell uses a single appdomain. I blogged a bit about this some years ago: https://web.archive.org/web/20170707034334/http://www.nivot.org/blog/post/2007/12/07/WhyAppDomainsAreNotAMagicBullet When I test like this, I usually keep a shell open and use a nested shell … Read more
dumpbin is a tool that comes with VC++. To see what DLLs a program will import: Open Visual Studio Menu Item Tools | Visual Studio Command prompt cd to folder containing executable dumpbin /dependents whatever.exe Dump of file whatever.exe File Type: EXECUTABLE IMAGE Image has the following dependencies: AIOUSB.DLL sqlite3.dll wxmsw293u_core_vc_custom.dll wxbase293u_vc_custom.dll KERNEL32.dll ole32.dll OLEAUT32.dll … Read more