Hi,
I'm struggling with a COM Interop issue that only manifests itself on
our production boxes. The app works fine on the dev boxes
(furthermore, it works on the production boxes when the remote
debugger is installed).
In a nutshell I have a root aspx page that consists of a frame set,
which itself consists of three aspx pages. Each of the aspx pages has
C# code behind, that is deployed to a DLL. All of the aspx pages make
calls through the RCW into COM components. I've generated the interop
dll's from the dev studio.
The problem is that some of the COM calls do not return (only in
production). Logging shows that the thread of execution is reaching
the end of the COM method, but the RCW is not returning to the DOT.NET
thread. Bizarre and somewhat annoying.
Each of the child ASPX pages work in isolation; it appears that having
multiple threads within a single ASP.NET session that access COM
components, causes the RCW or the COM Package problems.
ANy comments or suggestions would be great.
Regards, Darren.
