Does .net calling COM which in turn calls other .net COM object works when using SxS and manifest fi
Posted
by Alex Shnayder
on Stack Overflow
See other posts from Stack Overflow
or by Alex Shnayder
Published on 2010-04-07T11:11:31Z
Indexed on
2010/04/07
11:13 UTC
Read the original article
Hit count: 513
I have a .net application calling to a COM component (C++) which in turn calls to another COM object implemented in .NET.
This application is using Windows SxS capabilities and does not register any of it's COM components. Not the one written in C++, and not the one written in .net.
This first call to the C++ COM component works fine. But when the C++ COM component calls to the .net one, it fails with class not registered.
I have tried creating a small C++ app with a manifest file which calls the .net component and it works. It seems that when the flow is .net -> COM NATIVE -> .NET COM. Then SxS breaks and does not work.
When looking at Fusion Logs (assembly loading logs) I see that no one is even attempting to resolve the .NET COM assembly.
Is this SxS scenario even supposed to work (I think it does supposed to work)? If yes, then what can I be doing wrong ?
© Stack Overflow or respective owner