I am sure that the .NET code called through COM Interop will look for the "executable filename..config" in the same directory as the executable file name, where the executable file name is an unmanaged exe (calling process).
For classic ASP, this will probably be% WINDOWS% \ system32 \ dllhost.exe.config. I have a dumb memory that I was doing something similar almost ten years ago.
If you can modify your .NET project, the best option would be to manage your configuration settings in classic ASP code and pass them through the new Configure interface in your .NET library. Or use a different approach (for example, a registry or loading your own configuration file).
source
share