When I edit my LabWindows CVI code from TestStand then create the DLL again TestStand cant find my function again when I run it gets error code 17005

[dls6116]

When I edit my LabWindows CVI code from TestStand then create the DLL again TestStand cant find my function again when I run it gets error code 17005

[dls6116]

Added info
 
When I call the LabWindows code from TestStand so that I can edit it LabWindows opens and the function is highlighted so it knows where it is.  I edit the file and save and rebuid the DLL.  When I go back to run the program in TestStand I get the following error:
 
Error loading step "DMM Test" of sequence 'MainSequence' in file 'Cd Test.seq'. 
Could not find function 'CheckDMM' in DLL.  error code 17005
 
I have gotten it to work (rarely) but not most of the time and I cant figure out what the difference is.

[Chris_G.]

Hello dls6116,

Thank you for posting on the NI Discussion Forums.  What exactly are you editing in the DLL?  If you have edited any function names, then you must choose the new names in the function pull-down menu in each step that the DLL functions are called from your sequence.  The pull-down menu automatically populates with the names of all of the functions in the DLL, so if the function you are looking for does not populate there, then it is not being seen in the DLL by TestStand.

Also, what version of TestStand are you using?  If you are using version 4.1, there is a button just below the Edit Code in file button called Verify Prototype in file.   Selecting this button will tell you whether or not the function name and parameters in the step match those of the source file.  If they do not, it will offer to create the function in the source file for you, where you can alter the definition as you did before.  If you cannot locate ?DMM Test? in the function pull-down menu, I would suggest using this button to create the function, and checking for any differences there may be between the generated function, and the one that you believe TestStand should be pointing to (i.e. case, misspellings, etc.).

[dls6116]

I am using testStand 4.1.  I was editing the code to fine tune my output.  I was not changing function names just code within the function.  I started over and created a new LabWindows program to call from testStand and I have had no problem with it.  The only issue I have is when I update my code in LabWindows I cant recomplie the DLL without getting out of the program in TestStand.

[Chris_G.]

Hello dls6116,

TestStand most likely still has a handle on the DLL after running the sequence, and it needs to be released before you can recompile the DLL from another application.  To solve this, from the main menu in TestStand, select Edit » Sequence File Properties to bring up the Sequence File Properties dialogue.  Then on the General tab, change the Unload Option to either ?Unload after step executes? or ?Unload after sequence executes?.  Then run the sequence once so that the DLL gets unloaded.  After this, you should be able to compile the DLL from LabWindows/CVI.