Hi,
This is a bit like a house of cards.
At the bottom is a 3rd Party dll which uses pointers to access its
functions.
The next layer up is a C++ dll wrapper that exposes a series of
functions that can be called in the dotnet Framework.
Wrapping this is my component written in vb.net.
In my test application if I create an instance of my component on the
main thread it works.
If I create a thread and attempt to instantiate and use the component on
the thread it fails with the above error message.
The dll that the error message points to is the third party one at the
bottom.
I think I must be making a general design error in my component.
How it hangs together is.
a) A module which declares all the library calls into the C++ Dll
b) A class with public functions that make the appropriate calls into
C++ Dll and return the appropriate values.
Is this an acceptable way of designing the component?
Any suggestions as to how to get fix this would be appreciated.
Thanks
Bob
