Calling functions in a DLL from an extension
I'm using TC8.1, have created an extension, and am now trying to call functions in a DLL from the extension code. Initially we were adding the DLL to the CLRBridge of our main project (not the e...
Forum Discussion
Thanks Julia.
That clears things up a lot.
My Test_Misc() function was in my extension and was my attempt to call functions in the LogGenerator.dll.
I was hoping to be able to have only the extension need to know about the LogGenerator.dll. I wanted to free the projects that use the extension from having to know anything about the dll. It looks like there is a limitation in extensions that will not let me do that (since it sounds like I have to add LogGenerator.dll to the CLRBridge for each of my projects in order for the extension to be able to use dotNET to call the dll).
That is what we were originally doing. However, that is forcing the writers of the projects to have to remember to add LogGenerator.dll to the CLRBridge of the project. We also seem to have problems getting the calls to LogGenerator.dll to work consistently. Sometimes reloading in CLRBridge helps and sometimes we have to remove and re-add LogGenerator.dll to the CLRBridge. This seems to be a lot of maintenance and it does not always fix the problem (I seem to get "[object Error] : Exception: [null]." a lot when I try to call LogGenerator.dll functions).
Maybe we'll try creating an exe that wraps the calls to the dll, as you suggested.
~Rob
That clears things up a lot.
My Test_Misc() function was in my extension and was my attempt to call functions in the LogGenerator.dll.
I was hoping to be able to have only the extension need to know about the LogGenerator.dll. I wanted to free the projects that use the extension from having to know anything about the dll. It looks like there is a limitation in extensions that will not let me do that (since it sounds like I have to add LogGenerator.dll to the CLRBridge for each of my projects in order for the extension to be able to use dotNET to call the dll).
That is what we were originally doing. However, that is forcing the writers of the projects to have to remember to add LogGenerator.dll to the CLRBridge of the project. We also seem to have problems getting the calls to LogGenerator.dll to work consistently. Sometimes reloading in CLRBridge helps and sometimes we have to remove and re-add LogGenerator.dll to the CLRBridge. This seems to be a lot of maintenance and it does not always fix the problem (I seem to get "[object Error] : Exception: [null]." a lot when I try to call LogGenerator.dll functions).
Maybe we'll try creating an exe that wraps the calls to the dll, as you suggested.
~Rob