I am using the Notes client COM components within a .NET appliacation. We have found that there is a bug in the way the nlsxbe.dll (Lotus COM DLL) is registered in the registry. It puts the ThreadingModel under the InprocServer32 key as it’s OWN key with a default value of Both. Instead, the OLE API’s need it to have the ThreadingModel as a value, not a key! When you make the appropriate fix to the registry, Notes COM works fine under the MTA model; when it is run with the regsvr32 registry settings, it runs with erratic behaviour, occasionally blowing out the stack in an infinite loop creating a Notes.Moniker object.
In any case, how can I get this issue raised to Lotus so that they can fix the registration handling code in that COM DLL? Doing a registry fix is a poor workaround. Is this the appropriate forum for raising these bugs?
Thanks,
Sam