We have a VB6 application that launches a .NET CSLA DLL through COM and works fine. However, when the underlying VB6 DLL is launched through COM and then the CSLA DLL is launched through it, it does not know where to find the config file and thus doesn't get it's mappings to the data portal. Where should the config file live?
When it works, the config file is named after the VB6 EXE appname.exe.config. What should it be named and where should it live when launched through COM? I've tried naming it after the DLL (dllname.dll.config), but that doesn't work.
Any ideas would be greatly appreciated.
Thanks,
Darchele