12-29-2024 05:32 PM
hi,
I'm using teststand2020 API to create a .net application.In this application,I ran my sequence file and called a dll about insert-data to database,but it shows me member insert function not found in DLL.When I used teststand to run it,no error.how can I solve it?
12-29-2024 05:38 PM
In DLL adapter,I can find insert function easily,and it indeed calls correctly.
12-30-2024 10:40 AM
Some ideas/questions for you to investigate:
When you say that running the TestStand works I assume that means that you are using the Sequence Editor. One difference between that and your .NET application is that the base search directory would be different. Not sure if that could matter without knowing more about the DLL and its dependencies.
12-30-2024 05:37 PM
Thanks for your replying.Here is the Error info.
For 2,I indeed used workspace.So did I need to cancel this?
For 3,I will check my station settings
For 4,I used DLL adapter in this step.Because I need to insert my datas to the database,I used DLL to implement this part of the process.
For 5,I tried to test my DLL,it's strange that other functions can work when I tried to call,but insert-function no works.
12-31-2024 06:09 PM
The error message uses terms like member, class, assembly, which is what the .NET Adapter raises, not the DLL Adapter.
If the sequence works in the Sequence Editor and not in your UI, could it be resolving to find a different .NET DLL in each case?
01-01-2025 04:59 PM
Ok,So how do I confirm the path of the call while the application works?
01-02-2025 08:40 AM
If you only have one copy of the DLL on disk, you do not need to test for this.
Adapters likely use the capabilities of Engine.FindFile() to locate files, so you could use that in a step/expression and determine what it returns for the absolutePath parameter. For the currentSequenceFile parameter, you would pass a reference to the file that contains the step.
You previously stated that the function is found and works when called from the Sequence Editor, and is not found and errors when called from the customer UI. Can you clarify what you meant by your answer to (5) above? Did you get the same error from a TestStand installed UI example? Your previous answer suggests that your .NET DLL has multiple methods and that the "insert" method is the only one that fails in your custom UI?