Problem using COM code created with .Net framework

We just upgraded from R6 to R8 and now my namgr.exe.config or nserver.exe.config files stopped working. It’s like it can’t see them.

We were using a 3rd party COM library for a Notes app. The COM library is created using .Net framework and acts as a proxy to a (microsoft) web service. It requries a config file which must be named “[my_app_name].exe.config”.

I tried to name the config file as “notes.exe.config”, and “nlnotes.exe.config”. But it seems that Windows doesn’t work with Notes in this way.

Would appreciate any suggestion regard this.

Subject: SOLUTION: Problem using COM code created with… (

Well… I got it to work. I recompiled the dll with a call to AppDomain.CurrentDomain.SetupInformation.ConfigurationFile within my C# dll and discovered that R8 was looking for a config file with a different name.

R6 wanted namgr.exe.config while R8 wants namgr.config.