ViktorClerc
Programmer
Hello,
In linking two components, I decided to use a regular DLL. It is linked dynamically by one component, providing a standard DLL interface (C calling conventions). The actual operations are to be performed by the second component. This is a SmallTalk environment. I need to start this environment from my DLL using COM automation.
This has not succeeded. SmallTalk provides examples of an exe that is able to start the environment, but putting the same code inside a DLL results in a failure on the CreateDispatch call (CoCreateInstance of the SmallTalk environment).
Is this a security policy? Please help me out how to construct a COM bridge to an application using automation.
Regards,
Viktor Clerc
In linking two components, I decided to use a regular DLL. It is linked dynamically by one component, providing a standard DLL interface (C calling conventions). The actual operations are to be performed by the second component. This is a SmallTalk environment. I need to start this environment from my DLL using COM automation.
This has not succeeded. SmallTalk provides examples of an exe that is able to start the environment, but putting the same code inside a DLL results in a failure on the CreateDispatch call (CoCreateInstance of the SmallTalk environment).
Is this a security policy? Please help me out how to construct a COM bridge to an application using automation.
Regards,
Viktor Clerc